Hello guys,
I thought of a few issues on my way back home.
Firstly, if you want to edit stuff like nvram settings or anything else not available in the GUI, its apparently done via the /etc/local.* files. The DHCP server configuration for example, was done in /etc/local.udhcpd.conf or something similar. Just something to keep in mind before hacking the init scripts.
Secondly, I read this: http://tools.ietf.org/html/rfc3626#page-51 The cron script that was edited to prevent the default gw route loss (/usr/sbin/cron.minutely original at /usr/sbin/cron.minutely.orig) could have been trying to achieve this: http://tools.ietf.org/html/rfc3626#page-54 Please run a diff to make sure. But I don't think it should be kept the way it is in the original file either.
Another thing. If it is necessary to find out exactly which node assigned the ip to the client, in case of multiple DHCP servers, maybe interface aliases can be used to define two different subnets. Run DHCP server on the aliases to lease ips in two different subnets.
Also, apparently OLSR traffic happens on UDP port 698.
Regards.
On 4/1/07, Mrugesh Karnik mrugeshkarnik@gmail.com wrote:
Hello guys,
I thought of a few issues on my way back home.
Firstly, if you want to edit stuff like nvram settings or anything else not available in the GUI, its apparently done via the /etc/local.* files. The DHCP server configuration for example, was done in /etc/local.udhcpd.conf or something similar. Just something to keep in mind before hacking the init scripts.
Secondly, I read this: http://tools.ietf.org/html/rfc3626#page-51 The cron script that was edited to prevent the default gw route loss (/usr/sbin/cron.minutely original at /usr/sbin/cron.minutely.orig) could have been trying to achieve this: http://tools.ietf.org/html/rfc3626#page-54 Please run a diff to make sure. But I don't think it should be kept the way it is in the original file either.
Another thing. If it is necessary to find out exactly which node assigned the ip to the client, in case of multiple DHCP servers, maybe interface aliases can be used to define two different subnets. Run DHCP server on the aliases to lease ips in two different subnets.
Also, apparently OLSR traffic happens on UDP port 698.
Regards.
Hey i can help up by giving many isos for the server but i need help from
some person who could actually go to hbcse as i wont be able to come over there the preferred media for storage would be external hdd as it wont help burning so many dvds or cds which i would recommend if given by someone else as i dont have an external hdd with me. I would download the isos as i have a good high speed unlimited internet & give it to any person who could drop down to goregaon
On Sunday 01 April 2007 01:18, Mrugesh Karnik wrote:
Also, apparently OLSR traffic happens on UDP port 698.
That is useful so we can now check traffic flowing on 698.
On Sunday we got dhcp running on the wireless lan (which it seems is not the same as lan ) and internet access after running some iptables rules for forwarding. enabling firewall does not seem to execute the firewall script. I left at this point. Could someone brief us on what followed.
jtd wrote:
On Sunday 01 April 2007 01:18, Mrugesh Karnik wrote:
Also, apparently OLSR traffic happens on UDP port 698.
That is useful so we can now check traffic flowing on 698.
On Sunday we got dhcp running on the wireless lan (which it seems is not the same as lan ) and internet access after running some iptables rules for forwarding. enabling firewall does not seem to execute the firewall script. I left at this point. Could someone brief us on what followed.
We flashed the third one with the Friefunk firmware and tried it out but there were problems in that too. I left earlier than the rest of them so Dr. would know what happened.
Is there anyone on this list who knows German or some friend who knows it and can translate the Freifunk manuals for us. I feel that more information about the interface and its concept is needed. Meanwhile I will try to study the reports on the existing setups in other countries.
jtd wrote:
On Sunday 01 April 2007 01:18, Mrugesh Karnik wrote:
Also, apparently OLSR traffic happens on UDP port 698.
That is useful so we can now check traffic flowing on 698.
On Sunday we got dhcp running on the wireless lan (which it seems is not the same as lan ) and internet access after running some iptables rules for forwarding. enabling firewall does not seem to execute the firewall script. I left at this point. Could someone brief us on what followed.
firewall comes up automatically if the WLAN and LAN are on different networks. the script first checks if they are on the same net, if not iptable rules are added. after this, Internet also works fine. threfore, the script that I added manually need not be used at all.
we are almost close to getting the mesh working. very likely this saturday we will achieve what we wanted to achieve.
nagarjuna
-
Dilip Khanolkar -
jtd -
Mrugesh Karnik -
Nagarjuna G. -
Rony