> I think the problem is probably the routing tables in the other boxes > in the same LAN (e.g. 10.255.250.38) route in 10.255.250.38: Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 10.255.250.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 default 10.255.250.37 0.0.0.0 UG 0 0 0 eth0 traceroute -n 172.17.1.50 (from 10.255.250.38): traceroute to 172.17.1.50 (172.17.1.50), 30 hops max, 40 byte packets 1 10.255.250.37 0.194 ms 0.124 ms 0.120 ms 2 195.39.130.92 3000.438 ms !H 3000.449 ms !H 3000.427 ms !H The request comes to the LAN default GW and fells through to its default GW eth0 leading to Internet, instead of going to eth3 :(( Thank you... jh > ------------ Původní zpráva ------------ > Od: Andrew Haley <aph@xxxxxxxxxx> > Předmět: Re: Routing problems > Datum: 18.2.2010 13:08:00 > ---------------------------------------- > On 02/18/2010 11:56 AM, j.halifax . wrote: > >> Please post > >> * Full details of your network > >> * The routing table, uncensored :) > > Hmm, this is a remarkable plate of spaghetti. > > I think the problem is probably the routing tables in the other boxes > in the same LAN (e.g. 10.255.250.38) > > Andrew. > > > > route > > Destination Gateway Genmask Flags Metric Ref Use Iface > > 192.168.180.0 * 255.255.255.0 U 0 0 0 > eth3 > > 10.200.1.0 10.255.250.250 255.255.255.0 UG 0 0 0 eth2 > > 195.39.130.0 * 255.255.255.0 U 0 0 0 > eth0 > > 10.1.1.0 10.255.250.250 255.255.255.0 UG 0 0 0 eth2 > > 10.201.1.0 10.255.250.250 255.255.255.0 UG 0 0 0 eth2 > > 10.255.250.0 * 255.255.255.0 U 0 0 0 > eth2 > > link-local * 255.255.0.0 U 1003 0 > 0 eth0 > > link-local * 255.255.0.0 U 1004 0 > 0 eth2 > > link-local * 255.255.0.0 U 1005 0 > 0 eth3 > > 172.17.0.0 192.168.180.100 255.255.0.0 UG 0 0 0 eth3 > > 192.168.0.0 192.168.180.100 255.255.0.0 UG 0 0 0 eth3 > > default pc89.n 0.0.0.0 UG 0 0 > 0 eth0 > > > > ifconfig > > eth0 Link encap:Ethernet HWaddr 00:1B:11:B1:5D:0D > > inet addr:195.39.130.92 Bcast:195.39.130.255 Mask:255.255.255.0 > > inet6 addr: fe80::21b:11ff:feb1:5d0d/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:5174154 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:3474632 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:2851269308 (2.6 GiB) TX bytes:646868735 (616.9 MiB) > > Interrupt:21 Base address:0xca00 > > > > eth2 Link encap:Ethernet HWaddr 00:19:5B:38:B7:36 > > inet addr:10.255.250.37 Bcast:10.255.250.255 Mask:255.255.255.0 > > inet6 addr: fe80::219:5bff:fe38:b736/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:18187178 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:2506338 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:1585335954 (1.4 GiB) TX bytes:1901082841 (1.7 GiB) > > Interrupt:22 Base address:0xa900 > > > > eth3 Link encap:Ethernet HWaddr 00:1B:11:B1:1C:D4 > > inet addr:192.168.180.100 Bcast:192.168.180.255 > Mask:255.255.255.0 > > inet6 addr: fe80::21b:11ff:feb1:1cd4/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:2048995 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4746 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:201714109 (192.3 MiB) TX bytes:364982 (356.4 KiB) > > Interrupt:18 Base address:0x6800 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > RX packets:255570 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:255570 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:25105805 (23.9 MiB) TX bytes:25105805 (23.9 MiB) > > > > Thanx. :) > > > > > >> ------------ Povodní zpráva ------------ > >> Od: Andrew Haley <aph@xxxxxxxxxx> > >> PYedmt: Re: Routing problems > >> Datum: 18.2.2010 12:31:34 > >> ---------------------------------------- > >> On 02/18/2010 11:19 AM, j.halifax . wrote: > >>>> What is the address of the subnet "other LAN" ? > >>>> There seem to be two more subnets, 192.168.180.0 and 172.17.0.0. > >>> You are right, both of them are accessible through eth3 and the same > >>> box of 192.168.180.100 (I didn't include the whole routing table) like: > >>> 172.17.0.0 192.168.180.100 255.255.0.0 UG 0 0 0 eth3 > >>> 192.168.0.0 192.168.180.100 255.255.0.0 UG 0 0 0 eth3. > >> > >> Please post > >> > >> * Full details of your network > >> * The routing table, uncensored > >> > >>>> ------------ Povodní zpráva ------------ > >>>> Od: Andrew Haley <aph@xxxxxxxxxx> > >>>> PYedmt: Re: Routing problems > >>>> Datum: 18.2.2010 11:51:17 > >>>> ---------------------------------------- > >>>> On 02/18/2010 10:01 AM, Rick Sewill wrote: > >>>>> On Thu, 2010-02-18 at 07:31 +0100, j.halifax . wrote: > >>>>>> Hi All, > >>>>>> > >>>>>> Could you please help me with routing in the LAN default GW box? > >>>>>> > >>>>>> I have > >>>>>> eth0 connected to Internet > >>>>>> eth2 to internal LAN 10.255.250.0 > >>>>>> LAN default GW is 10.255.250.37 > >>>>>> eth3 connected to other LAN > >>>> > >>>> What is the address of the subnet "other LAN" ? > >>>> > >>>> There seem to be two more subnets, 192.168.180.0 and 172.17.0.0. > >>>> > >>>> Andrew. > >>>> > >>>> > >>>> > >>>>>> Route in the default GW (10.255.250.37): > >>>>>> > >>>>>> Destination Gateway Genmask Flags Metric Ref > Use > >>>> Iface > >>>>>> 192.168.180.0 * 255.255.255.0 U 0 0 > > >> > >>>> 0 eth3 > >>>>>> 10.255.250.0 * 255.255.255.0 U 0 0 > > >> > >>>> 0 eth2 > >>>>>> link-local * 255.255.0.0 U 1003 > > >> 0 > >>>> 0 eth0 > >>>>>> link-local * 255.255.0.0 U 1004 > > >> 0 > >>>> 0 eth2 > >>>>>> link-local * 255.255.0.0 U 1005 > > >> 0 > >>>> 0 eth3 > >>>>>> 172.17.0.0 192.168.180.100 255.255.0.0 UG 0 0 > 0 > >> > >>>> eth3 > >>>>>> default dsl-router 0.0.0.0 UG 0 > > >> 0 > >>>> 0 eth0 > >>>>>> > >>>>>> >From the LAN default GW (10.255.250.37) > >>>>>> - I can ping 172.17.1.50: > >>>>>> PING 172.17.1.50 (172.17.1.50) 56(84) bytes of data. > >>>>>> 64 bytes from 172.17.1.50: icmp_seq=1 ttl=253 time=5.62 ms > >>>>>> 64 bytes from 172.17.1.50: icmp_seq=2 ttl=253 time=3.29 ms > >>>>>> > >>>>>> >From other boxes in the same LAN (e.g. 10.255.250.38) > >>>>>> - I cann't ping 172.17.1.50 > >>>>>> - I cann't traceroute 172.17.1.50: It goes to LAN default GW > >>>>>> 10.255.250.37 and then to its default GW dsl-router on eth0 > >>>>>> instead of eth3 (so that the routing rule for 172.17.0.0 > >> doesn't > >>>> > >>>>>> match for 172.17.1.50) > >>>>>> > >>>>>> Can anybody help pleasee? > >>>>>> Thank you so much! > >>>>>> jh > >>>>>> > >>>>> > >>>>> Your problem has me stumped. > >>>>> > >>>>> The only thing I can think of is to ask how iptables is set up. > >>>>> > >>>>> I think you have iptables doing masquerading to the eth0 interface. > >>>>> The masquerading shouldn't be the problem. > >>>>> > >>>>> Are you doing anything special with packets coming in eth2 in iptables? > >>>>> > >>>>> I assume 10.255.250.38 can ping the Internet so you have routing set up. > >>>>> > >>>>> I can't think of anything else to check at this moment. > >>>>> > >>>>> Hopefully others will have better suggestions and ideas where to look. > >>>>> > >>>>> > >>>>> > >>>> > >>>> -- > >>>> users mailing list > >>>> users@xxxxxxxxxxxxxxxxxxxxxxx > >>>> To unsubscribe or change subscription options: > >>>> https://admin.fedoraproject.org/mailman/listinfo/users > >>>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > >>>> > >>>> > >>>> > >> > >> -- > >> users mailing list > >> users@xxxxxxxxxxxxxxxxxxxxxxx > >> To unsubscribe or change subscription options: > >> https://admin.fedoraproject.org/mailman/listinfo/users > >> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > >> > >> > >> > > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > > -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
