[Gllug] Numpty Networking

[Darren Beale]

Hi and thanks for all of the replies.

> Somthing puzzles me, if all you want to do is hool to LANs together via a
> router why do you need 2 machines?

good question, I've now ditched the second machine

> assuming the following.:-
>
> Network A 10.0.1.0/24
> Network B 10.0.6.0/24

check

> eth0 - connected to network A
> eth1 - connected to network B

check

> ifconfig eth0 10.0.1.110 netmask 255.255.255.0
> ifconfig eth1 10.0.6.101 netmask 255.255.255.0
> echo 1 > /proc/sys/net/ipv4/ip_forward

check (I've used 10.0.6.2)

> new inform the machines on the B side that 10.0.6.101 is thier route to
> 10.0.1.0/24 by doing:-
> route add -net 10.0.1.0 netmask 255.255.255.0 gw 10.0.6.101

I only want to go A -> B so I've not done this

> and the same for A machines

> route add -net 10.0.6.0 netmask 255.255.255.0 gw 10.0.1.110

check

Here is my status:

1) The bridge machine can ping machines on both 10.0.1.0/24 and 10.0.6.0/24

2) a traceroute to an external machine from the bridge machine shows
that it goes via the A networks' default gw, this is correct

3) Machines on A can ping the B interface 10.0.6.2

4) Machines on A CANNOT ping any other machines on the B network

5)  /proc/sys/net/ipv4/ip_forward contains a 1 on the bridge machine

I'm guess it's something subtle that I've missed, but I can't see
what, here is the routing table on the bridge machine FWIW

flump:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.6.0        0.0.0.0         255.255.255.0   U     0      0        0 eth1
10.0.1.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0        0 eth0

any ideas?

regs
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug