dhclient.conf for ath wireless
Erik Nørgaard
norgaard at locolomo.org
Tue Jul 5 08:18:49 GMT 2005
Hi,
This is posibly just missing documentation, but it may be a bug or
undesirable behaivour. I have read the ath, ifconfig, dhclient and
dhclient.conf man pages, searched the web and asked in questions@, but
not found an answer.
I am running -CURRENT with the new port of dhclient from OpenBSD. The
problem is that dhclient most often associante with my neighbours AP
instead of mine.
The man-pages mentions the "media" statement and according to the
examples I can find in google I should add an entry like this:
interface "ath0" {
media "ssid MYAP mode 11g";
}
in dhclient.conf. But on boot, dhclient enters into an infinite loop
bringing up and down the interface, until I break it. I have to manually
run "ifconfig ath0 ssid MYAP mode 11g" and then start dhclient manually
to force it to associate correctly with MYAP.
Can anyone point me to the correct documentation?
I recall seeing one example which mentions something like this entry in
rc.conf:
interface_ath0="ssid MYAP mode 11g DHCP"
Is this correct?
Also, according to the examples I have seen, I should be able to list
multiple wireless networks with the media option in dhclient.conf and
dhclient will try them in order.
This is cool since I can then configure my nic to associate depending on
where I am. This seems not to be posible if the configuration goes into
rc.conf.
I have a 3Com wireless NIC and a comtrend AP. My dhcp server is isc-dhcp
v.3 running on FBSD 5.4. I usually get associated with my neighbours
3Com AP running with a default setup.
Thanks, Erik
--
Ph: +34.666334818 web: http://www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
More information about the freebsd-current
mailing list