Date: Sat, 26 Nov 2005 19:24:08 -0700 From: James Earl <james@icionline.ca> To: Hans Nieser <hans@nieser.net> Cc: freebsd-mobile@freebsd.org Subject: Re: Switching wired <-> wireless in a user-friendly manner, possible? Message-ID: <c6bf2550511261824pe186d14o82142d4200e50fb0@mail.gmail.com> In-Reply-To: <4388B53F.9020905@nieser.net> References: <4388B53F.9020905@nieser.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/26/05, Hans Nieser <hans@nieser.net> wrote: > Hello, > > I have a laptop that I mainly use at home. It's got both a wired and > wireless interface, both work fine. I used to run Windows XP on it which > allowed me to easily switch from the wired interface to the wireless > interface and vice versa. I found this convenient because I could plugin > the cable when I have my laptop on my desk for better performance. When I > wanted to work with the laptop somewhere else, like downstairs or perhaps > for some reading before I go to sleep, I could just unplug the cable and > could continue reading websites and access my LAN over the wireless inter= face. > > I have now installed FreeBSD 6.0 on my laptop and am trying to get it to > behave the same as Windows XP. Right now when I boot the laptop with the > cable plugged in it will access the LAN over the wired interface (fxp0), > as soon as I unplug the cable, I lose connectivity and won't route traffi= c > over the wireless interface (ipw0). > > I am guessing that what needs to happen is, as soon as fxp0 becomes > inactive, the default route needs to be updated so it will route over the > ipw0 interface. What is the best way to accomplish this? Do I have to > write a shellscript that continiously checks for fxp0's status and then > somehow update the default route, or are there facilities available for t= his? You could also try out the nicmond port. James
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c6bf2550511261824pe186d14o82142d4200e50fb0>