Two Segment setup

Hi all,

Thanks in advance for any and all advice. This is a relatively simple setup,
so I hope this is a nerf toss.

We are replacing our existing servers and network with a Linux network. We
currently have a large number of segments and a poorly designed system we
are hoping to streamline. Our proposed system is a follows.

Two Servers, Server A and Server B. Server A is a file server for Group A,
Server B is a file server for Group B (two portions of the same building).
Server B is also running a DHCP server and Server A is running DHCP relay to
get IP addresses from Server B.

Server A has two ethernet cards, IP addresses 192.168.5.X ("Server" segment)
and 192.168.6.X ("Client" segment) and Server B has IP addresses 192.168.5.X
and 192.168.7.X. So a Client on A segment gets assigned a 192.168.6.X
address and a client on B segment gets assigned a 192.168.7.X. All fine and
dandy so far?

Clients on B can see Server B and it's 192.168.7.X IP address fine, and can
ping it's other address fine as well, the 192.168.5.X one. However, the
routing stops there, and it cannot see the other server nor any of the other
client machines.

We need to add routing so that the Clients on each segment can see each
other, and the other server.

I imagine this is simple, but any advice is welcome and appreciated!

Matt

"Matt Fuerst" <(E-Mail Removed)> wrote in message
news:bf4bpn$fo1$(E-Mail Removed)...
> "Matt Fuerst" <(E-Mail Removed)> wrote in message
> news:bf3rsj$kg$(E-Mail Removed)...
> > Hi all,
> >
> > Thanks in advance for any and all advice. This is a relatively simple
> setup,
> > so I hope this is a nerf toss.
> >
> > We are replacing our existing servers and network with a Linux network.
We
> > currently have a large number of segments and a poorly designed system
we
> > are hoping to streamline. Our proposed system is a follows.
> >
> > Two Servers, Server A and Server B. Server A is a file server for Group
A,
> > Server B is a file server for Group B (two portions of the same
building).
> > Server B is also running a DHCP server and Server A is running DHCP
relay
> to
> > get IP addresses from Server B.
> >
> > Server A has two ethernet cards, IP addresses 192.168.5.X ("Server"
> segment)
> > and 192.168.6.X ("Client" segment) and Server B has IP addresses
> 192.168.5.X
> > and 192.168.7.X. So a Client on A segment gets assigned a 192.168.6.X
> > address and a client on B segment gets assigned a 192.168.7.X. All fine
> and
> > dandy so far?
> >
> > Clients on B can see Server B and it's 192.168.7.X IP address fine, and
> can
> > ping it's other address fine as well, the 192.168.5.X one. However, the
> > routing stops there, and it cannot see the other server nor any of the
> other
> > client machines.
> >
> > We need to add routing so that the Clients on each segment can see each
> > other, and the other server.
> >
>
> We're just tearing each others hair out over this. The relevant entries
from
> the machines...
>
> Server B
> /sbin/ifconfig
>
> eth0 Link encap:Ethernet HWaddr 00:08:C7:56:01:C2
> inet addr:192.168.5.65 Bcast:192.168.5.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:127189 errors:0 dropped:0 overruns:0 frame:0
> TX packets:27609 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:22958849 (21.8 Mb) TX bytes:3216313 (3.0 Mb)
> Interrupt:5 Base address:0x6880
>
> eth1 Link encap:Ethernet HWaddr 00:50A:BB:8C:0C
> inet addr:192.168.7.1 Bcast:192.168.7.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:610 errors:0 dropped:0 overruns:0 frame:0
> TX packets:444 errors:0 dropped:0 overruns:0 carrier:382
> collisions:0 txqueuelen:100
> RX bytes:90334 (88.2 Kb) TX bytes:85564 (83.5 Kb)
> Interrupt:11 Base address:0x6800
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:663050 errors:0 dropped:0 overruns:0 frame:0
> TX packets:663050 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2579291289 (2459.8 Mb) TX bytes:2579291289 (2459.8 Mb)
>
> /sbin/route
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.7.0 * 255.255.255.0 U 0 0 0
eth1
> 192.168.5.0 * 255.255.255.0 U 0 0 0
eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0
eth1
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> default 192.168.5.1 0.0.0.0 UG 0 0 0
eth0
>
> /sbin/ip route
>
> 192.168.7.0/24 dev eth1 scope link
> 192.168.5.0/24 dev eth0 scope link
> 169.254.0.0/16 dev eth1 scope link
> 127.0.0.0/8 dev lo scope link
> default via 192.168.5.1 dev eth0
>
> Server A
>
> /sbin/ifconfig
>
> eth0 Link encap:Ethernet HWaddr 00:08:C7:B1:B8:AE
> inet addr:192.168.5.66 Bcast:192.168.5.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:99060 errors:0 dropped:0 overruns:0 frame:0
> TX packets:32734 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:12888186 (12.2 Mb) TX bytes:11354648 (10.8 Mb)
> Interrupt:5 Base address:0x6880
>
> eth1 Link encap:Ethernet HWaddr 00:01:02:3D:6DE
> inet addr:192.168.6.1 Bcast:192.168.6.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1106 errors:0 dropped:0 overruns:0 frame:0
> TX packets:819 errors:0 dropped:0 overruns:0 carrier:387
> collisions:0 txqueuelen:100
> RX bytes:87527 (85.4 Kb) TX bytes:120193 (117.3 Kb)
> Interrupt:11 Base address:0x6800
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:491697 errors:0 dropped:0 overruns:0 frame:0
> TX packets:491697 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:1303638222 (1243.2 Mb) TX bytes:1303638222 (1243.2 Mb)
>
> /sbin/route
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.6.0 * 255.255.255.0 U 0 0 0
eth1
> 192.168.5.0 * 255.255.255.0 U 0 0 0
eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0
eth1
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> default 192.168.5.1 0.0.0.0 UG 0 0 0
eth0
>
> /sbin/ip route
>
> 192.168.6.0/24 dev eth1 scope link
> 192.168.5.0/24 dev eth0 scope link
> 169.254.0.0/16 dev eth1 scope link
> 127.0.0.0/8 dev lo scope link
> default via 192.168.5.1 dev eth0
>
>
> We connect a Client machine to the switch, set the IP address to
> 192.168.6.2, netmask to 255.255.255.0 and gateway to 192.168.6.1. The
> machine can successfully ping 192.168.6.1, the eth1 for Server A,
> 192.168.5.66 which is eth0 for Server B, but it cannot ping 192.168.5.65,
> nor could it ping any of the client machines connected to the 192.168.7.X
> portion....
>

