| 1 |
Hello, |
| 2 |
|
| 3 |
On Sat, Feb 17, 2007 at 11:07:34PM +0100, Roman Naumann wrote: |
| 4 |
> Here the whole configuration: (imagine it as a complicated line of different |
| 5 |
> connections through the entire house...) |
| 6 |
> [SNIP] |
| 7 |
|
| 8 |
Hm, I think in theory you should have the PC in the middle with 2 IP |
| 9 |
addresses, on each interface different. On each segment (each side of |
| 10 |
the middle one) should be IPs from different range and there should be |
| 11 |
allowed routing (that I do not know how). It would look like this: |
| 12 |
|
| 13 |
-->( PC1 <IP-A/Range1> ) -- ( <IP-B/Range1> PC2 <IP-C/Range2> ) -- ( <IP-D/Range2> PC3 ) |
| 14 |
|
| 15 |
PC2 can comm with all (since it is on both nets). PC3 shloud use IP-C as |
| 16 |
its gateway, which will allow it to access PC1. PC1 should have static |
| 17 |
route for whole Range2 to IP-B, so it can send to PC3. Now, how is that |
| 18 |
set in Windows, who knows.. |
| 19 |
|
| 20 |
After this all is set, PC1 and PC3 should be able to talk to each other. |
| 21 |
However, you will not see the pings unless both directions work. |
| 22 |
|
| 23 |
So, you need to: |
| 24 |
• PC3: /etc/conf.d/net:routes_eth0 = { default via IP-C } |
| 25 |
• PC2: enable routing (I guess /etc/conf.d/net too) |
| 26 |
• PC1: add a static route Range2 -> IP-B. |
| 27 |
|
| 28 |
I just hope I did not mess that up. |
| 29 |
|
| 30 |
Or you can set up a bridge on PC2 to make both segments one net only: |
| 31 |
http://gentoo-wiki.com/HOWTO_setup_a_gentoo_bridge |
| 32 |
|
| 33 |
Have a nice day |
| 34 |
|
| 35 |
-- |
| 36 |
BOFH Excuse #452: |
| 37 |
|
| 38 |
Somebody ran the operating system through a spelling checker. |
| 39 |
|
| 40 |
Michal 'vorner' Vaner |
Archives