Re: [leaf-wisp] Interesting routing problem
Vladimir Ivashchenko <[email protected]>
| Newsgroups | gmane.linux.leaf.wisp-dist |
|---|---|
| Message-ID | <[email protected]> |
And to what is 67.65.229.254 connected? I see that interface is missing in DEFAULT_GW, it should be something like "67.65.229.254 dev ath0" Gerry Weaver wrote about "RE: [leaf-wisp] Interesting routing problem": > Hi, > > It is from the CPE. > > Here's the one from the Test Client machine. > > c:\>tracert 151.164.1.8 > > Tracing route to dns1.rcsntx.sbcglobal.net [151.164.1.8] > over a maximum of 30 hops: > > 1 <10ms <10ms <10ms 67.65.229.11 > 2 67.65.229.11 reports: Destination host unreachable > > Trace complete. > > c:\> > > Thanks, > Gerry > > > -----Original Message----- > From: Vladimir Ivashchenko [mailto:[email protected]] > Sent: Sunday, February 29, 2004 4:33 PM > To: Gerry Weaver > Cc: Leaf-Wisp-Dist > Subject: Re: [leaf-wisp] Interesting routing problem > > > This is a traceroute from where? > > Gerry Weaver wrote about "RE: [leaf-wisp] Interesting routing problem": > > Hi, > > > > Here you go. > > > > # traceroute 151.164.1.8 > > traceroute to 151.164.1.8 (151.164.1.8), 30 hops max, 40 byte packets > > 1 67.65.229.11 (67.65.229.11) 3000.73 ms !H 2999.56 ms !H 2999.64 ms > !H > > > > Thanks, > > Gerry > > > > -----Original Message----- > > From: Vladimir Ivashchenko [mailto:[email protected]] > > Sent: Sunday, February 29, 2004 3:47 PM > > To: Gerry Weaver > > Subject: Re: [leaf-wisp] Interesting routing problem > > > > > > Try doing a traceroute to an external IP and send me its output. > > > > Gerry Weaver wrote about "RE: [leaf-wisp] Interesting routing problem": > > > Hi, > > > > > > Okay... I've gotten a little farther. I've had to change up the ip > > addresses > > > to test internet access. > > > > > > Current setup: > > > > > > Test Client: 67.65.229.2 <==> CPE: eth0(67.65.229.11) ath0(67.65.229.11) > > > <==> AP: ath0(67.65.229.12) eth0(67.65.229.12) > > > > > > The default gateway on the Test Client, CPE, and AP is 67.65.229.254 > > > > > > Results: > > > > > > I can ping everything on the 67.65.229.0 network > > > > > > I can't ping any address outside of the 67.65.229.0 network from either > > the > > > Test Client or the CPE > > > > > > I can ping the internet from the AP > > > > > > Additional Data: > > > > > > [AP] > > ====================================================================== > > > > > > BR_IFACES="eth0 ath0 " > > > br0_IPADDR="67.65.229.12/24" > > > ENABLE_L2_BRIDGING="no" > > > ENABLE_PARP_BRIDGING="yes" > > > IFACES="eth0 ath0 " > > > eth0_IPADDR="67.65.229.12/24" > > > DEFAULT_GW="67.65.229.254" > > > ath0_IPADDR="67.65.229.12/24" > > > > > > > -------------------------------------------------------------------------- > > -- > > > > > > # ip addr > > > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > > inet 127.0.0.1/8 scope host lo > > > 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop > > > link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff > > > 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > > > link/ether 00:00:24:c1:e1:c4 brd ff:ff:ff:ff:ff:ff > > > inet 67.65.229.12/24 scope global eth0 > > > 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100 > > > link/ether 00:00:24:c1:e1:c5 brd ff:ff:ff:ff:ff:ff > > > 5: ath0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 199 > > > link/ether 00:02:6f:20:1c:5b brd ff:ff:ff:ff:ff:ff > > > inet 67.65.229.12/24 scope global ath0 > > > > > > > -------------------------------------------------------------------------- > > - > > > > > > > > > # ip route > > > 169.254.142.7 dev eth0 scope link metric 50 > > > 169.254.113.17 dev eth0 scope link metric 50 > > > 169.254.252.42 dev eth0 scope link metric 50 > > > 169.254.14.146 dev eth0 scope link metric 50 > > > 169.254.31.42 dev eth0 scope link metric 50 > > > 67.65.229.69 dev eth0 scope link metric 50 > > > 169.254.8.101 dev eth0 scope link metric 50 > > > 169.254.183.132 dev eth0 scope link metric 50 > > > 169.254.55.246 dev eth0 scope link metric 50 > > > 169.254.171.226 dev eth0 scope link metric 50 > > > 67.65.229.2 dev ath0 scope link metric 50 > > > 169.254.119.53 dev eth0 scope link metric 50 > > > 67.65.229.3 dev eth0 scope link metric 50 > > > 169.254.37.65 dev eth0 scope link metric 50 > > > 169.254.220.128 dev eth0 scope link metric 50 > > > 169.254.58.136 dev eth0 scope link metric 50 > > > 169.254.186.2 dev eth0 scope link metric 50 > > > 169.254.89.19 dev eth0 scope link metric 50 > > > 169.254.225.202 dev eth0 scope link metric 50 > > > 169.254.212.223 dev eth0 scope link metric 50 > > > 169.254.6.251 dev eth0 scope link metric 50 > > > 169.254.137.69 dev eth0 scope link metric 50 > > > 169.254.20.91 dev eth0 scope link metric 50 > > > 169.254.145.133 dev eth0 scope link metric 50 > > > 169.254.132.202 dev eth0 scope link metric 50 > > > 169.254.171.78 dev eth0 scope link metric 50 > > > 169.254.232.243 dev eth0 scope link metric 50 > > > 169.254.115.252 dev eth0 scope link metric 50 > > > 169.254.151.196 dev eth0 scope link metric 50 > > > 169.254.35.207 dev eth0 scope link metric 50 > > > 67.65.229.11 dev ath0 scope link metric 50 > > > 169.254.240.117 dev eth0 scope link metric 50 > > > 169.254.37.27 dev eth0 scope link metric 50 > > > 169.254.233.40 dev eth0 scope link metric 50 > > > 67.65.229.254 dev eth0 scope link metric 50 > > > 67.65.229.0/24 dev eth0 proto kernel scope link src 67.65.229.12 > > > 67.65.229.0/24 dev ath0 proto kernel scope link src 67.65.229.12 > > > default via 67.65.229.254 dev eth0 > > > > > > > [CPE]==================================================================== > > > > > > br0_IPADDR="67.65.229.11/24" > > > BR_IFACES="eth0 ath0 " > > > ENABLE_L2_BRIDGING="no" > > > ENABLE_PARP_BRIDGING="yes" > > > DEFAULT_GW="67.65.229.254" > > > eth0_IPADDR="67.65.229.11/24" > > > IFACES="eth0 ath0 " > > > ath0_IPADDR="67.65.229.11/24" > > > > > > > -------------------------------------------------------------------------- > > > > > > # ip addr > > > 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue > > > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > > > inet 127.0.0.1/8 scope host lo > > > 2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop > > > link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff > > > 3: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100 > > > link/ether 00:00:24:c1:80:90 brd ff:ff:ff:ff:ff:ff > > > inet 67.65.229.11/24 scope global eth0 > > > 4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100 > > > link/ether 00:00:24:c1:80:91 brd ff:ff:ff:ff:ff:ff > > > 5: ath0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 199 > > > link/ether 00:02:6f:20:1c:73 brd ff:ff:ff:ff:ff:ff > > > inet 67.65.229.11/24 scope global ath0 > > > > > > > -------------------------------------------------------------------------- > > - > > > > > > # ip route > > > 169.254.142.7 dev ath0 scope link metric 50 > > > 169.254.113.17 dev ath0 scope link metric 50 > > > 169.254.252.42 dev ath0 scope link metric 50 > > > 169.254.14.146 dev ath0 scope link metric 50 > > > 169.254.31.42 dev ath0 scope link metric 50 > > > 67.65.229.69 dev ath0 scope link metric 50 > > > 169.254.8.101 dev ath0 scope link metric 50 > > > 169.254.183.132 dev ath0 scope link metric 50 > > > 169.254.55.246 dev ath0 scope link metric 50 > > > 169.254.171.226 dev ath0 scope link metric 50 > > > 67.65.229.2 dev eth0 scope link metric 50 > > > 169.254.119.53 dev ath0 scope link metric 50 > > > 67.65.229.3 dev ath0 scope link metric 50 > > > 169.254.37.65 dev ath0 scope link metric 50 > > > 169.254.220.128 dev ath0 scope link metric 50 > > > 169.254.58.136 dev ath0 scope link metric 50 > > > 169.254.186.2 dev ath0 scope link metric 50 > > > 169.254.89.19 dev ath0 scope link metric 50 > > > 169.254.225.202 dev ath0 scope link metric 50 > > > 169.254.212.223 dev ath0 scope link metric 50 > > > 169.254.6.251 dev ath0 scope link metric 50 > > > 169.254.137.69 dev ath0 scope link metric 50 > > > 169.254.20.91 dev ath0 scope link metric 50 > > > 169.254.145.133 dev ath0 scope link metric 50 > > > 169.254.132.202 dev ath0 scope link metric 50 > > > 67.65.229.12 dev ath0 scope link metric 50 > > > 169.254.171.78 dev ath0 scope link metric 50 > > > 169.254.232.243 dev ath0 scope link metric 50 > > > 169.254.115.252 dev ath0 scope link metric 50 > > > 169.254.151.196 dev ath0 scope link metric 50 > > > 169.254.35.207 dev ath0 scope link metric 50 > > > 169.254.240.117 dev ath0 scope link metric 50 > > > 169.254.37.27 dev ath0 scope link metric 50 > > > 169.254.233.40 dev ath0 scope link metric 50 > > > 67.65.229.254 dev ath0 scope link metric 50 > > > 67.65.229.0/24 dev eth0 proto kernel scope link src 67.65.229.11 > > > 67.65.229.0/24 dev ath0 proto kernel scope link src 67.65.229.11 > > > default via 67.65.229.254 dev eth0 > > > > > > > > > > > > -----Original Message----- > > > From: Vladimir Ivashchenko [mailto:[email protected]] > > > Sent: Sunday, February 29, 2004 7:44 AM > > > To: Gerry Weaver > > > Cc: Leaf-Wisp-Dist > > > Subject: Re: [leaf-wisp] Interesting routing problem > > > > > > > > > Gerry, > > > > > > The default gateway should be 11.11.11.254 everywhere. > > > > > > Also, I suggest to use IPs from 11.11.11.0/24 range on ath0 if > > > you want to be able to check connectivity from the WISP-Dist > > > units themselves. > > > > > > Gerry Weaver wrote about "RE: [leaf-wisp] Interesting routing problem": > > > > > > > Hi Vladimir, > > > > > > > > I have not been able to get layer 3 bridging to work. The setup is > > below. > > > > > > > > CPE: eth0(11.11.11.1) ath0(10.10.10.1) <===========> AP: > > ath0(10.10.10.2) > > > > eth0(11.11.11.2) > > > > > > > > I can ping the AP address (10.10.10.2) from the CPE > > > > I can ping the CPE address (10.10.10.1) from the AP > > > > I cannot ping anything on the 11.11.11.0/24 network > > > > > > > > I have tried various default gateways for each side. No matter what it > > > will > > > > not pass the traffic. > > > > 10.10.10.1 and 10.10.10.2 respectively > > > > 11.11.11.1 and 11.11.11.2 respectively > > > > 11.11.11.254 (T1 router) > > > > > > > > Nothing seems to work. Any thoughts? > > > > > > > > Thanks, > > > > Gerry > > > > > > > > > > > > -----Original Message----- > > > > From: Vladimir Ivaschenko [mailto:[email protected]] > > > > Sent: Saturday, February 28, 2004 3:13 PM > > > > To: Gerry Weaver > > > > Cc: Leaf-Wisp-Dist > > > > Subject: Re: [leaf-wisp] Interesting routing problem > > > > > > > > > > > > Gerry, > > > > > > > > If the addresses are unused, why do you want to route them? > > > > > > > > As soon as new machine is inserted, layer 3 bridging code will "see" > it. > > > > > > > > Gerry Weaver wrote: > > > > > Hi Vladimir, > > > > > > > > > > Sorry.. What I meant was the range of ip addresses that were not in > > use > > > > per > > > > > "2." below. I guess I don't really care what method is used to get > the > > > > thing > > > > > working. The best solution would be if the point to point link were > a > > > > > transparent bridge. This would be a lot simpler. Have you, or anyone > > > else, > > > > > been able to get a link working that way? > > > > > > > > > > BTW: I'm nearing completion on the network config library for the > > > command > > > > > line interface. I'll send it to you for your review when the code is > > > > > complete. > > > > > > > > > > > > > > > Thanks, > > > > > Gerry > > > > > > > > > > -----Original Message----- > > > > > From: Vladimir Ivaschenko [mailto:[email protected]] > > > > > Sent: Friday, February 27, 2004 3:48 AM > > > > > To: Gerry Weaver > > > > > Cc: Leaf-Wisp-Dist > > > > > Subject: Re: [leaf-wisp] Interesting routing problem > > > > > > > > > > > > > > > > > > > > What do you mean by "full block of available addresses"? > > > > > > > > > > Another alternative is to VTUN. It will allow you to setup an > Ethernet > > > > > tunnel between two boxes. The drawback is the overhead (each > Ethernet > > > > > frame will be encapsulated into IP packet). > > > > > > > > > > Gerry Weaver wrote: > > > > > > > > > >>Hello All, > > > > >> > > > > >>I have come across a bit of a routing challenge. I need to do a > point > > to > > > > >>point link with 2 wisp-dist boxes. Here are the specifics. > > > > >> > > > > >>1. The wireless nics in the wisp-dist boxes do not support > promiscuous > > > > > > > > > > mode > > > > > > > > > >>making a layer 2 bridge impossible. > > > > >>2. The network currently has x.x.x.1-x.x.x.10 and > x.x.x.250-x.x.x.254 > > in > > > > >>use. > > > > >>3. The CPEs are getting addresses via dhcp within the available > range. > > > > >> > > > > >>I would like to setup a proxy arp bridge, but I need to route the > full > > > > > > > > > > block > > > > > > > > > >>of available addresses. The wisp-dist boxes need to act as a > > transparent > > > > >>bridge. I assume I could set up subnet for the three blocks of > > > addresses, > > > > >>but I'm no routing wizard. Does anyone have any suggestions? > > > > >> > > > > >>Thanks in advance, > > > > >>Gerry > > > > >>--- > > > > >>Outgoing mail is certified Virus Free. > > > > >>Checked by AVG anti-virus system (http://www.grisoft.com). > > > > >>Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > >> > > > > >> > > > > >> > > > > >>------------------------------------------------------- > > > > >>SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > >>Build and deploy apps & Web services for Linux with > > > > >>a free DVD software kit from IBM. Click Now! > > > > >>http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > >>_______________________________________________ > > > > >>leaf-wisp-dist mailing list > > > > >>[email protected] > > > > >>https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > >> > > > > > > > > > > > > > > > > > > > > -- > > > > > Best Regards, > > > > > Vladimir Ivashchenko > > > > > ThunderWorx - www.thunderworx.com > > > > > Senior Systems Designer/Engineer > > > > > > > > > > > > > > > --- > > > > > Incoming mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > > > > > > > --- > > > > > Outgoing mail is certified Virus Free. > > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > > > > > Build and deploy apps & Web services for Linux with > > > > > a free DVD software kit from IBM. Click Now! > > > > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > > > > > _______________________________________________ > > > > > leaf-wisp-dist mailing list > > > > > [email protected] > > > > > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist > > > > > > > > > > > > > > > > > -- > > > > Best Regards, > > > > Vladimir Ivashchenko > > > > ThunderWorx - www.thunderworx.com > > > > Senior Systems Designer/Engineer > > > > > > > > > > > > --- > > > > Incoming mail is certified Virus Free. > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > > > > > --- > > > > Outgoing mail is certified Virus Free. > > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > > > > > > > -- > > > Best Regards, > > > Vladimir Ivashchenko > > > ThunderWorx - www.thunderworx.com > > > Senior Systems Designer/Engineer > > > > > > --- > > > Incoming mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > > > --- > > > Outgoing mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > > > > -- > > Best Regards, > > Vladimir Ivashchenko > > ThunderWorx - www.thunderworx.com > > Senior Systems Designer/Engineer > > > > --- > > Incoming mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > -- > Best Regards, > Vladimir Ivashchenko > ThunderWorx - www.thunderworx.com > Senior Systems Designer/Engineer > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.576 / Virus Database: 365 - Release Date: 1/30/2004 > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > leaf-wisp-dist mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist -- Best Regards, Vladimir Ivashchenko ThunderWorx - www.thunderworx.com Senior Systems Designer/Engineer ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click