Surely the sign of a desperate man responding to my own message not once,
but twice (what an idiot).

I have IP Forwarding enabled on both machines (more
/proc/sys/net/ipv4/ip_forward is 1) and I have the sysctl.conf file set to
keep it enabled after a reboot.

Matt

On Wed, 16 Jul 2003, Matt Fuerst <(E-Mail Removed)> wrote:
> Hi all,
>
> Thanks in advance for any and all advice. This is a relatively simple setup,
> so I hope this is a nerf toss.
>
> We are replacing our existing servers and network with a Linux network. We
> currently have a large number of segments and a poorly designed system we
> are hoping to streamline. Our proposed system is a follows.
>
> Two Servers, Server A and Server B. Server A is a file server for Group A,
> Server B is a file server for Group B (two portions of the same building).
> Server B is also running a DHCP server and Server A is running DHCP relay to
> get IP addresses from Server B.
>
> Server A has two ethernet cards, IP addresses 192.168.5.X ("Server" segment)
> and 192.168.6.X ("Client" segment) and Server B has IP addresses 192.168.5.X
> and 192.168.7.X. So a Client on A segment gets assigned a 192.168.6.X
> address and a client on B segment gets assigned a 192.168.7.X. All fine and
> dandy so far?
>
> Clients on B can see Server B and it's 192.168.7.X IP address fine, and can
> ping it's other address fine as well, the 192.168.5.X one. However, the
> routing stops there, and it cannot see the other server nor any of the other
> client machines.

Set DHCP to give 192.168.6.x boxes a default route to server A.
Set DHCP to give 192.168.6.x boxes a default route to server B.

on server A:
route add -net 192.168.7.0 gw serverB_192.168.5.x_IP
echo 1 > /proc/sys/net/ipv4/ip_forward

on server B:
route add -net 192.168.6.0 gw serverA_192.168.5.x_IP
echo 1 > /proc/sys/net/ipv4/ip_forward

Note: You might need to include the device that leads to the other network
at the end of the route command (like: dev eth1). If the above tests
successfully, there are likely settings in your network scripts that could
make it more permanent (automatic during boot).

If you have single point internet access, put that on 192.168.5.x network
and give each of server A and server B a default route to it. However, it
may be more involve than that is it cannot be configured to route to your
A and B networks.

--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/
http://cgi-help.virtualave.net/ http://hammer.prohosting.com/~cgi-wiz/

David Efflandt wrote:
> On Wed, 16 Jul 2003, Matt Fuerst <(E-Mail Removed)> wrote:
>
>>Hi all,
>>
>>Thanks in advance for any and all advice. This is a relatively simple setup,
>>so I hope this is a nerf toss.
>>
>>We are replacing our existing servers and network with a Linux network. We
>>currently have a large number of segments and a poorly designed system we
>>are hoping to streamline. Our proposed system is a follows.
>>
>>Two Servers, Server A and Server B. Server A is a file server for Group A,
>>Server B is a file server for Group B (two portions of the same building).
>>Server B is also running a DHCP server and Server A is running DHCP relay to
>>get IP addresses from Server B.
>>
>>Server A has two ethernet cards, IP addresses 192.168.5.X ("Server" segment)
>>and 192.168.6.X ("Client" segment) and Server B has IP addresses 192.168.5.X
>>and 192.168.7.X. So a Client on A segment gets assigned a 192.168.6.X
>>address and a client on B segment gets assigned a 192.168.7.X. All fine and
>>dandy so far?
>>
>>Clients on B can see Server B and it's 192.168.7.X IP address fine, and can
>>ping it's other address fine as well, the 192.168.5.X one. However, the
>>routing stops there, and it cannot see the other server nor any of the other
>>client machines.
>
>
> Set DHCP to give 192.168.6.x boxes a default route to server A.
> Set DHCP to give 192.168.6.x boxes a default route to server B.
>
> on server A:
> route add -net 192.168.7.0 gw serverB_192.168.5.x_IP
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> on server B:
> route add -net 192.168.6.0 gw serverA_192.168.5.x_IP
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> Note: You might need to include the device that leads to the other network
> at the end of the route command (like: dev eth1). If the above tests
> successfully, there are likely settings in your network scripts that could
> make it more permanent (automatic during boot).
>
> If you have single point internet access, put that on 192.168.5.x network
> and give each of server A and server B a default route to it. However, it
> may be more involve than that is it cannot be configured to route to your
> A and B networks.
>


OSPF much easier and scalable.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQE/Fe3wi6NlI+CoSzsRAnZXAKCCjiXIswyaMjw2i1QoJRGowmBTJg CgwdZW
ku/idmaY41GuTSLKFWZAQnM=
=/IPE
-----END PGP SIGNATURE-----