On Tuesday 10 Apr 2007 01:21:14 Rony wrote:
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.
Err. The static WLAN IP is for the server. After that any client who wants to connect gets an ip from the DHCP server. You can run the native udhcpd on any interface you want.
The native dhcpd does not allow any changes to it.
It does. I had set it up and it was working properly on 31st. It was working fine for WLAN, not OLSR, because if I'm not mistaken, there's a different interface for OLSR, bridged with the actual WLAN interface. The DHCP server was running on the WLAN interface rather than the OLSR interface.
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.
There is provision. I did the last time. Edit the /etc/local.udhcpd.conf file. Either that or something similar. It allows you to run DHCP on any interface. With dnsmasq you get a DNS server + DHCP server. I'm wondering what has been done with the DNS server part? Does it run a caching nameserver or something? What's the nameserver address that any client connecting gets from the server?
The mistake I made, due to obvious lack of knowledge, was to run the DHCP server on the WLAN interface rather than the OLSR interface. Can someone please post the ifconfig output on the `server'? Server being the wireless router connected to the internet directly through its WAN port.