update: No IP assignment at TMobile hotspots

Recap: Laptop running Suse9.1Pro with Cisco Aironet 350 PCMCIA card.
Associates fine with home (WEP'd) WLAN, and some friends' various
(unWEP'd) WLANs, connects to internet flawlessly. Will not get IP
from DHCP servers are public hotspots like Kinko's, Borders, Panera
Bread, various hotels.

Well, I think I made a mistake, or gone backwards. Now I can't seem
to get my card to associate with the Kinko's AP.

Here's what I get:

Omnicomm:/home/David # iwlist eth1 scanning
eth1 Scan completed :
Cell 01 - Address: 00:0E:83:B6:72:4E
ESSID:"tmobile"
Mode:Master
Frequency:2.417GHz
Quality:0/10 Signal level:-28 dBm Noise level:-256 dBm
Encryption keyff
Bit Rate:1Mb/s
Bit Rate:2Mb/s
Bit Rate:5.5Mb/s
Bit Rate:11Mb/s

So far, so good. But then:

Omnicomm:/home/David # iwconfig eth1 ap tmobile
Interface eth1 doesn't support IP addresses
eth1 Interface doesn't support IP addresses
Error for wireless request "Set AP Address" (8B14) :
invalid argument "tmobile".


And here I'm stuck. I tried:

Omnicomm:/home/David # iwconfig eth1 essid tmobile
Omnicomm:/home/David # iwconfig eth1
eth1 IEEE 802.11-DS ESSID:"tmobile" Nickname:"Omnicomm"
Mode:Managed Frequency:2.442GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thrff Fragment thrff
Encryption key:****-****-** Security modepen
Power Managementff
Link Quality:126/10 Signal level:-92 dBm Noise level:-97 dBm
Rx invalid nwid:6 Rx invalid crypt:425 Rx invalid frag:0
Tx excessive retries:23 Invalid misc:4787 Missed beacon:0

But that obviously wasn't any good. Then I tried:

Omnicomm:/home/David # iwconfig eth1 ap 00:0E:83:B6:72:4E
Omnicomm:/home/David # iwconfig eth1
eth1 IEEE 802.11-DS ESSID:"tmobile" Nickname:"Omnicomm"
Mode:Managed Frequency:2.442GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thrff Fragment thrff
Encryption key:****-****-** Security modepen
Power Managementff
Link Quality:126/10 Signal level:-92 dBm Noise level:-97 dBm
Rx invalid nwid:8 Rx invalid crypt:425 Rx invalid frag:0
Tx excessive retries:23 Invalid misc:4916 Missed beacon:0

But even though I didn't get any error messages, nothing happened.

Relevant chunks from /var/log/messages:

May 23 15:20:10 Omnicomm cardmgr[2364]: socket 0: 350 Series Wireless
LAN Adapter
May 23 15:20:11 Omnicomm kernel: airo: cmd= 111
May 23 15:20:11 Omnicomm kernel: airo: status= 7f11
May 23 15:20:11 Omnicomm kernel: airo: Rsp0= 2
May 23 15:20:11 Omnicomm kernel: airo: Rsp1= 0
May 23 15:20:11 Omnicomm kernel: airo: Rsp2= 0
May 23 15:20:11 Omnicomm kernel: airo: Doing fast bap_reads
May 23 15:20:11 Omnicomm kernel: airo: MAC enabled eth1 0:f:f8:4f:6a:23
May 23 15:20:11 Omnicomm kernel: eth1: index 0x05: Vcc 5.0, Vpp 5.0,
irq 3, io 0x0100-0x013f
May 23 15:20:12 Omnicomm kernel: Setting key 0
May 23 15:20:12 Omnicomm kernel: SFW2-OUT-IPv6_PROHIB IN= OUT=eth1
SRC=0000:0000:0000:0000:0000:0000:0000:0000
DST=ff02:0000:0000:0000:0000:0001:ff4f:6a23 LEN=72 TC=0 HOPLIMIT=1
FLOWLBL=0 PROTO=0
May 23 15:20:13 Omnicomm kernel: SFW2-OUT-IPv6_PROHIB IN= OUT=eth1
SRC=0000:0000:0000:0000:0000:0000:0000:0000
DST=ff02:0000:0000:0000:0000:0001:ff4f:6a23 LEN=64 TC=0 HOPLIMIT=255
FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
May 23 15:20:14 Omnicomm kernel: SFW2-OUT-IPv6_PROHIB IN= OUT=eth1
SRC=fe80:0000:0000:0000:020f:f8ff:fe4f:6a23
DST=ff02:0000:0000:0000:0000:0000:0000:0002 LEN=56 TC=0 HOPLIMIT=255
FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0
May 23 15:20:16 Omnicomm kernel: SFW2-OUT-IPv6_PROHIB IN= OUT=eth1
SRC=fe80:0000:0000:0000:020f:f8ff:fe4f:6a23
DST=ff02:0000:0000:0000:0000:0001:ff4f:6a23 LEN=72 TC=0 HOPLIMIT=1
FLOWLBL=0 PROTO=0
May 23 15:20:16 Omnicomm ifup: No configuration found for wifi0
May 23 15:20:18 Omnicomm kernel: SFW2-OUT-IPv6_PROHIB IN= OUT=eth1
SRC=fe80:0000:0000:0000:020f:f8ff:fe4f:6a23
DST=ff02:0000:0000:0000:0000:0000:0000:0002 LEN=56 TC=0 HOPLIMIT=255
FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0
May 23 15:20:19 Omnicomm SuSEfirewall2: Firewall rules successfully
set from /etc/sysconfig/SuSEfirewall2
May 23 15:20:22 Omnicomm kernel: SFW2-OUT-IPv6_PROHIB IN= OUT=eth1
SRC=fe80:0000:0000:0000:020f:f8ff:fe4f:6a23
DST=ff02:0000:0000:0000:0000:0000:0000:0002 LEN=56 TC=0 HOPLIMIT=255
FLOWLBL=0 PROTO=ICMPv6 TYPE=133 CODE=0
May 23 15:20:23 Omnicomm kernel: eth1: no IPv6 routers present


One odd bit:
Omnicomm:/home/David # iwconfig
lo no wireless extensions.

sit0 no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11-DS ESSID:"tmobile" Nickname:"Omnicomm"
Mode:Managed Frequency:2.442GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thrff Fragment thrff
Encryption key:****-****-** Security modepen
Power Managementff
Link Quality:126/10 Signal level:-92 dBm Noise level:-123 dBm
Rx invalid nwid:16 Rx invalid crypt:425 Rx invalid frag:0
Tx excessive retries:23 Invalid misc:5141 Missed beacon:0

wifi0 IEEE 802.11-DS ESSID:"tmobile" Nickname:"Omnicomm"
Mode:Managed Frequency:2.442GHz Access Point: FF:FF:FF:FF:FF:FF
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thrff Fragment thrff
Encryption key:****-****-** Security modepen
Power Managementff
Link Quality:126/10 Signal level:-92 dBm Noise level:-123 dBm
Rx invalid nwid:16 Rx invalid crypt:425 Rx invalid frag:0
Tx excessive retries:23 Invalid misc:5141 Missed beacon:0


I don't know why, but wifi0 and eth1 are both the same connection. I
usually just perform my commands on eth1, but trying them on wifi0
doesn't get me anywhere either.
I'm stumped. I've used these same public hotspots, with this same
hardware, before under WXP and had no trouble. What could be
different between the various home WLANs and these public hotspots
that's keeping me out? And why the *heck* would the Aironet card balk
at taking an 'iwconfig ap' command? It makes no sense. If anything,
I'd expect to have problems at *home,* because there I'm using WEP. I
bought the Aironet precisely because it supposedly works natively with
Linux w/o needing additional drivers. And at home, that's exactly how
things have gone.

David McMillan wrote:
> Recap: Laptop running Suse9.1Pro with Cisco Aironet 350 PCMCIA
> card. Associates fine with home (WEP'd) WLAN, and some friends' various
> (unWEP'd) WLANs, connects to internet flawlessly. Will not get IP from
> DHCP servers are public hotspots like Kinko's, Borders, Panera Bread,
> various hotels.

<massive snippage>

Okay, I made a big step forward: I had to use 'iwconfig eth1 enc
off' to force the WEP off on the client end. As soon as I did that,
the Aironet card associated to tmobile automatically, I even saw a MAC
ID for the AP, and about 10-20sec later, eth1 got an IP from the DHCP
server. Apparently, having just one WEP key set up under YAST causes
the card to keep using that key, even when the YAST setting for AP and
ESSID is "any," and the only AP within range is open. Now I just have
to figure out why I can connect to my *friend's* open AP... gah.

But I can't get any internet traffic. Any attempt to ping the
nameserver IPs gave consistent "Destination Host Unreachable" errors.
Pings to the gateway IP apparently went to /dev/null. Traceroute
attempts just timeout... eventually. It *could* be the tmobile login
thing, but I doubt it -- that's supposed to redirect my first HTTP
access and then use port capture (AIUI), but over eth1 my Firefox just
reports "connecting to" for ~5min before finally timing out.
So I've achieved associattion to the AP, received an IP... but can't
get any traffic through. I know the tmobile AP is okay, because it
worked with the same hardware under WXP.
Sooo... any thoughts?

Shell outputs:

Omnicomm:/home/David # ifstatus eth1
eth1 device: "Cisco Systems", "350 Series Wireless LAN Adapter"
eth1 configuration: wlan-bus-pcmcia
dhcpcd running
eth1 is up
4: eth1: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast
qlen 1000
link/ether 00:0f:f8:4f:6a:23 brd ff:ff:ff:ff:ff:ff
inet 10.221.165.241/27 brd 10.221.165.255 scope global eth1
inet6 fe80::20f:f8ff:fe4f:6a23/64 scope link
valid_lft forever preferred_lft forever
eth1 IP address: 10.221.165.241/27 (DHCP)

current lease for eth1:
IPADDR=10.221.165.241
NETMASK=255.255.255.224
GATEWAY=10.221.165.225
DOMAIN='cust.hotspot.t-mobile.com'
DNS=66.94.9.120,66.94.25.120
DHCPSIADDR=0.0.0.0
DHCPCHADDR=00:0F:F8:4F:6A:23

eth1 IEEE 802.11-DS ESSID:"tmobile" Nickname:"Omnicomm"
Mode:Managed Frequency:2.442GHz Access Point: 00:0E:83:B6:72:4E
Bit Rate:11Mb/s Tx-Power=20 dBm Sensitivity=0/65535
Retry limit:16 RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality:15/10 Signal level:-60 dBm Noise level:-100 dBm
Rx invalid nwid:174 Rx invalid crypt:434 Rx invalid frag:0
Tx excessive retries:30 Invalid misc:10238 Missed beacon:0

Omnicomm:/home/David # cat /etc/resolv.conf
### BEGIN INFO
#
# Modified_by: dhcpcd
# Backup: /etc/resolv.conf.saved.by.dhcpcd
# Process: dhcpcd
# Process_id: 2936
# Script: /sbin/modify_resolvconf
# Saveto:
# Info: This is a temporary resolv.conf created by service dhcpcd.
# The previous file has been saved and will be restored
later.
#
# If you don't like your resolv.conf to be changed, you
# can set MODIFY_{RESOLV,NAMED}_CONF_DYNAMICALLY=no. This
# variables are placed in /etc/sysconfig/network/config.
#
# You can also configure service dhcpcd not to modify it.
#
# If you don't like dhcpcd to change your nameserver
# settings
# then either set DHCLIENT_MODIFY_RESOLV_CONF=no
# in /etc/sysconfig/network/dhcp, or
# set MODIFY_RESOLV_CONF_DYNAMICALLY=no in
# /etc/sysconfig/network/config or (manually) use dhcpcd
# with -R. If you only want to keep your searchlist, set
# DHCLIENT_KEEP_SEARCHLIST=yes in
/etc/sysconfig/network/dhcp or
# (manually) use the -K option.
#
### END INFO
search cust.hotspot.t-mobile.com
nameserver 66.94.9.120
nameserver 66.94.25.120

Omnicomm:/home/David # traceroute cnn.com
cnn.com: Temporary failure in name resolution

It took quite a while for that last error message to come up -- over
2min.

In article <uuadnWGlKolqpw_fRVn-(E-Mail Removed)>, David McMillan wrote:

>But I can't get any internet traffic. Any attempt to ping the
>nameserver IPs gave consistent "Destination Host Unreachable" errors.
> Pings to the gateway IP apparently went to /dev/null. Traceroute
>attempts just timeout... eventually.

man route
man traceroute

What exactly does '/sbin/route -n' show? The 'Destination Host
Unreachable" message means that the network stack can't determine
the hardware address of the remote host. It thinks it knows where
to send the packet, but it can't find anyone to talk to. That often
means your routing is fscked.

>Omnicomm:/home/David # traceroute cnn.com
>cnn.com: Temporary failure in name resolution
>
> It took quite a while for that last error message to come up -- over
>2min.

You know, this has been part of the Linux FAQ for over NINE years. The
old FAQ is posted to comp.os.linux.misc weekly. The newer FAQ version is
available from the LDP - try http://ibiblio.org/pub/linux/docs/faqs/
But then, it would take you longer to type 'delay in name resolution'
into groups.google.com then it would for them to supply you with
several thousand hits - including every newbie in town giving the
correct answer.

Because you didn't include the -n option to traceroute, and used a
name rather than an IP address, the application is trying to resolve
the name to an IP address, and waiting till the resolver times out.
Also, because you have IPv6 enabled, there will be an additional delay
in name resolution while the kernel gamely tries to get an AAAA response.
You might try using '/usr/sbin/tcpdump -n -i eth1' to see if there
is any traffic on the interface. Who knows, you might be surprised.

Old guy