[Ndiswrapper-general] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Status: Beta
Brought to you by:
pgiri
From: Truong T. S. <so...@fc...> - 2007-03-01 08:38:47
|
Dear Sir, I install ndiswrapper on FC6 with no error, no bug. The PC has two interface, one NIC on board and one wireless. Wireless CNet-CWP-854 PART No. 18-1B-WP85 Wireless interface starts good, but can not PING to gateway and another host. # ping 172.16.198.1 <--- gateway PING 172.16.198.1 (172.16.198.1) 56(84) bytes of data. >From 172.16.198.52 icmp_seq=1 Destination Host Unreachable >From 172.16.198.52 icmp_seq=2 Destination Host Unreachable # cat /etc/sysconfig/network-scripts/ifcfg-wlan0 DEVICE=wlan0 ONBOOT=yes BOOTPROTO=static TYPE=Wireless ESSID=FC_CAN IPADDR=172.16.198.52 NETWORK=172.16.198.0 DOMAIN= NETMASK=255.255.255.128 GATEWAY=172.16.198.1 IPV6INIT= HWADDR=00:08:A1:87:55:EA MODE=Managed # cat /etc/sysconfig/network-scripts/keys-wlan0 KEY=1111111111 #dmesg ndiswrapper: using IRQ 10 wlan0: ethernet device 00:08:a1:87:55:ea using NDIS driver: rt2500, version: 0x20001, NDIS version: 0x500, vendor: 'IEEE 802.11g Wireless Card.', 1814:0201.5.conf wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA usbcore: registered new driver ndiswrapper eth0: no IPv6 routers present SELinux: initialized (dev rpc_pipefs, type rpc_pipefs), uses genfs_contexts wlan0: no IPv6 routers present Bluetooth: Core ver 2.10 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP ver 2.8 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 Bluetooth: HIDP (Human Interface Emulation) ver 1.1 SELinux: initialized (dev autofs, type autofs), uses genfs_contexts SELinux: initialized (dev autofs, type autofs), uses genfs_contexts ADDRCONF(NETDEV_UP): eth0: link is not ready e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready ADDRCONF(NETDEV_UP): wlan0: link is not ready eth0: no IPv6 routers present # iwconfig lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. wlan0 IEEE 802.11g ESSID:off/any Nickname:"can" Mode:Auto Frequency:2.412 GHz Access Point: Not-Associated Bit Rate=11 Mb/s Tx-Power:20 dBm Sensitivity=-120 dBm RTS thr=2347 B Fragment thr=2346 B Encryption key:1111-1111-11 Security mode:restricted Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 # ifconfig -a eth0 Link encap:Ethernet HWaddr 00:00:0E:D9:40:84 inet addr:172.16.134.116 Bcast:172.16.134.127 Mask:255.255.255.128 inet6 addr: fe80::200:eff:fed9:4084/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4946 errors:0 dropped:0 overruns:0 frame:0 TX packets:1446 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1147372 (1.0 MiB) TX bytes:206570 (201.7 KiB) 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:20 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1882 (1.8 KiB) TX bytes:1882 (1.8 KiB) sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr 00:08:A1:87:55:EA inet addr:172.16.198.52 Bcast:172.16.198.127 Mask:255.255.255.128 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Memory:f4202000-f4204000 Please teach me what is wrong ? Thanks you and best regards, -- TRUONG TAN SON Fujitsu Computer Products of Vietnam. Network System section. email:so...@fc... |