[lwip-users] Re: [lwip] running lwip in unixsim

[Felipe Massia Pereira]

Hello,

I'm trying to make it work under linux. There's another person
working on it. Well... I found that in linux 2.4 kernels, you should
create a device '/dev/net/tun' with

# mkdir /dev/net
# mknod -m 660 /dev/net/tun c 10 200

A program that opens this device can then do "ifconfig tun0 ..." via
system() call.

I had to tell module loader how to link modules with device adding the
following lines to /etc/modules.conf:

alias tun0 tun
alias char-major-10-200 tun

After adding these line, it's recommended to run "depmod -a".

But this is not all...I'm still working.

[]s
Felipe

On Fri, 2 Nov 2001, Ganesh  Subramaniam wrote:

> Hi lwip users
> 
> I tried to run the latest lwip-0.4.1 on a linux machine (2.4 kernel). I would 
> like to test the stack on the unix environment before attempting to port on a 
> PowerPC 405 platform running my port of ucos-ii. 
> 
> To test lwip (unixsim), I found that there are really two executables that i 
> can use. simrouter
> to run first a unix server. Then simnode the unix client. But the moment i 
> run simnode, the simrouter aborts (details below). In the first look, it 
> seems like no thread id in the thread list matches with the currently running 
> thread. Before, i begin to debug further, i would like to know if others had 
> similar problems. It seems like this is the testbed most others like Adam 
> would use before porting. Any suggestions would be helpful.
> 
> ./simrouter
> System initialized.
> Now run client.
> SIOCADDRT: Operation not permitted
> SIOCADDRT: Operation not permitted
> sys: current_thread: could not find current thread!
> This is due to a race condition in the LinuxThreads
> pthreads implementation. Start the program again.
> Aborted
> 
> 
> ./simnode
> System initialized.
> TCP/IP initialized.
> Applications started.
> 
> 
> Also, any inputs on testing the lwip stack on unixsim would be helpful.
> 
> Thanks in advance.
> 
> 
> Ganesh
> 
> 
> 
> 
> I was quite impressed with the lwip design - for it can be run standalone and 
> also 
> integrated easily to an OS. I have my design for the port of lwip to ucos 
> ready.
> 
> 
> 


[This message was sent through the lwip discussion list.]