netdev
[Top] [All Lists]

Re: setting ip address from within driver

To: Andi Kleen <ak@xxxxxx>
Subject: Re: setting ip address from within driver
From: "Bjoern A. Zeeb" <bzeeb+netdev@xxxxxxxxxxxx>
Date: Thu, 30 Aug 2001 16:10:02 +0200 (CEST)
Cc: <netdev@xxxxxxxxxxx>
In-reply-to: <20010830151046.65125@colin.muc.de>
Sender: owner-netdev@xxxxxxxxxxx
On Thu, 30 Aug 2001, Andi Kleen wrote:

> > It is no problem to check all that but is it also possible to set ip
> > address from within driver without problems ?
> >
> > Would setting ifa_list->* be some kind of right approach ?
>
> The right approach would be a user mode daemon that sets it
> (kernel should supply mechanism, not policy)

ok, also thought of this but "mechanism" for this will blow up
kernel about the same size I think as doing it in ?
Another point is that as long none of the two peers are rebooted or
the line goes down (carrier prob) this only should happen once.
running a full blown user space daemon just for the possibility that
the line might go down isn't what I would like (even if it would sleep
all the time). Last I would do it that way if one could easily get
that data but p.ex. on isdn interface (where I am doing this stuff;
it is also not in net/wan/hdlc.c yet) one cannot use for example
libpcap to listen and wait for the packet (don't know if one even
can capture it because this happens the same second the
interface/leased line comes up). So one will need to buffer the
values somewhere in kernel space.

Well anyway can you provide me with some pointers/ideas for how to do
this in userspace ? How to make the "mechanism" in a good way that
would be acceptable (main question is directed to kernel/userspace
interaction) ? Then I am going to do it this way.

thanks in advance

-- 
Bjoern A. Zeeb                          bzeeb at Zabbadoz dot NeT
56 69 73 69 74                          http://www.zabbadoz.net/


<Prev in Thread] Current Thread [Next in Thread>