Tony Finch wrote:
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> >I can't wait for IPv6 stateless autoconfiguration plus SLPv2 so
> >we can get rid of all this DHCP crap once and for all. 8-(.
> >SLPv2 is used to find the gateway and DNS server, and after that,
> >everything "magically works".
>
>
On Tue, 29 Jul 2003, Terry Lambert wrote:
> This is part of the problem. The other parts are that this is really
> networking code, and should be a separate thing, if possible, and, as
> Martin just pointed out, the OMAPI stuff is not really cooked yet.
Hence the notion of a neteventd -- I don'
Terry Lambert <[EMAIL PROTECTED]> wrote:
>
>I can't wait for IPv6 stateless autoconfiguration plus SLPv2 so
>we can get rid of all this DHCP crap once and for all. 8-(.
>SLPv2 is used to find the gateway and DNS server, and after that,
>everything "magically works".
I thought that the gateway add
On Tue, Jul 29, 2003 at 10:18:05PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Martin Blapp <[EMAIL PROTECTED]> writes:
> : Hi Folks,
> :
> : I had a closer loom at the OMAPI stuff in dhclient.
> :
> : Just to say, I'm very disappointed. The only objects that exis
On Wed, Jul 30, 2003 at 08:52:19AM +0200, Martin Blapp wrote:
> But the interface adding does still not work. Maybe a different
> syntax than this ?
>
> connect
> new interface
> open
> set rl0 = "up";
> update
> close
I think you want this syntax (although I still couldn't get it to work):
conn
Hi,
> Odd:
>
> %%%
> # cat /etc/sleep_dhclient
> #!/bin/sh
>
> omshell > /dev/null << EOF
> connect
> new control
> open
> set state = 3
> update
> close
> EOF
> # cat /etc/wakeup_dhclient
> #!/bin/sh
>
> omshell > /dev/null << EOF
> connect
> new control
> open
> set state = 4
> update
> close
>
Robert Watson wrote:
> On Tue, 29 Jul 2003, Daniel C. Sobral wrote:
> > > You could add kevents for interface arrival and departure, and
> > > add a kqueue to the dhcpd to catch the arrival/departure events,
> > > and then just act on them.
> >
> > Instead of just adding the stuff to devd?
>
> Cur
"Daniel C. Sobral" wrote:
> Terry Lambert wrote:
> > You could add kevents for interface arrival and departure, and
> > add a kqueue to the dhcpd to catch the arrival/departure events,
> > and then just act on them.
>
> Instead of just adding the stuff to devd?
The entire dhcpd code? Isn't that
In message: <[EMAIL PROTECTED]>
Martin Blapp <[EMAIL PROTECTED]> writes:
:
: Hi Folks,
:
: I had a closer loom at the OMAPI stuff in dhclient.
:
: Just to say, I'm very disappointed. The only objects that exist are:
: "control" and "interface". The later is not inplemented at all.
:
In message: <[EMAIL PROTECTED]>
Robert Watson <[EMAIL PROTECTED]> writes:
:
: On Tue, 29 Jul 2003, Daniel C. Sobral wrote:
:
: > > You could add kevents for interface arrival and departure, and
: > > add a kqueue to the dhcpd to catch the arrival/departure events,
: > > and then just
On Wed, 30 Jul 2003, Martin Blapp wrote:
> "control" does only release leases and exit (state 2), I never managed
> to make dhclient sleep (state 3) and wake up (state 2).
Odd:
%%%
# cat /etc/sleep_dhclient
#!/bin/sh
omshell > /dev/null << EOF
connect
new control
open
set state = 3
update
close
Hi Folks,
I had a closer loom at the OMAPI stuff in dhclient.
Just to say, I'm very disappointed. The only objects that exist are:
"control" and "interface". The later is not inplemented at all.
It pretends to work, but if you look at the source there are
stubs only :P.
"control" does only rele
On Tue, 29 Jul 2003, Daniel C. Sobral wrote:
> > You could add kevents for interface arrival and departure, and
> > add a kqueue to the dhcpd to catch the arrival/departure events,
> > and then just act on them.
>
> Instead of just adding the stuff to devd?
Currently, devd is in the business o
Terry Lambert wrote:
Martin Blapp wrote:
I't is my goal to make dhclient really functional, so it can not only
be used with one interface, but several.
On a well known OS this works just fine. A first interface gets
initialized and the GW gets set as usual. But if a second interface
gets added, an
On Tue, 29 Jul 2003, Terry Lambert wrote:
> > Some of those events already exist for routing sockets, so in a worst case
> > scenario, you can hook up a routing socket to a kqueue :-).
> >
> > Martin -- you might want to try the "route monitor" command sometime and
> > take a look at the vent st
Robert Watson wrote:
> > [ ... ]
> > > If there are other ideas, I'm open to them.
> >
> > You could add kevents for interface arrival and departure, and add a
> > kqueue to the dhcpd to catch the arrival/departure events, and then just
> > act on them.
>
> Some of those events already exist for r
On Tue, 29 Jul 2003, Terry Lambert wrote:
> Martin Blapp wrote:
> > I't is my goal to make dhclient really functional, so it can not only
> > be used with one interface, but several.
> >
> > On a well known OS this works just fine. A first interface gets
> > initialized and the GW gets set as us
On Tue, Jul 29, 2003 at 02:01:36PM +0200, Martin Blapp wrote:
> > > can access dhclient (or dhcpd) on the local machine without authentification.
> >
> > You can get omshell working without auth over tcp/ip - I managed this
> > today when playing. But a unix domain socket would be nicer because
Hi,
> > can access dhclient (or dhcpd) on the local machine without authentification.
>
> You can get omshell working without auth over tcp/ip - I managed this
> today when playing. But a unix domain socket would be nicer because the
> dhclient server binds to INADDR_ANY by default.
Cool. Do
On Tue, Jul 29, 2003 at 09:56:48AM +0200, Martin Blapp wrote:
> I't is my goal to make dhclient really functional, so it can not only
> be used with one interface, but several.
Yay! This bites me badly on my laptop with a permanent fxp0 and a
sometimes-present wi0.
> On a well known OS this work
Martin Blapp wrote:
> I't is my goal to make dhclient really functional, so it can not only
> be used with one interface, but several.
>
> On a well known OS this works just fine. A first interface gets
> initialized and the GW gets set as usual. But if a second interface
> gets added, and the fir
Hi all,
I't is my goal to make dhclient really functional, so it can not only
be used with one interface, but several.
On a well known OS this works just fine. A first interface gets
initialized and the GW gets set as usual. But if a second interface
gets added, and the first one is still active
22 matches
Mail list logo
