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 exist
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 address is
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't
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
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 first
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 works
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 you
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
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 usual
yet? I was under the impression that it only
sent out route change events (maybe I need to update my copy of
the -current sources, though). What I was talking about is the
idea that naked interface (0.0.0.0) arrivals and departures
could be signalled, which would cause dhclient to try to get
interface
(0.0.0.0) arrivals and departures could be signalled, which would cause
dhclient to try to get a lease on the interface.
got message of size 24 on Tue Jul 29 13:27:59 2003
RTM_IFANNOUNCE: interface arrival/departure: len 24, if# 6, what: arrival
got message of size 96 on Tue Jul 29 13
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
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 of
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 release
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
EOF
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 act on
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
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 what dhcpd
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?
Currently, devd is
from dhclient(8):
The DHCP client can be directed not to attempt to configure any
interfaces using the -n flag.
this does not seem to work, my interface gets configured, resolv.conf
written.
can anyone confirm this? what sort of action should be taken to fix
Hi folks-
I'm happily using 5.1 and it's terrific. Keep up the great work.
I just submitted a PR for a bug I noticed in the dhclient script. Namely,
it ignores the setting of dhcp_program from rc.conf. A one-line fix did
the trick for me, although there may be ramifications I'm not aware
On Sat, 7 Jun 2003 03:18:18 -0600
John Nielsen [EMAIL PROTECTED] wrote:
I just submitted a PR for a bug I noticed in the dhclient script. Namely,
it ignores the setting of dhcp_program from rc.conf. A one-line fix did
the trick for me, although there may be ramifications I'm not aware
-pc, when it's not attached to
my LAN.
We could modify rc.network by adding a to the dhclient row, but we are
looking for a more efficient way.
Can an optional flag be added (configurable in rc.conf)?
Thanks in advance,
Dario
--
Dario Freni [EMAIL PROTECTED]
SaturNero @ IRCNet, Azzurra IRC
for timeout.
I also had the same problem with my mobile-pc, when it's not attached to
my LAN.
We could modify rc.network by adding a to the dhclient row, but we are
looking for a more efficient way.
Can an optional flag be added (configurable in rc.conf)?
You could use the timeout option
configuration, which is great on a dhcp network, but ugly when it has to
wait for timeout.
I also had the same problem with my mobile-pc, when it's not attached to
my LAN.
We could modify rc.network by adding a to the dhclient row, but we are
looking for a more efficient way.
Can an optional flag
Reply to both and in ML
You could use the timeout option in dhclient.conf..
IMHO it's a risk.
From man dhclient:
The client can also be instructed to become a daemon imme-
diately, rather than waiting until it has acquired an IP
address. This can be done
On Fri, Jan 10, 2003 at 03:03:57PM +0100, Dario Freni wrote:
Reply to both and in ML
You could use the timeout option in dhclient.conf..
IMHO it's a risk.
From man dhclient:
The client can also be instructed to become a daemon imme-
diately, rather than waiting
After having updated to the world past 2002-02-19, dhclient started
very fast cycle of acquiring and releasing leases every time it was
attached to the local network, like it's attacking the DHCP server.
After all, it was /sbin/dhclient-script that failed trying to update
/etc/resolv.conf which
Sounds more like a non-reachable dhcp server
On Thu, 13 Dec 2001, Edwin Culp wrote:
Is anyone using dhclient successfully with Current of the last week or so?
I don't use it all the time but I have been trying for the last couple of
days without success.
It accesses the server
On Thu, 13 Dec 2001, Edwin Culp wrote:
Is anyone using dhclient successfully with Current of the last week or
so? I don't use it all the time but I have been trying for the last
couple of days without success.
It accesses the server and changes the interface ip to 0.0.0.0 netmask
Robert,
I got it working by adding a dhclient configuration file rather than using
the empty file that I have always used. I'm not sure why but it works:-)
I'll break out ethereal a little later and see if I can figure it out.
Thanks,
ed
Quoting Robert Watson [EMAIL PROTECTED]:
On Thu
Is anyone using dhclient successfully with Current of the last week or so?
I don't use it all the time but I have been trying for the last couple of
days without success.
It accesses the server and changes the interface ip to 0.0.0.0 netmask
255.255.255.255.
Thanks,
ce
---
To Unsubscribe
* Edwin Culp ([EMAIL PROTECTED]) wrote:
Is anyone using dhclient successfully with Current of the last week or so?
I don't use it all the time but I have been trying for the last couple of
days without success.
It accesses the server and changes the interface ip to 0.0.0.0 netmask
Date: Thu, 13 Dec 2001 06:15:32 -0800
From: Edwin Culp [EMAIL PROTECTED]
Is anyone using dhclient successfully with Current of the last week or so?
Sure; hadn't noticed any problems with it.
I don't use it all the time but I have been trying for the last couple of
days without success
:
Is anyone using dhclient successfully with Current of the last week or
so?
I don't use it all the time but I have been trying for the last couple of
days without success.
It accesses the server and changes the interface ip to 0.0.0.0 netmask
255.255.255.255.
No problems here, I
Quoting David Wolfskill [EMAIL PROTECTED]:
Date: Thu, 13 Dec 2001 06:15:32 -0800
From: Edwin Culp [EMAIL PROTECTED]
Is anyone using dhclient successfully with Current of the last week or so?
Sure; hadn't noticed any problems with it.
I don't use it all the time but I have been trying
This may explain my problem with the excite@home/attbi.com change over.
According to them it is pure dhcp. Since it has always just worked when
I needed it, I haven't really tested.
ed
Quoting Warner Losh [EMAIL PROTECTED]:
In message [EMAIL PROTECTED] Pierre Y.
Dampure writes:
: Are you
In message [EMAIL PROTECTED] Pierre Y. Dampure
writes:
: Are you asking for specific options (my dhclient.conf is empty)? are you using a
:reservation?
I'm 100% sure it worked before the upgrade. :-(.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in
On Sat, 8 Dec 2001 02:07:22 -0500, Jeremy Parker [EMAIL PROTECTED] wrote:
I have also experienced this issue, caused me a lot of trouble. The only
workaround I have figured out, is to bring up the interface with an IP
address, then start dhclient and it seems to work.
This is a very
% ifconfig -a
...
wi0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
...
status: associated
ssid X
% dhclient wi0
dhclient: wi0: not found
dhclient: exiting
Has anybody else seen this? I've seen this on two machines now,
including one from yesterday
I have also experienced this issue, caused me a lot of trouble. The only
workaround I have figured out, is to bring up the interface with an IP
address, then start dhclient and it seems to work.
This is a very recent problem for me as well.
Jeremy
Warner Losh([EMAIL PROTECTED])@Fri, Dec 07
For the last five days or so, dhclient from isc-dhcp2 has not worked
with -current on my machine. It reports dc0: not found. Some others
reported a similar problem with postfix which was cured by
recompiling. The same solution does not work with dhclient.
--
Michael D. Harnois
On Tue, Sep 11, 2001 at 01:28:12PM -0500, Michael Harnois wrote:
For the last five days or so, dhclient from isc-dhcp2 has not worked
with -current on my machine. It reports dc0: not found. Some others
reported a similar problem with postfix which was cured by
recompiling. The same solution
On Tue, 11 Sep 2001 13:05:57 -0700, David O'Brien [EMAIL PROTECTED] said:
Why are you using the client from isc-dhcp2 when that is the
same client in the base system?
In fact, having looked at my rc.conf now, I am using the one from the
base system.
--
Michael D. Harnois
Please, please commit this.
At Wed, 25 Oct 2000 01:31:57 +0900,
Motomichi Matsuzaki [EMAIL PROTECTED] wrote:
patch for revision 1.20:
--- /etc/pccard_ether Thu Oct 19 16:24:35 2000
+++ pccard_ether Wed Oct 25 01:27:05 2000
@@ -46,7 +46,7 @@
interface=$1
shift
-startstop=$2
patch for revision 1.20:
--- /etc/pccard_ether Thu Oct 19 16:24:35 2000
+++ pccard_etherWed Oct 25 01:27:05 2000
@@ -46,7 +46,7 @@
interface=$1
shift
-startstop=$2
+startstop=$1
shift
case ${startstop} in
@@ -101,7 +101,7 @@
;;
# Stop the interface
*)
-
Maybe I didn't get all the changes. I'm going to cvsup again and check.
Thanks,
ed
cc -nostdinc -O -pipe
-I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes
-I/usr/src/sbin/dhclient/../../contrib/isc-dhcp
-I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o
dhclient.o
Eric Hodel wrote:
When running dhclient with the kernel fxp driver I get a kernel panic in
ifconfig. Might be some other things I enabled in the kernel, but I haven't
double-checked yet.
I got it all straightened out, something in the config file was
messing up, but I accidentally deleted
When running dhclient with the kernel fxp driver I get a kernel panic in
ifconfig. Might be some other things I enabled in the kernel, but I haven't
double-checked yet.
--
Eric Hodel
hodel...@seattleu.edu
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current
201 - 249 of 249 matches
Mail list logo
