
>> Thanks to anyone willing to help !!

>> lunar worked fine with 2.6.18 until we stopped the development in 2007.
   I am now "resurrecting" that code for some new project.

-------------
>> To compile: 
Do 'make intel' in top-level directory

-------------
>> To run:
Beware: running lunar creates a 'lunar' interface and running S01lunar runs a DHCP client on the lunar interface.
The module has a built-in "mini-fake" DHCP server and DNS server: the DHCP server returns an address in the range 192.168.42.0/24, and the DNS server sends replies for the "net.lunar" domain with the range 192.168.42.0/24.
For example, doing "nslookup bill.net.lunar" returns an address from 192.168.42.0/24.

Edit S01lunar and set a valid interface for BASEDEVNAME (line 37) -- doesn't need to be a wireless interface.
Run './S01lunar start'

-------------
>> To produce kernel crash/hang/(possibly deadlock)
Just run a few 'nslookup {bill|joe|whatever}.net.lunar' with some 'arp -a' from time to time.
This usually crashes the machine after very few attemps.

I am currently testing on debian 2.6.31 in qemu, while the real deployment is on OpenWRT 2.6.32 on Linksys devices. 

-------------
>> IMPORTANT
I modified lunar_do_ndisc() in lunar_core.c to always return an answer for DNS lookups for "net.lunar" and to skip the real route discovery/build phase of lunar while debugging.
(normally a DNS lookup for net.lunar triggers a route discovery/build phase: if successful a DNS reply is sent, otherwise a DNS nosuchname is sent back -- I skipped all this to narrow down the bug.)

-------------
>> SORRY
The code is full of old stuff for 2.4 or older 2.6 kernels, also some code pollution for no-longer working NS2 (net simulator) compilation: I apologize for that.

Thanks in advance to anyone willing to help,
Christophe

