Re: freebsd-mobile Digest, Vol 219, Issue 5
ximo <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.mobile |
|---|---|
| Message-ID | <[email protected]> |
RE: 1. wifi connection to resortwifi (Stephen Montgomery-Smith) Try to do a Sysinstall as root in a console or xterm and reconfigure your netconfiguration in this case your nic ndis or something like this, it's what is named a postconfigure, other hint maybe I should not say it try Ubuntu Live CD a.k.a. Dapper or Freesbie 2.0 in the last option probably you need to do the postconfigure too :) Ximo On 6/10/07, [email protected] < [email protected]> wrote: > > Send freebsd-mobile mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-mobile digest..." > > > Today's Topics: > > 1. wifi connection to resortwifi (Stephen Montgomery-Smith) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 9 Jun 2007 21:49:18 -0500 (CDT) > From: Stephen Montgomery-Smith <[email protected]> > Subject: wifi connection to resortwifi > To: [email protected] > Message-ID: <[email protected]> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > > I'm trying to connect to "Resort Wifi" whilst staying in my hotel. I can > get windows XP to connect fine, but FreeBSD seems to have a hard time with > dhclient. The problem seems to be that the resort wants to connect as if > I had issued the following instructions: > > ifconfig ndis0 inet 192.168.4.190 netmask 255.255.255.255 up > route add default 192.168.4.1 > > If I do this by hand, I get an error message after the "route" command. I > can get around it by typing: > > ifconfig ndis0 netmask 255.255.255.0 > route add default 192.168.4.1 > > where the netmask was chosen somewhat arbitrarily, and then it all works > fine. I get the feeling that "resortwifi" are doing something bad, > perhaps taking an advantage of a bug in Windows XP that should reject this > bogus DHCP assignment. > > Anyway, can any of you suggest a more permanent workaround? I bet I'll > get messed up when my dhcp assignment gets renewed. > > > > ------------------------------ > > _______________________________________________ > [email protected] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "[email protected]" > > End of freebsd-mobile Digest, Vol 219, Issue 5 > ********************************************** > -- Mary Shelley's lost child _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mobile To unsubscribe, send any mail to "[email protected]"