How To: Manual Network Configuration without the need for Network Manager

[kingweee]

First of all, thank you to all those that have provided help in this thread.

Unfortunately, I have a problem with my manual configuration. Specifically, I cannot associate with an OPEN or WEP APs after first connecting to a WPA AP.

Process:

sudo dhclient -r ath0
sudo ifconfig ath0 down
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd
sudo ifconfig ath0 up
sudo iwconfig ath0 mode Managed
sudo dhclient ath0

I have absolutely no problem associating with "Jamnet", my home AP. However when I close wpa_supplicant (ctrl_c) and:

sudo dhclient -r ath0
sudo ifconfig ath0 down
sudo ifconfig ath0 up
sudo iwconfig interface essid "freenet"
sudo iwconfig interface mode Managed
sudo dhclient ath0

I cannot associate with the AP 'freenet'. Iwconfig lists freenet under the essid, but nothing under "Access Point". Further, it lists the incorrect "Link Quality", showing the quality for Jamnet rather than the weaker signal of freenet. I have previously also had the problem with associating with WEP networks after using wpa_supplicant.

If I do want to associate with WEP or OPEN networks after running wpa_supplicant, I am forced to reboot my machine. Once I reboot, I can easily connect to the OPEN and WEP networks. However, if I connect to my WPA network, I cannot go back to OPEN or WEP networks.

wpa_supplicant.conf

//
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant

network={
ssid="Jamnet"
scan_ssid=0
proto=WPA
key_mgmt=WPA-PSK
psk="testtest"
pairwise=TKIP
group=TKIP
}
//

lshw -C network

//
*-network
description: Wireless interface
product: AR5212/AR5213 Multiprotocol MAC/baseband processor
vendor: Atheros Communications, Inc.
physical id: 0
bus info: pci@0000:04:00.0
logical name: wifi0
version: 01
serial: 00:20:a6:60:c2:f4
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list logical ethernet physical wireless
configuration: broadcast=yes driver=ath_pci ip=192.168.1.225 latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes wireless=IEEE 802.11g
//

[kevdog]

Ok a couple of things I would try:

This particular line:
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

Since you know it works, you could probably drop the -dd option since you no longer need the debugging info, and instead fork it to the background with the -Bw option.

Also, you driver is ath_pci or madwifi, not wext in your case. So I would use this as follows:

sudo wpa_supplicant -Bw -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf

Next, when you are done with wpa_supplicant (or done connecting with WPA), kill the wpa_supplicant handshake with:

sudo killall wpa_supplicant

This line would go right under the sudo dhclient -r ath0 line.

[kingweee]

Ok a couple of things I would try:

This particular line:
sudo wpa_supplicant -Dwext -iath0 -c/etc/wpa_supplicant.conf -dd

Since you know it works, you could probably drop the -dd option since you no longer need the debugging info, and instead fork it to the background with the -Bw option.

Also, you driver is ath_pci or madwifi, not wext in your case. So I would use this as follows:

sudo wpa_supplicant -Bw -Dmadwifi -iath0 -c/etc/wpa_supplicant.conf

Next, when you are done with wpa_supplicant (or done connecting with WPA), kill the wpa_supplicant handshake with:

sudo killall wpa_supplicant

This line would go right under the sudo dhclient -r ath0 line.

Thank you very much good sir, the problem has been solved.

You are a gentleman and a scholar.

[madscientist]

I feel a little left out in the cold, trying to use Ubuntu in a traditional Enterprise environment, but nevertheless I persevere!!

You m ight want to add a note to your guide that if you are working in an environment using NIS, and you are using Hardy, and you want to disable NetworkManager, then you also have to add this line to /etc/defaults/nis:

YPBINDARGS=-no-dbus

If you don't do that then ypbind will wait around forever for NetworkManager to report via dbus that the network is up, and it will never bind.

This new behavior of ypbind is confusing, and I don't think I like the requirement that NetworkManager seems to make, that all upper-layer applications who require networking services have to be modified to have special GNU/Linux-specific awareness (for dbus/NM) or they don't work correctly.

I haven't considered the problem completely but it just FEELS like, if your implementation requires this level of cooperation, you're doing something wrong and need to step back and reconsider from first principles.

[kevdog]

Sorry, but I have no experience with NIS or ypbind. You would have to elaborate on these two programs further. Thanks.

