Thanks Yeoh for suggestions.. I have mentioned about DHCP issue in my previous post.. Can you please see it?
Thanks. On Thu, Jul 21, 2016 at 6:01 PM, Yeoh Chun-Yeow <[email protected]> wrote: > Mesh gate is the mesh STA with external network access, such as IEEE > 802.3 Ethernet. > > Bridge interface should only have one IP address for all the bridged > interfaces. You seems to have one for mesh interface and one for > bridge interface. > > Please note that 802.11s is working on L2 level or MAC level, not IP. > > Suggest you take a look on this wiki: > https://github.com/o11s/open80211s/wiki/HOWTO > > You should able to find a lot of info there. > > Hope this help. > > --- > Chun-Yeow > > > On Thu, Jul 21, 2016 at 7:29 PM, Akshay Jindal > <[email protected]> wrote: > > What is the difference between mesh gate and bridge? > > > > > > Interfaces file: > > > > auto lo > > iface lo inet loopback > > > > iface eth0 inet manual > > > > allow-hotplug wlan0 > > iface wlan0 inet manual > > wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf > > > > allow-hotplug wlan1 > > iface wlan1 inet manual > > wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf > > > > > > I have manually assigned IP addresses to mesh nodes.. > > > > for example mesh5 (not mesh gate) > > > > ifconfig wlan0 down > > iw dev wlan0 interface add mesh5 type mp mesh_id testmesh > > ifconfig mesh5 10.0.0.5 > > > > If I have new node in the mesh network and I would like to dynamically > > assign 10.0.0.* address to its mesh interface as soon as it turn on then > > do I need to run DHCP server on mesh gate or any mesh node? > > > > But as I mentioned in my previous posts, there is already one DHCP server > > running on 192.168.1.1 and it is also assigning some 192.168.*.* ip > address > > to mesh node which I only see when I ping some external node.. > > > > Please clear my concepts if I am lacking into it. > > > > > > Thanks. > > > > > > > > On Thu, Jul 21, 2016 at 1:10 PM, Akshay Jindal < > [email protected]> > > wrote: > >> > >> Hi Yeoh, > >> > >> Router ---(wired)---mesh node 1 (mesh1)-----(wireless)----mesh node > >> 2(mesh2) > >> > >> DHCP server is running on router (192.168.1.1). I have created bridge > >> between eth0 and mesh1 interfaces in order to setup mesh node 1 as mesh > >> gate. > >> > >> I have assigned bridge br0 with 10.*.*.* address. > >> > >> brctl addbr br0 > >> brctl stp br0 off > >> brctl addif br0 eth0 > >> brctl addif br0 mesh1 > >> ifconfig mesh1 down > >> ifconfig eth0 down > >> ifconfig mesh1 0.0.0.0 up > >> ifconfig eth0 0.0.0.0 up > >> ifconfig br0 10.0.0.1 > >> > >> routing table for mesh1: > >> > >> Desination Gateway Genmask Iface > >> 0.0.0.0 192.168.1.1 0.0.0,0 br0 > >> 10.0.0.0 0.0.0.0 255.0.0.0 br0 > >> 192.168..0.0 0.0.0.0 255.255.0.0 br0 > >> > >> As of now, I am not running any DHCP server on mesh node 1.. I have > >> manually configured IP addresses of mesh nodes. > >> > >> Suppose mesh2 address is 10.0.0.2 and if it ping 8.8.8.8 and its routing > >> table has entry for router (192.168.1.1). > >> then in wireshark, it shows other address assigned to this mesh2 i.e. > >> 192.168.1.* > >> It is because DHCP server running on router and it is assigning address > to > >> mesh2. But how is this happening? > >> > >> If mesh2 ping mesh1 then it has 10.0.0.2 ip address. Why IP address is > >> changing if it is going outside the mesh network? > >> > >> Do we need entry for router (gateway) in the routing table..? because > if I > >> delete this entry then it does not ping any external node. > >> > >> Thanks.. > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> On Thu, Jul 21, 2016 at 12:26 PM, Yeoh Chun-Yeow < > [email protected]> > >> wrote: > >>> > >>> How your router connected to the mesh gate or mesh node? wired or > >>> wireless? > >>> > >>> 192.168.*.* network and DHCP server that you mentioned is facing your > >>> mesh network? > >>> > >>> Please note that o11s working on L2 mesh. If you have a DHCP client on > >>> the mesh interface, it should be able to get the IP address from the > >>> DHCP server facing your mesh network. > >>> > >>> On Thu, Jul 21, 2016 at 4:42 PM, Akshay Jindal via Devel > >>> <[email protected]> wrote: > >>> > Hi All, > >>> > > >>> > I request you all to help me in some doubts as mentioned below. I am > >>> > trying > >>> > to access internet from mesh point for scenario: > >>> > > >>> > mesh point ------>mesh gate or mesh node---->router----->Internet > >>> > > >>> > mesh point are 10.*.*.* network and router is 192.168.*.* network. > >>> > > >>> > I read the how to and also referred some posts on devel group but I > >>> > didn't > >>> > understand the difference between bridge and mesh gate. Please > explain? > >>> > > >>> > If I setup bridge as given in HowTo then I am facing some issues like > >>> > > >>> > DHCP server running on router is setting IP address for mesh point > (not > >>> > connected via ethernet). However I have manually configured IP > address > >>> > for > >>> > all nodes. If I ping 8.8.8.8 from mesh point (10.*.*.*) then source > IP > >>> > address becomes 192.168.*.* (observed in wireshark). But if I ping > any > >>> > mesh > >>> > node which is also 10.*.*.* network then source IP address does not > >>> > change. > >>> > Is this happening because of bridge? > >>> > > >>> > > >>> > If there is no bridge between mesh node and router but they are > >>> > connected > >>> > via ethernet then I can also ping internet by just setting proper > >>> > routes in > >>> > routing table. What does this exactly mean? > >>> > > >>> > As of now I have manually configured IP addresses for nodes. Is it > >>> > possible > >>> > to dynamically assign addresses to nodes? Do I need to run DHCP > server > >>> > on > >>> > one of the mesh node? > >>> > Or DHCP server running on router can assign addresses to all nodes > (if > >>> > bridging)? > >>> > > >>> > > >>> > > >>> > Thanks and Regards, > >>> > Akshay > >>> > > >>> > > >>> > > >>> > _______________________________________________ > >>> > Devel mailing list > >>> > [email protected] > >>> > http://lists.open80211s.org/mailman/listinfo/devel > >> > >> > > >
_______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/mailman/listinfo/devel
