[SlugLUG] Fwd: Ticket 11007 Open (Updated) --> Problems with cruznet wireless and LInux: I am ...

[Peter Belew]

It appears much of the problem was a misconfiguration in the interface
configuration file for debian/ubuntu (/etc/network/interfaces)
- the wireless-essid entry was quoted, and should not have been

Also I've started using an application called Wireless Assistant
(wlassistant) which graphically displays detected APs and
allows one to connect to a specific one, as in Windows. That
really helps with roaming.

- Peter Belew

On 9/11/06, Mark Boolootian <booloo at ucsc.edu> wrote:
>
> Odd - this email doesn't appear in the sluglugl list archives.
>
> I checked the DHCP logs for Sept 8th (the day your wrote this message) and
> found several entries that show you being given an address:
>
> Sep  8 13:54:58 DHCPDISCOVER from 00:e0:98:ce:ea:f3 via 169.233.68.254
> Sep  8 13:54:59 DHCPOFFER on 169.233.68.151 to 00:e0:98:ce:ea:f3 (cupid)
> Sep  8 13:54:59 DHCPREQUEST for 169.233.68.151 from 00:e0:98:ce:ea:f3
> Sep  8 13:54:59 DHCPACK on 169.233.68.151 to 00:e0:98:ce:ea:f3
>
> Your machines issues a DHCPDISCOVER to find a DHCP server, the server
> offers you an address, the DHCPREQUEST is your machine saying you'd like
> to use said address, and the DHCPACK is a confirmation by the DHCP server
> that it's yours to use.
>
> The above address comes from somewhere at Cowell/Stevenson/Bookstore.
> There are similar log entries at 14:16, 14:40, and 14:47.  These latter
> entries are from core, which probably includes McHenry.
>
> I believe the entry "(cupid)" is the client-id and exists somewhere on
> your system.  Perhaps you recognize it?
>
> Since you said you booted both linux and windows, and windows worked
> but linux didn't, it's possible these entries are all related to your
> windows boots.
>
> There aren't any changes in the system that we're aware of that would
> cause the behavior you're seeing.  There isn't any restriction on the
> type of system you use with wireless (nor in resnet, for that matter).
>
> Have you run a tcpdump when trying to acquire an address in linux?
> It would be instructive to see whether you are communicating with the
> DHCP server at all.
>
> Yours is the only complaint I'm aware of, but that may simply mean
> we don't have many linux wireless users.  Have you tried using it
> over at Baskin Engineering?  They run their own wireless stuff, and
> while you may not be able to log in, you might at least be able to
> get an address to verify that it isn't a local system problem.  That's
> another useful datapoint to throw our direction.
>
>
> mb
> ---
>
>
> > This is today in the Stevenson coffeehouse:
> >
> > 1) scan for APs:
> >
> > $ iwlist wlan0 scan
> > wlan0     Scan completed :
> >          Cell 01 - Address: 00:02:8A:78:C0:F1
> >                    ESSID:"cruznet"
> >                    Mode:Master
> >                    Frequency:2.432 GHz (Channel 5)
> >                    Quality=47/100  Signal level=26/100  Noise level=0/100
> >                    Encryption key:off
> >                    Bit Rates:11 Mb/s
> >
> > 2) part of /etc/network/interfaces
> >
> > iface wlan0 inet dhcp
> > wireless-essid "cruznet"
> >
> > 3) try to connect
> > root at cupid:/etc/network# ifup wlan0
> > Internet Systems Consortium DHCP Client V3.0.3
> > Copyright 2004-2005 Internet Systems Consortium.
> > All rights reserved.
> > For info, please visit http://www.isc.org/products/DHCP
> >
> > Listening on LPF/wlan0/00:e0:98:ce:ea:f3
> > Sending on   LPF/wlan0/00:e0:98:ce:ea:f3
> > Sending on   Socket/fallback
> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
> > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.
> >
> > 4) output of ifconfig - wlan0 has no IP
> > root at cupid:/etc/network# ifconfig
> > lo        Link encap:Local Loopback
> >          inet addr:127.0.0.1  Mask:255.0.0.0
> >          inet6 addr: ::1/128 Scope:Host
> >          UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >          RX packets:5 errors:0 dropped:0 overruns:0 frame:0
> >          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
> >          collisions:0 txqueuelen:0
> >          RX bytes:272 (272.0 b)  TX bytes:272 (272.0 b)
> >
> > wlan0     Link encap:Ethernet  HWaddr 00:E0:98:CE:EA:F3
> >          UP BROADCAST MULTICAST  MTU:1500  Metric:1
> >          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >          collisions:0 txqueuelen:1000
> >          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
> >          Interrupt:169
> >
> > root at cupid:/etc/network#
> >
> > Later in the afternoon, I went to the bottom floor of the McHenry library,
> > and tried connecting from both Windows and Linux. Again, I had no luck with
> > Linux. With Windows, however, I saw that I could no long connect to outside
> > addresses,  only to the internal UCSC network. Does this mean that special
> > software  is now going to be needed to connect to outside IPs? Does it mean
> > that guest access is no longer going to be available?
> >
> > = Peter
> >
> >
> >
> > On 9/8/06, Cody Caughlan <toolbag at gmail.com> wrote:
> > >
> > >Re: your issue, I asked someone here on campus who is in tune with IT
> > >support, this is his response:
> > >
> > ><snip>
> > >Not enough info to troubleshoot. Can he associate to the SSID but not
> > >receive an IP address? Does he receive an IP address but no
> > >connectivity? Has he tried other locations on campus?
> > >
> > >Linux has lots of log files, I don't see that he's pasted any snippets
> > >or error messages, or even shown a sample of the issue
> > ></snip>
> > >
> > >/Cody
> > >
> > >
> > >
>
> > _______________________________________________
> > Sluglug mailing list
> > Sluglug at sluglug.ucsc.edu
> > http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>
>