Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Re: routing question
- Date: Sun, 27 Jun 2004 17:16:41 +0900
- From: Botond Botyanszki <tlug@example.com>
- Subject: Re: [tlug] Re: routing question
- References: <20040626195119.5450ddc0.tlug@example.com><20040626110829.GA30783@example.com><20040626205150.7e11be74.tlug@example.com><20040626120306.GB30950@example.com><20040626214921.5ad8fb7f.tlug@example.com><20040626200700.GD13647@example.com>
- Organization:
On Sat, 26 Jun 2004 22:07:03 +0200 Tobias Diedrich <ranma@example.com> wrote: > > +-------------------------------------> > > | <----------------------------------+ > > firewall laptop eth0 laptop usb0 zaurus usbd0 > > 192.168.1.1 <--> 192.168.2.12 <--> 192.168.129.1 <--> 192.168.129.201 > > > The machine with IP 192.168.2.1 or its default gw needs to know that it > has to route packets destined to 192.168.129.201 over your notebook. I did set that route. It seems to me (from tcpdump output) that packages are not beeing routed between the eth0 and usb0 interfaces on the laptop for some reason. Am I missing something from the kernel? Now I changed the laptop to 192.168.1.12 to avoid further confusion and problems but that was not related I think. > You can avoid fiddling with the other routing tables by masquerading the > packets from your zaurus on your notebook. Tried this, didn't help. > A packet sniffer like ethereal or tcpdump is a good tool to check where > the packets get stuck. Pinging the usb0 interface on the laptop and doing a "tcpdump -i eth0" shows that ping is OK. siliconium > 192.168.129.1: icmp: echo request (DF) (ttl 64, id 1, len 84) 192.168.129.1 > siliconium: icmp: echo reply (ttl 64, id 44801, len 84) Pinging the usbd0 interface on the zaurus and doing a"tcpdump-i eth0" on the laptop shows only the requests but no reply: siliconium > zaurus: icmp: echo request (DF) (ttl 64, id 2, len 84) siliconium > zaurus: icmp: echo request (DF)(ttl 64, id 3, len 84) if I ping the laptop's eth0(!) interface from the zaurus, the ping is OK. # tcpdump -i usb0 192.168.129.201 > 192.168.1.12: icmp: echo request (DF) 192.168.1.12 > 192.168.129.201: icmp: echo reply # ifconfig eth0 Link encap:Ethernet HWaddr 08:00:46:05:63:69 inet addr:192.168.1.12 Bcast:192.168.2.255 Mask:255.255.255.0 "tcpdump -i eth0" gives no output. Why? Just to try something else, I set up PPP over irda between the zaurus and the laptop. Ditto the same. Communication between to two machines over the irda connection is fine but no luck reaching other hosts. PPP via modem works on this laptop with a dialin ISP. I'll just pull the ethernet cable and hang myself with it... > Sometimes enabling logging of martians and > disabling the reverse path filter can also help debugging complicated > setups (/proc/sys/net/ipv4/conf/*/(rp_filter|log_martians)). Thanks, I'll look at this.
- Follow-Ups:
- Re: [tlug] Re: routing question
- From: uvacoder
- [tlug] Re: routing question
- From: Tobias Diedrich
- References:
- [tlug] routing question
- From: Botond Botyanszki
- Re: [tlug] routing question
- From: uvacoder
- Re: [tlug] routing question
- From: Botond Botyanszki
- Re: [tlug] routing question
- From: uvacoder
- Re: [tlug] routing question
- From: Botond Botyanszki
- [tlug] Re: routing question
- From: Tobias Diedrich
Home | Main Index | Thread Index
- Prev by Date: Re: [tlug] routing question
- Next by Date: Re: [tlug] Re: routing question
- Previous by thread: [tlug] Re: routing question
- Next by thread: Re: [tlug] Re: routing question
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links