On Tuesday 10 April 2007 18:16, Mrugesh Karnik wrote:
On Tuesday 10 Apr 2007 12:30:50 jtd wrote:
It does. I had set it up and it was working properly on 31st.
I think it was a combination of settings that allowed dhcp. Cause when we disabled dhcp in the web i/f and tried to create a udhcpd.conf file it simply refused to run on ANY interface.
Agreed. It needs to run the DHCP server on the wired LAN ports. That's the default setting. You can add one additional interface through the local config file. Which is what I had done.
Aha. But why not only on the wireless lan?.
The init scripts are a kind of weird.
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 OLSR i/f is for the backbone routing. running dhcp on this will open a new can of worms requiring dhcp forwarding etc.
Hmmmm. Now I'm royally confused. Which interface does dnsmasq listen to, in the working mesh? From what Dr. Nagarjuna said, there was a parameter called `OLSR-DHCP'. I assumed that that corresponds to the OLSR interface. I assumed wrong it seems :s So if I'm wrong, I guess OLSR handles the `cascaded' DHCP requests properly with dnsmasq listening to the WLAN interface?
I am confused. Looks like we have to have a close look at "OLSR-DHCP". Because having OLSR and wlan in the same subnet seems just not right, cause u are reducing the number of nodes or clients, a completely unneccessary trade off.
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.
Trust u not to remember ;-). We tried to replicate what u did but could not.
Well take a look at the init script /etc/init.d/udhcpd. There's a section towards the end where it populates the /etc/udhcpd.conf file with a here document. You'll see that it sources the file /etc/local.something at the end of the here document. This is the file where the manual configuration goes. In the udhcpd.conf, there comes up a comment saying `local settings go after this' or something. The sourced local file is reproduced there, right below the default config section.
Ok. so that is where u put the settings rather than changing the initial default interface.
afaik what u did was right but we were unable to repeat it. Which makes it a chance occurence or your own brand of witchcraft ;-) or we were stupid - but i am sure that it's not the case.
Well we were stupid. We should have put the local settings right where it said we should - at the end of the conf file. Never trust oneself.
It definitely isn't.
Can someone please post the ifconfig output on the `server'? Server being the wireless router connected to the internet directly through its WAN port.
Hmmm. That one still stands..
Ya. Looks like we gotta go to HBCSE once more to look things up thoroughly.