bridging on the client side

[dkii]

is there anything wrong with routing at the AP, but bridging 2 wireless cards on the client side? Reason I ask is I'm all for routing, but several of our customers want a local wireless to cover their house as well, since we will have a soekris there anyways, we can just plug another card into it, but I don't want to waste another subnet for their local coverage, so I want to bridge the local wireless client card to the other local card, running in AP mode. Just want to make sure I'm not going to run into problems down the road.

[tony]

It's not ideal, but should work with little problem.

Thanks!

[bobbyc]

I'm still trying to learn networking (i'm not the sys adm), but we have a customer who lives on top of a hill and let us put a tower up in trade for free internet. We strung cat5 from the starOS to his hub which is in turn plugged into his XP machine where the VPN client is done and he has ICS enabled on the vpn... that way his other computers in his house that are plugged into the hub can share the internet.
In this case, the tower gets it's backhaul from the sector of the other tower (10.8.3.2, 255.255.255.0) We gave the backhaul card a ip of 10.8.3.7.
Then we gave the sector antennas their IPs and the NIC card 10.8.17.2, 255.255.255.0. We set the route 0.0.0.0, 0.0.0.0, 10.8.3.2
It's ok to have the guy on the hill on the same subnet as the wireless, and all the other sectors the same subnet as our other towers?
Bob C

[lonnie]

It will work but you should not have customers on your backbone. Leave it this way until you learn enough routing to move them to their own subnet.

All you need is one of your customers to pull an IP out of thin air that matches a key IP on your backbone and you are dead. If you route them their own subnet, they cannot hurt you. The worst they can do is whack their own connection but they cannot cross your router and contaminate anything else.

[dkii]

hmm... I see what you mean. I had some problems with it today anyways. When I first went to the site, I could not access the local staros box(x.x.5.10) I could surf and talk to my main AP fine (x.x.5.1) the main AP reported the IP address of the associated client card as 2.240, which is the IP address of my laptop. I got into the local box via one of the ethernet ports, and once I activated changes, everything was fine. I could talk to it via the wireless again. I went ahead and set up dhcp on our main AP. I haven't tried associating my laptop with it directly, but when I link to the local staros box, it almost doesn't give me an IP address, it goes through the entire wait period, then times out and gives me a 169 address. Within 5 secs of getting the 169 address, it grabs the right IP. This is on a 2000 machine. I tried it with a 98 machine and it wouldn't get anything but a 169. I tried turning on dhcp relay, but it didn't work either. I think I know enough about routing to set everything up routed, but it just seems like a pain to me. Since these are my only 2 boxes, I might test out the rip2 and see how that works out.