"Matthew R. Dempsky" <[EMAIL PROTECTED]> wrote: > Is there a proper way to dynamically manage network interfaces > with OpenBSD? I have been using ``ifconfig iwi0 nwid $ESSID > nwkey $KEY; dhclient iwi0'' to connect to a given wireless > network and ``ifconfig iwi0 down'' to disconnect (and similarly > with em0 for wired networks), but this gives me problems at > times.
You want trunk(4) in failover mode, it is pure magic. :-) ifconfig trunk0 trunkproto failover trunkport em0 trunkport iw0 dhclient trunk0 When moving to a new wireless network use ifconfig to set a new nwid and nwkey and it should just work. > For example, sometimes it seems I cannot (re)associate with a > wireless network or dhclient(1) will not give an IP address. > Surely there's a better solution than rebooting anytime my > network setup gets wedged. :-) (Sorry for the vague problem > descriptions---I'm not yet familiar with how to diagnose my > networking issues on OpenBSD.) I have hade some problems with iwi(4), it seems the card can hang when changing nwid but I have not enough info for a bug report. Blame Intel that won't give out documentation so that developers have to guess how the card works. > Finally, the ifconfig(1) man page mentions that the down action > ``automatically disables routes using the interface,'' but if I > run ``ifconfig iwi0 down'' after connecting to my home network, > ``route show'' still lists iwi0. Am I misreading the man page > or is this a bug? Don't know that one.
