This bridge is not bridged with the ethernet.
What is strange to me is that the internet gateway has a bridge from the wireless mesh to the wireless access point. I have the ethernet interface acting as a static DHCP server so that I can connect my computer to it. I am able to access the internet through connecting with the wireless AP interface. When a new device is connected to the wireless AP, it's DHCP request I believe is forwarded to that internet gateway to pull in an IP. It receives an IP from the internet gateway just fine. The node B right now has a bridged wireless AP to bat0 and the bridge is in DHCP client mode. So you can static-IP them to what should be the best gateway based on where you initially site them. This use is limited and they don't necessarily need to be optimally configured for fast access, they could do it to a very distant gateway as long as the mesh stays intact. It should again be noted that the B nodes' link to the Internet is only for their internal use such as setting the time by NTP or downloading packages.
#Open mesh wired client never receives dhcp offer movie
If they now have a different public IP, the movie server will lose contact with them. This may or may not give them the same gateway they had before. As they move out of range of the B node that they originally connected to, their wifi STA will reconnect to a different B node and (usually) re-DHCP. If your mesh is also providing AP access, the situation is not good for a mobile user such as someone streaming a movie on their iPad as they walk through the mesh.
This is fine for wired clients, except if their A node goes down, they lose Internet access until they re-DHCP (usually manually) to find another A node. The gateway's DHCP server will then configure the user onto its layer 3 subnet and they will now always use that A node for their Internet access.
They all run a DHCP server and the BATMAN "gateway" flag is set on each one.īATMAN running on a B node will look at what it knows about neighbors in the mesh, in particular those gateway flags, and (layer 2) route DHCP requests from a new user to the closest gateway. Each of your independent gateways (A1, A2, etc.) will have a different LAN subnet so they don't conflict with each other. It doesn't care about IP addresses at all. Remember that BATMAN-adv works at layer 2. Looking at an entry-level approach to the second situation. The second situation is very complex and developers have worked on it for years with considerable debate over which method may be best. When you say "multiple gateways", will they all be connected (by some method outband of the mesh, such as Ethernet cables) ultimately to the same wan and public IP on the Internet? Or will they each have their own different ISP modem and a different link to the Internet?
0 kommentar(er)