[steveo10078]

Hey, i'm pretty much a noob to ubuntu and linux on a whole really so please excuse my ignorance. When i got ubuntu, my wireless wouldnt work, so my friend took the windows drivers and installed them using ndiswrapper, and installed wifi radar, and thats the only way i can connect. The only problem with this is that i have to go into terminal and type in:
code: sudo modprobe ndiswrapper
every time i start my comp.

is there a way i can automate this, or would i do this the same way it was dome as shown above?

i would apreciate the help because so far thats one of the only problems i have with ubuntu so far

[madscientist]

NIS, or Network Information Services, is the granddaddy of distributed information services: it was around long before, and serves the same type of niche as, Active Directory. Originally developed by Sun, it was called "Yellow Pages", or YP, until Sun was sued by AT&T (I suppose--I don't remember the details) over using "Yellow Pages" which they had trademarked or something. Anyway, they changed the name of the feature to NIS but the commands and config files that make it up all still refer to YP, so ypbind, ypwhich, yp.conf, etc.

Unlike AD which is LDAP-based, NIS is an extremely simple key/value pair database, like UNIX dbm, but network-distributed. It can store any type of information which can be expressed as a lookup key and a value. Each "database" is called an NIS "map". It is most often used to distribute username and group information via the "passwd" and "group" NIS maps. This is how this information was shared in a UNIX enterprise, much like AD is used to share user information in a Windows environment.

Other, less common but still widely used maps are automount maps and netgroup maps. It used to be that hosts were distributed that way as well, before it became easier to run your own DNS server. And some companies have created their own types of maps for special purposes. Commands like ypcat (show an entire map) and ypmatch (show a matching entry) are used to display maps.

NIS is a 3-tier protocol: at the top is the master server where the master copies of all the maps live. Then you can (optionally) have slave servers, and finally the clients themselves. Clients do not do any caching of data, so if you have a large network you need slave servers to distribute the load. In the old days, there would be one slave per LAN and the clients would broadcast for an NIS server. These days that's not very common and instead a specific server is configured. The configuration file that controls this is /etc/yp.conf.

Ypbind is the daemon that runs on a client system that "binds" to the NIS server, either by broadcasting and listening for a response or by connecting to the server specified in the config file. On Debian/Ubuntu it's started via /etc/init.d/nis. If you look through Launchpad bugs and these forums you'll find many reports that it wasn't working properly in Feisty and Gutsy, because of NetworkManager; when the system comes up, NetworkManager is invoked to try to configure the network interfaces. But, unlike "normal" UNIX startup, the interface is not actually up when the system initialization continues, and so when ypbind tries to come up it can't connect and the whole thing fails.

In Hardy, apparently ypbind has been enhanced to be able to listen on D-Bus for reports from NetworkManager about interfaces coming up, and when you start it by default it waits for those D-Bus messages before it continues on. If it doesn't receive that message, it will never actually try to bind.

That's good, I suppose, in that it works better with NetworkManager (although now we've just delayed the errors to the NEXT set of things: the things that depend on NIS, like automount, which now don't work right in Hardy... but that's another bug report). However, if NetworkManager is not running then ypbind waits forever because NetworkManager is not there.

So, if you disable NM you have to add a -no-dbus flag to the ypbind startup so it will go back to its old behavior. You do that by adding it to /etc/default/nis. If you install the NIS package you can read about it in the ypbind man pages.

HTH!

[kevdog]

steveo

Yes just type one type

echo ndiswrapper | sudo tee -a /etc/modules and the ndiswrapper kernel device driver will be loaded automatically at startup.

[fxjr]

Hi, kevdog!

As you said, I tried to setup a commandline manual connection with my ap and here is the output I got:

 wpa_supplicant -w -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ap_scan=1
ctrl_interface='/var/run/wpa_supplicant'
Line: 5 - start of a new network block
ssid - hexdump_ascii(len=5):
     74 65 73 74 65                                    teste           
scan_ssid=0 (0x0)
proto: 0x1
key_mgmt: 0x2
PSK (ASCII passphrase) - hexdump_ascii(len=10): [REMOVED]
pairwise: 0x8
group: 0x8
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
   id=0 ssid='teste'
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:90:4b:17:8a:a9
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=8
Received 386 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:17:9a:62:bb:e7 ssid='teste' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
   selected WPA AP 00:17:9a:62:bb:e7 ssid='teste'
