[openbeosnetteam] Re: detaching ifnet in netstack
- From: "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Wed, 26 Nov 2003 21:33:14 +0100
> What happens if the ifnet structure disappears?
>
> Simple : memory leak(s). :-(
> Yet another thing to fix...
Now, I figured this out, too. ;)
There is another bug:
Ifconfig does not change the address of an interface if it was already set. The
problem is (I think) that our netstack does not handle SIOCAIFADDR when it is
called a second time. Using SIOCSIFADDR, etc. works, though.
> If in_control() don't do it fine, I really don't know what else will...
> What's the issue you have with in_control() ?
I think the problem is fixed now. As I said above SIOCAIFADDR does not work
correctly, so I had to find out how to use SIOCSIFADDR, SIOCSIFDSTADDR, and
SIOCSIFNETMASK.
At least, when I connect the addresses are assigned correctly.
But: there is a problem with sending packets (e.g.: ping). It always reports
"no route to host". It is the same when only my network card is set up. Only
"ping 127.0.0.1" works at the moment. Using host names does not work at all.
Do we have a networking BUG/TODO list so I can add three items to it? Should I
use the SF.net BUG tracker?
> > Uhm, I think around 70% could be finished now. Only the preflet and
> > the serial modem module are left.
>
> Okay, I've updated the task data according to your estimation.
Thank you.
Waldemar
- References:
- [openbeosnetteam] Re: detaching ifnet in netstack
- From: Philippe Houdoin
Other related posts:
- » [openbeosnetteam] detaching ifnet in netstack
- » [openbeosnetteam] Re: detaching ifnet in netstack
- » [openbeosnetteam] Re: detaching ifnet in netstack
- » [openbeosnetteam] Re: detaching ifnet in netstack
- » [openbeosnetteam] Re: detaching ifnet in netstack
- [openbeosnetteam] Re: detaching ifnet in netstack
- From: Philippe Houdoin