Default route doesn't change to wireless device (ath0)

Brooks Davis brooks at
Thu Sep 1 15:36:38 PDT 2005

On Thu, Sep 01, 2005 at 02:43:57PM -0700, Jon Dama wrote:
> If the start_if.ath0 script isn't running, you should check that you have
> removable_interfaces="ath0" in rc.conf.  Though, I saw some traffic that
> say this was going away.

Yup, it's dying.

> Anyway, quoting Brooks in "HEADSUP: OpenBSD dhclient incoming"
> "Second the pccard_ifconfig variable is only used as a default value for
> interfaces that are on the removable_interfaces list, but do not have an
> ifconfig_<if> variable. Third, interfaces must be on the
> removable_interfaces list for pccard_ether to work."

This is now wrong.  I've nuked the pccard_ifconfig and added an
ifconfig_DEFAULT variable which applies to all interfaces that don't
have ifconfig_<ifn> variables (actually, it applies to those with empty
ones as well at this point which is probably a bug.)

> There should not be a need to modify devd.conf as there is already this
> line:
> attach 0 {
>         device-name "$ethernet-nic-regex";
>         action "/etc/pccard_ether $device-name start";
> }
> The regex does cover ath0, and pccard_ether should handle the event if the
> interface is listed in removable_interfaces

We've actually done away with the regex in HEAD and are using interface
types so anything should work now.

> I also saw some traffic from Brooks where he explicitly stated that
> the new dhclient does not touch the default route if one is already
> configured.  afaik, this should not actually be a problem because start_if
> is always run before dhclient has a change to start.  Also I agree, it
> would rather dangerous if dhclient just started flushing the routing
> table.

If you want to forcably set the default route via dhclient, you can do
it via /etc/dhclient-exit-hooks which is executed when dhclient-script
exits or you could write code to unset the current default route if the
interface is down and put it in /etc/dhclient-enter-hooks.

> Incidentially, I've seen this topic come up a dozen times + never knew
> what do myself until Nate Lawson pointed me in the right direction a year
> ago.  At that time, he remarked that this stuff isn't documented any where
> + it really should be in the handbook.
> Can someone point me to where I should look for information on how to
> contribute to the handbook in a format that is likely to be accepted?
> This is such a standard thing to want, it has to be done!

You're probably looking for the doc project primer.

We're hoping to make route handling a bit more flexable in dhclient, but
I haven't had time to work on it yet.

-- Brooks

> -Jon
> On Thu, 1 Sep 2005, Kevin Oberman wrote:
> > > Date: Thu, 1 Sep 2005 13:01:38 -0700 (PDT)
> > > From: Jon Dama <jd at>
> > > Sender: owner-freebsd-current at
> > >
> > > Flush the routing table or at least delete the default entry in a
> > > start_if.ath0 script.
> >
> > This is obvious, but does not answer the question: "Can't that be done
> > automatically on plugging in either?"
> >
> > As I recall, when the OpenSSH dhclient was added, one of the things it
> > was supposed to do was flush the routing table. This never seems to have
> > happened and I'm not sure I'd want it to.
> >
> > Maybe devd could automate it? (I think I'm going to try that.)
> > --
> > R. Kevin Oberman, Network Engineer
> > Energy Sciences Network (ESnet)
> > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> > E-mail: oberman at			Phone: +1 510 486-8634
> >
> >
> > > On Thu, 1 Sep 2005, Jochen Gensch wrote:
> > >
> > > > Hi!
> > > >
> > > > If I plug in my wireless nic (atheros) it comes up automatically through
> > > > wpa_supplicant. However the default route still points to my non wireless
> > > > nic (fxp0) even if remove the network cable before plugging in the wireless
> > > > device. I have found no way around this, the only way of getting the
> > > > default route changed to ath0 is setting in manually. Can't that be done
> > > > automatically on plugging in either?
> >
> _______________________________________________
> freebsd-current at mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at"
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :

More information about the freebsd-current mailing list