Try to find non-WPA AP
Trying to associate with 00:17:9a:62:bb:e7 (SSID='teste' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: DISCONNECTED -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=13
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=161
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE2432043048606cdd160050f20101000050f20201000050f20201000050f202 RespIE)'
Association info event
req_ies - hexdump(len=47): 00 05 74 65 73 74 65 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:17:9a:62:bb:e7
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:17:9a:62:bb:e7
No keys have been configured - skip key clearing
Associated with 00:17:9a:62:bb:e7
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
Added BSSID 00:17:9a:62:bb:e7 into blacklist
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 386 bytes of scan results (2 BSSes)
Scan results: 2
Selecting BSS from priority group 0
Try to find WPA-enabled AP
0: 00:17:9a:62:bb:e7 ssid='teste' wpa_ie_len=24 rsn_ie_len=0 caps=0x11
   selected based on WPA IE
   selected WPA AP 00:17:9a:62:bb:e7 ssid='teste'
Try to find non-WPA AP
Trying to associate with 00:17:9a:62:bb:e7 (SSID='teste' freq=2447 MHz)
Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
WPA: using IEEE 802.11i/D3.0
WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 proto 1
WPA: set AP WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
WPA: clearing AP RSN IE
WPA: using GTK TKIP
WPA: using PTK TKIP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
No keys have been configured - skip key clearing
wpa_driver_wext_set_drop_unencrypted
State: SCANNING -> ASSOCIATING
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
wpa_driver_wext_associate
Setting authentication timeout: 10 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b04 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b1a len=13
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8c02 len=161
WEXT: Custom wireless event: 'ASSOCINFO(ReqIE2432043048606cdd160050f20101000050f20201000050f20201000050f202 RespIE)'
Association info event
req_ies - hexdump(len=47): 00 05 74 65 73 74 65 01 08 02 04 0b 16 0c 12 18 24 32 04 30 48 60 6c dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
resp_ies - hexdump(len=16): 01 04 82 84 8b 96 32 08 0c 12 18 24 30 48 60 6c
WPA: set own WPA/RSN IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:17:9a:62:bb:e7
State: ASSOCIATING -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated to a new BSS: BSSID=00:17:9a:62:bb:e7
No keys have been configured - skip key clearing
Associated with 00:17:9a:62:bb:e7
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
RTM_NEWLINK: operstate=0 ifi_flags=0x11003 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b15 len=20
Wireless event: new AP: 00:00:00:00:00:00
Setting scan request: 0 sec 100000 usec
BSSID 00:17:9a:62:bb:e7 blacklist count incremented to 2
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
EAPOL: External notification - EAP success=0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
State: DISCONNECTED -> SCANNING
Starting AP scan (broadcast SSID)
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface wlan0
State: SCANNING -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
Removed BSSID 00:17:9a:62:bb:e7 from blacklist (clear)
Cancelling scan request
Cancelling authentication timeout
WEXT: Operstate: linkmode=0, operstate=6

I don't know what can be going wrong, but I think it is the same problem networkmanager is having to be able to connect to my AP.

Here is the result of lshw -C network:

lshw -C network
  *-network:0             
       description: Network controller
       product: BCM4306 802.11b/g Wireless LAN Controller
       vendor: Broadcom Corporation
       physical id: 3
       bus info: pci@0000:02:03.0
       version: 02
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list
       configuration: driver=b43-pci-bridge latency=64 module=ssb
  *-network:1
       description: Ethernet interface
       product: 82801DB PRO/100 VE (MOB) Ethernet Controller
       vendor: Intel Corporation
       physical id: 8
       bus info: pci@0000:02:08.0
       logical name: eth0
       version: 83
       serial: 00:e0:b8:67:5f:90
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A ip=192.168.0.156 latency=66 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s
  *-network
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       serial: 00:90:4b:17:8a:a9
       capabilities: ethernet physical wireless
       configuration: broadcast=yes multicast=yes wireless=IEEE 802.11g

If you can shed some light about that, I would thank you very much!

Thanks in advance.

[kevdog]

Something is wacky about your driver setup on your wireless card. Can you post iwlist scan. Do you have a bridge configured?