BridGing

back to http://scratchpad.wikia.com/wiki/Sasecurity

TableOfContents

BridgedAndRouted

{{{ Subject:       Re: [MeshAPuser] MeshAP as a bridge? Ryan, I suppose that you wish to put a MeshAP on one LAN, and a bridge on the other? Or, do you want to use MeshAP to MeshAP? I think you'll have to open up the firewall, but either way, it should work. If you have multiple AP's (one on each LAN), then you will have to enable cross mesh routing. If one LAN connects (with a bridge) the the MeshAP which is located on the other LAN, then you just need to have "same node clients firewalled" set to off. > Is it possible to use the meshbox to bridge to another WLAN?

=
Subject:       Re: [MeshAPuser] MeshAP as a bridge? What I want to do specificially is this: There is a wireless network in another building called NetworkA. The horrible powerbooks' antenna I have don't pick up any signal, kind of a joke really for how much I paid for these things. So I need something to act as a bridge so I can access NetworkA via the meshbox on all the powerbooks in my building. I have a DLINK bridge that works great. But it only works for one computer. I tried hooking an access point up to the DLINK bridge but I guess the regular AP is forwarding through MAC info and so I am still only able to get one laptop at a time to connect to NetworkA. I don't have a hardware router except for a WRT54G that I need to unbrick. Meshbox is the only hardware type router I have access to at the moment. I was hoping that I could use the meshbox to bridge wirelessly to NetworkA and then use eth0 on the meshbox for all my powerbooks to plug into via a switch. I'll call the powerbooks LAN NetworkB. This is only

Wireless bridge
Using the suggested setup we experience ethernet problems after a while. A 'straight' pc acting as a meshbox, a soekris board, any other unit we put there, comes with the same problem after a while. Setup is meshbox, wireless bridge plugged in the ethernet interface connected to another bridge about 900 m away. Everything works fine, but every few weeks or so the connection between meshbox and bridge fails due to a stoned ethernet port on the meshbox. There's *no* way we can get it to work - we have to reflash the cf card. I can ping the eth0 interface, but pings to other devices result in an extensive error report table, something I've seen before on an OpenBSD box when the media setting of the ethernet interface was wrong. Changing the media setting with the meshbox is no option though, it refuses. This has only happened with a wireless bridge---al other setups with meshboxes going directly to a wired gateway showed no problems. Any clues?

asdfas
 Wireless bridge to mesh eth0 BR How mesh configures itself as a gateway BR  QUES: BR     Using the suggested setup we experience ethernet problems after a BR while. A 'straight' pc acting as a meshbox, a soekris board, any other unit we BR put there, comes with the same problem after a while.BR Setup is meshbox, wireless bridge plugged in the ethernet interface BR connected to another bridge about 900 m away. Everything works fine, BR but every few weeks or so the connection between meshbox and bridge fails BR due to a stoned ethernet port on the meshbox. There's *no* way we can BR get it to work - we have to reflash the cf card. I can ping the eth0 BR interface, but pings to other devices result in an extensive error BR report table, something I've seen before on an OpenBSD box when the BR media setting of the ethernet interface was wrong. Changing the media BR setting with the meshbox is no option though, it refuses.BR This has only happened with a wireless bridge---al other setups with BR meshboxes going directly to a wired gateway showed no problems. Any BR clues? BR

ANSW: BR It's not the best way in the world to do so, but if you plug a bridge into the ethernet port of the MeshAP, if it pulls an ip address,  it should configure itself as a gateway. If dhcp is off on his system, you'll have to hardkey a static ip, but nevertheless it will gateway.

Were the MT Router is as a bridge, this gives us a lot of management on the connection for little £££. PS Pat did you get my last email about ADSL as I'm not 100% sure it made it to the list?

On one network I'm shepherding, the backhaul arrives via an SDSL modem, then goes into a router, then a server running a Checkpoint firewall, then into the gateway meshbox. It does so mostly because the meshbox replaced a legacy network which didn't have a firewall.

Would it be safe/wise to simply connect (CAT5) directly from the router to the meshbox. If I did this, how would I ssh to that meshbox rather than ssh'ing to the server and thence to the meshbox ?