1
I have the following configuration:
Routing table on M3 is:
Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth1 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.3.0 0.0.0.0 255.255.255.192 U 0 0 0 eth0
Routing table on M1 is:
Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
So basically M3's gateway is M1, and M1's gateway is M2's wireless internet interface. If I ping 8.8.8.8 from M1, everything is ok, replies are received. Pinging from M1 to M3 and viceversa is also possible.
I have configured M1 as gateway trafic forwarder using firestarter package and stopped firewall with it.
iptables policies are ACCEPT for everything.
Problem: I have tried ping-ing ip 8.8.8.8 from M3 but without success.
What could be the source of this problem?
Could you pls post M1's routing table, and state whether you can ping M1 from M3? – MariusMatutiae – 2013-10-27T21:00:25.317
@MariusMatutiae edited and added required information. – Andrew-George Hondrari – 2013-10-27T21:08:53.907
1Is that a typo where M1 and M2 have the same IP on the 192.168.2.x network? And which device has 192.168.0.1 - does it have a route for 192.168.2.x? – Paul – 2013-10-27T22:16:14.060
You should use tcpdump or wireshark on M1 to see where M3 pings disappear. – MariusMatutiae – 2013-10-27T22:28:48.557
@Paul, no, it's actually a bridged connection between the virtual machine and my laptop and I've configured both interfaces with that IP. 192.168.2.101 should have a route through switch->m3(192.168.2.1)->m1->m3(192.168.0.101)->wireless(192.168.0.1) – Andrew-George Hondrari – 2013-10-28T20:19:10.173
Sure but does the wireless router know about 192.168.2.x? – Paul – 2013-10-28T21:20:28.413
Well .. it should, M1 is configured as gateway. – Andrew-George Hondrari – 2013-10-30T21:57:43.283