Hi Brock, I still don't understand your setup. I don't exclude possibility that there can be a problem with the bridging itself, as the code for parproute is quite new. If you can send that Visio diagram to me... :-)
Regarding DHCP across the bridge - it will not work. DHCP is Layer 2 protocol, and the only bridging possible with non-Prism cards is Layer 3 (IP). Brock Nanson wrote about "Re: wisp-dist 2312, bridge, lucent": > Thanks for the response Vladimir! > > Put together a sketch with Visio that I was going to post... fired > everything up again tonight to pull the arp and route information and > another idea finally hit me. Surprisingly enough, it seems like the right > idea. ;-) > > It seems that having the wireless interfaces on another subnet really > messes things up! I'm guessing, but I think that selecting the default > gateway IP (on the wired subnet) creates problems when you try to select > netcs0 as the device to use to get there! Makes sense when you stop and > think about it. I put the wireless interfaces on the same subnet as the > wired and everything seems to be working close to correctly. Even tried > using the same IP as the wired card in each box and had the same success. > > I do have some new questions now however! > > 1) when I was having all the trouble I saw in ps ax that some sort of ping > function was running now and then. What is it and what does it do? > > 2) I can't seem to get a dynamic ip across the bridge. Should I be able > to? If so, where should I start to look given that the configuration is > pretty much 'out of the box' with the exception of the IP's, ESSID etc.? > > 3) My bering box has a third lucent card in it (besides the two in the > wisp boxes) using ad-hoc and channel 6. I put the wisp boxes on channel 1 > and found I was losing around 60% of my packets. Shutting down the card > on the bering box fixed the problem. But, I thought that channels 1, 6 > and 12 were far enough apart not to cause interference. Any thoughts? > > Thanks! I'm anxious to poke around this package a little more now that > the basics are going! > > Brock > > On Mon, 26 Aug 2002, Vladimir I. wrote: > > > Hi, > > > > Can you provide a small diagram (ASCII text is ok.. ) and a copy of routing > > table and ARP table contents? > > > > Brock Nanson wrote: > > > I've got two test boxes running 2312 and Lucent cards. After some trial and > > > error, the two will talk back and forth (192.168.100.0 subnet used for the > > > wireless cards) and I thought I was ready to get the bridging to work. > > > > > > The bridged network is 192.168.1.0 (/25 if that matters). I have a bering > > > box between the LAN and the Internet. I've set the bering box as the > > > default gateway on both wisp boxes. Both boxes have the gateway device set > > > as the 'closest' device to the bering gateway. So the local wisp uses eth0 > > > and the remote uses netcs0. > > > > > > I plugged a notebook into the 'remote' wisp box and can ping it > > > successfully. > > > > > > The wisp boxes have different IP's on all interfaces, on the subnets noted > > > above. In both cases, the eth0 port shows up as the default route for > > > 192.168.1.0/25. > > > > > > The problem I have is that the routing table seems to be updated > > > incorrectly... and I can't find what triggers the problem. Essentially, I > > > don't always get the route entry appearing with the correct interface. That > > > is, the remote wisp as an example will update the route table to use eth0 > > > for a target located on the other side of the bridge. It seems that if the > > > connection is initiated from the main LAN, the tables are configured > > > correctly. But if the notebook in the remote end initiates a connection, > > > the routing table is incorrect. I can manually change the table and have it > > > work, so the basics are there. > > > > > > I notice some occurrences in the arp table of the same IP twice, with the > > > second entry shown as "incomplete" if that helps. > > > > > > I'm betting I'm missing something simple here, but I can't see it! What > > > specific information can I provide to troubleshoot this? > > > > > > Thanks, > > > > > > Brock Nanson > > > Kamloops BC > > > Canada > > > > > > > > > > > -- > Brock Nanson > Kamloops BC Canada -- Best Regards, Vladimir Systems Engineer (RHCE) ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
