Mrugesh Karnik wrote:
On Monday 09 Apr 2007 17:57:32 Nagarjuna G. wrote:
installed a package called 'freifunk-dnsmasq', restarted it. Now we see
an additional parameter on the web interface called OLSR-DHCP: This is
where we give the DHCP share of the mesh network (not the lan network).
thats it.
I need some details.
This entire thing now works only on the WLAN interface right? Is the LAN
completely out of the picture? So, the backend itself gets broadened? Maybe
subnetted, depending on the DHCP server(s).
DHCP works only in the LAN, not in WLAN. If WLAN is set to dhcp then
there is no mesh getting established. WLAN IP has to be static. With
static WLAN, we can access any network through the mesh. Even internet
access was possible by simply plugging in the cable to the WAN port of
one router. Even though it was outside the 192.168.x.x subnet. NAT and
Firewall were enabled.
Secondly, without the dnsmasq package, can we get the native udhcpd to work
with the OLSR interface? I think we can.. What's the OLSR interface that
shows up with ifconfig? It is possible, I think, to manually configure the
DHCP server to listen on the OLSR interface.
The native dhcpd does not allow any changes to it.
The problem, I think, wasn't with the missing package, but with the fact that
we had DHCP running on the WLAN interface instead of the OLSR interface. The
native DHCP should work perfectly fine if I'm right... unless dnsmasq has
some features I don't know about..
Yes it works fine but only in LAN. There is no native provision to
allocate dhcp ips for wireless users who join in. Thats why the extra
package.
--
Regards,
Rony.
--
http://mm.glug-bom.org/mailman/listinfo/linuxers
