On Feb 28, 2006, at 7:16 PM, David W. Hankins wrote:
On Thu, Feb 09, 2006 at 12:50:08PM -0500, Chuck Swiger wrote:
If you haven't read this:
http://files.stuartcheshire.org/draft-cheshire-ipv4-acd.txt
...it's worth considering the way it standardizes (or proposes to
standardize)
how ARP
On Wed, Mar 01, 2006 at 02:05:48PM -0500, Charles Swiger wrote:
Perhaps I'll be free to contribute some patches, as I've got code
that handles layer-2 ARP traffic per the recommendations in the link
above. But I don't own the software in question, it was for a
client, so I'll have to
On Thu, Feb 09, 2006 at 12:50:08PM -0500, Chuck Swiger wrote:
If you haven't read this:
http://files.stuartcheshire.org/draft-cheshire-ipv4-acd.txt
...it's worth considering the way it standardizes (or proposes to standardize)
how ARP traffic from unconfigured IPs should be done to
Freddie Cash wrote:
Completely naive, non-developer question: would it be possible to split
the wi(4) driver into two drivers? One to support all the ancient,
pre-802.11 cards, and one to support all the nice, new cards?
All things are possible, if a volunteer steps forward to do the
Craig Boston wrote:
On Sat, Feb 04, 2006 at 10:04:16PM -0800, Kevin Oberman wrote:
The problem is that the integration of the modern wlan (802.11) code has
never been done in the if_wi code and it does not report state back to
wlan adequately to make the OpenBSD client function correctly.
On Wednesday 15 February 2006 09:31 am, Sam Leffler wrote:
Craig Boston wrote:
On Sat, Feb 04, 2006 at 10:04:16PM -0800, Kevin Oberman wrote:
I recently made another stab at overhauling wi to better integrate with
net80211. It uses some of Craig's work and some of mine. The results
were
On Sat, Feb 04, 2006 at 10:04:16PM -0800, Kevin Oberman wrote:
The problem is that the integration of the modern wlan (802.11) code has
never been done in the if_wi code and it does not report state back to
wlan adequately to make the OpenBSD client function correctly.
Well, that's not quite
David W. Hankins wrote:
On Sat, Feb 04, 2006 at 01:37:33AM -0500, Chuck Swiger wrote:
[ ...sorry for the minor delay, realjob sometimes interferes... ]
OK, cool. Are you doing anything with regard to Zeroconf/Rendezvous?
Not really, no, except when DHCP options appear to turn off IPv4LL, or
On Mon, Feb 06, 2006 at 11:11:45AM +, Matt Dawson wrote:
send host-name `hostname -s`;
I currently have *three* competing execute() patches queued for ISC
DHCP 3.1.0 which could be used to do this:
send host-name execute(hostname -s);
send fqdn.fqdn execute(hostname);
On Sunday 05 February 2006 06:04, you wrote:
The problem is that the integration of the modern wlan (802.11) code has
never been done in the if_wi code and it does not report state back to
wlan adequately to make the OpenBSD client function correctly.
Thank you, right there. That's exactly
At 07:02 PM 6/02/2006, Matt Dawson wrote:
On Sunday 05 February 2006 06:04, you wrote:
The problem is that the integration of the modern wlan (802.11) code has
never been done in the if_wi code and it does not report state back to
wlan adequately to make the OpenBSD client function correctly.
On Monday 06 February 2006 10:04, you wrote:
The thing I found with DDNS was getting the darn client to return the
correct hostname. For some reason, without setting it in
dhclient.conf, the DNS would not update, even if I have configured
the DHCP server to do the updates.
Yep, AOL. This was
On Sat, Feb 04, 2006 at 01:37:33AM -0500, Chuck Swiger wrote:
Howdy. Do you have a computer named HAL, by any chance? :-)
No, but I do have one named 'goliath'.
OK, cool. Are you doing anything with regard to Zeroconf/Rendezvous?
Not really, no, except when DHCP options appear to turn off
On Saturday 04 February 2006 12:01, [EMAIL PROTECTED] wrote:
many aspects of the network interface configuration
process were overhauled.
Which, I suppose, explains the yo-yo effect of my two xe (4) PC Cards, amongst
others, and why my wi (4) card no longer behaves itself.
From: Matt Dawson [EMAIL PROTECTED]
Date: Sat, 4 Feb 2006 18:08:02 +
Sender: [EMAIL PROTECTED]
On Saturday 04 February 2006 12:01, [EMAIL PROTECTED] wrot e:
many aspects of the network interface configuration process
were overhauled.
Which, I suppose, explains the yo-yo effect of
hi all... again...
i sent this message to general questions but nobody got excited about
it.
i just installed 6 on my t30 laptop. brand new. when trying dhclient i
get:
DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5
this trys 6 times then this shows up:
No DHCPOFFERS
On Fri, 3 Feb 2006 06:10:18 -0500 (EST)
make stuff up [EMAIL PROTECTED] wrote:
hi all... again...
i sent this message to general questions but nobody got excited
about it.
i just installed 6 on my t30 laptop. brand new. when trying
dhclient i get:
DHCPDISCOVER on fxp0 to
There was a change in DHCP between FreeBSD 5.x and 6.
I noticed the same behaviour with a couple of hw broadband routers.
AFAIR this was also reported back to the list, still no fix was
provided.
thank you... does that mean back to 5.4 for now?
this is the only system i have on the
2006/2/3, make stuff up [EMAIL PROTECTED]:
thank you... does that mean back to 5.4 for now?
Try install /usr/ports/net/isc-dhcp3-client/
--
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
___
freebsd-stable@freebsd.org
2006/2/3, make stuff up [EMAIL PROTECTED]:
thank you... does that mean back to 5.4 for now?
Try install /usr/ports/net/isc-dhcp3-client/
without a connection?
--
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
try install /usr/ports/net/isc-dhcp3-client
and edit your rc.conf:
dhclient_program=/usr/local/sbin/dhclient
dhclient_flags= see manual for isc-dhcp3-client
2006/2/3, Frank Altpeter [EMAIL PROTECTED]:
Hi there,
kalin mintchev wrote on 2006-02-03 at 13:55:01 CET:
2006/2/3, make stuff up
On Fri, 3 Feb 2006 14:02:41 +0100
Frank Altpeter [EMAIL PROTECTED] wrote:
Hi there,
kalin mintchev wrote on 2006-02-03 at 13:55:01 CET:
2006/2/3, make stuff up [EMAIL PROTECTED]:
thank you... does that mean back to 5.4 for now?
Try install /usr/ports/net/isc-dhcp3-client/
On Fri, 3 Feb 2006 14:39:19 +0100
Frank Altpeter [EMAIL PROTECTED] wrote:
Hi there,
Marcin Jessa wrote on 2006-02-03 at 14:33:55 CET:
On Fri, 3 Feb 2006 14:02:41 +0100
Frank Altpeter [EMAIL PROTECTED] wrote:
Hi there,
kalin mintchev wrote on 2006-02-03 at 13:55:01 CET:
try install /usr/ports/net/isc-dhcp3-client
and edit your rc.conf:
dhclient_program=/usr/local/sbin/dhclient
dhclient_flags= see manual for isc-dhcp3-client
ok.. this sounds reasonable...
but how do i tell the dhcp server what number am i assigning to fxp0?
now ifconfig shows exactly the
try install /usr/ports/net/isc-dhcp3-client
and edit your rc.conf:
dhclient_program=/usr/local/sbin/dhclient
dhclient_flags= see manual for isc-dhcp3-client
ok.. this sounds reasonable...
but how do i tell the dhcp server what number am i assigning to fxp0?
now ifconfig shows exactly
Marcin Jessa wrote:
Son't be silly. What if you dont know what IP you will get from the
lease? That's what working implementation of DHCP is for...
I thought that was why FreeBSD moved away from ISC DHCP to OpenBSD
dhclient?
Actually, I guess I never did understand that move. Certainly, no
kalin mintchev wrote:
try install /usr/ports/net/isc-dhcp3-client
and edit your rc.conf:
dhclient_program=/usr/local/sbin/dhclient
dhclient_flags= see manual for isc-dhcp3-client
ok.. this sounds reasonable...
but how do i tell the dhcp server what number am i assigning to fxp0?
now ifconfig
On Saturday 04 February 2006 00:36, Marcin Jessa wrote:
What if you take your laptop to an university to hold a lecture and you
are unable to run dhcp? None of the students know of the IPs avaliable
in the range.
Some systems disallow traffic unless your MAC-address is registered in
their
David W. Hankins wrote:
Marcin Jessa wrote:
Son't be silly. What if you dont know what IP you will get from the
lease? That's what working implementation of DHCP is for...
I thought that was why FreeBSD moved away from ISC DHCP to OpenBSD
dhclient?
Actually, I guess I never did
David W. Hankins wrote this message on Fri, Feb 03, 2006 at 16:55 -0800:
There's no one I think I'm supposed to be talking to about
architectural plans like these at FreeBSD. So all these plans
Well, you could always check the FreeBSD cvs repository to see who
imported dhclient (a hint, it's
On Saturday 04 February 2006 11:25, David W. Hankins wrote:
I thought that was why FreeBSD moved away from ISC DHCP to OpenBSD
dhclient?
Actually, I guess I never did understand that move. Certainly, no
one ever explained it to me without a great deal of wifi handwaving.
I was under the
Chuck Swiger wrote:
It would also be good if dhcpd would reassign the same IP to the same machine
(if the IP is not otherwise being used) if there was a prior lease matching the
client asking for a new lease, and not just when a client is trying to renew an
existing lease.
I'm way outside
32 matches
Mail list logo
