Posted by: isaraffee | August 29, 2009

Exploring the /var/log/syslog when Wifi device is detected in Mandrivia 2009

Exploring the /var/log/syslog when Wifi device is detected in Mandrivia Spring 2009

Below are the messages recorded in the /var/log/syslog:

Aug 23 09:12:12 localhost klogd: usb 1-4: new high speed USB device using ehci_hcd and address 2

Aug 23 09:12:12 localhost klogd: usb 1-4: New USB device found, idVendor=148f, idProduct=2573

Aug 23 09:12:12 localhost klogd: usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Aug 23 09:12:12 localhost klogd: usb 1-4: Product: 54M.USB…….

Aug 23 09:12:12 localhost klogd: usb 1-4: Manufacturer: Ralink

Aug 23 09:12:12 localhost klogd: usb 1-4: configuration #1 chosen from 1 choice

Aug 23 09:12:12 localhost klogd: wmaster0 (rt73usb): not using net_device_ops yet

Aug 23 09:12:12 localhost klogd: phy0: Selected rate control algorithm ‘minstrel’

Aug 23 09:12:12 localhost klogd: wlan0 (rt73usb): not using net_device_ops yet

Aug 23 09:12:12 localhost klogd: Registered led device: rt73usb-phy0:radio

Aug 23 09:12:12 localhost klogd: Registered led device: rt73usb-phy0:assoc

Aug 23 09:12:12 localhost klogd: Registered led device: rt73usb-phy0:quality

Aug 23 09:12:12 localhost klogd: udev: renamed network interface wlan0 to wlan1

Aug 23 09:12:12 localhost klogd: rt73usb 1-4:1.0: firmware: requesting rt73.bin

Aug 23 09:12:13 localhost klogd: ADDRCONF(NETDEV_UP): wlan1: link is not ready

Aug 23 09:12:13 localhost klogd: cfg80211: Calling CRDA for country: SG

Aug 23 09:12:13 localhost klogd: cfg80211: Regulatory domain changed to country: SG

Aug 23 09:12:13 localhost klogd: ^I(start_freq – end_freq @ bandwidth), (max_antenna_gain, max_eirp)

Aug 23 09:12:13 localhost klogd: ^I(2402000 KHz – 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)

Aug 23 09:12:13 localhost klogd: ^I(5170000 KHz – 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)

Aug 23 09:12:13 localhost klogd: ^I(5250000 KHz – 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)

Aug 23 09:12:13 localhost klogd: ^I(5735000 KHz – 5835000 KHz @ 40000 KHz), (N/A, 2000 mBm)

Aug 23 09:12:13 localhost ifplugd(wlan1)[5410]: ifplugd 0.28 initializing.

Aug 23 09:12:13 localhost ifplugd(wlan1)[5410]: Using interface wlan1/00:19:E0:18:6F:D8

Aug 23 09:12:13 localhost ifplugd(wlan1)[5410]: Using detection mode: wireless extension

Aug 23 09:12:13 localhost ifplugd(wlan1)[5410]: Initialization complete, link beat not detected.

Aug 23 09:12:51 localhost klogd: wlan1: authenticate with AP 00:1e:10:09:8d:58

Aug 23 09:12:51 localhost klogd: wlan1: authenticated

Aug 23 09:12:51 localhost klogd: wlan1: associate with AP 00:1e:10:09:8d:58

Aug 23 09:12:51 localhost klogd: wlan1: RX AssocResp from 00:1e:10:09:8d:58 (capab=0x411 status=0 aid=1)

Aug 23 09:12:51 localhost klogd: wlan1: associated

Aug 23 09:12:51 localhost klogd: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready

Aug 23 09:12:52 localhost ifplugd(wlan1)[5410]: Link beat detected.

Aug 23 09:12:52 localhost avahi-daemon[3361]: Registering new address record for fe80::219:e0ff:fe18:6fd8 on wlan1.*.

Aug 23 09:12:53 localhost ifplugd(wlan1)[5410]: Executing ‘/etc/ifplugd/ifplugd.action wlan1 up’.

Aug 23 09:12:56 localhost dhclient: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6

Aug 23 09:12:56 localhost dhclient: DHCPOFFER from 192.168.1.1

Aug 23 09:12:56 localhost dhclient: DHCPREQUEST on wlan1 to 255.255.255.255 port 67

Aug 23 09:12:56 localhost dhclient: DHCPACK from 192.168.1.1

Aug 23 09:12:56 localhost avahi-daemon[3361]: Joining mDNS multicast group on interface wlan1.IPv4 with address 192.168.1.101.

Aug 23 09:12:56 localhost avahi-daemon[3361]: New relevant interface wlan1.IPv4 for mDNS.

Aug 23 09:12:56 localhost avahi-daemon[3361]: Registering new address record for 192.168.1.101 on wlan1.IPv4.

Aug 23 09:12:56 localhost NET[6933]: /sbin/dhclient-script : updated /etc/resolv.conf

Aug 23 09:12:56 localhost dhclient: bound to 192.168.1.101 — renewal in 37846 seconds.

Aug 23 09:12:56 localhost ifplugd(wlan1)[5410]: client: Determining IP information for wlan1… done.

Aug 23 09:12:56 localhost ifplugd(wlan1)[5410]: Program executed successfully.

Some important things to take note from the above log file are:

  • The manufacturer of the Wifi device, Ralink was detected.
  • The wifi rt73usb module is loaded
  • The firmware for rt73usb, rt73usb.bin was loaded
  • wlan1 and not wlan0 is used as the Wifi interface
  • ifplugd is running
  • dhclient request for IP address
  • /etc/resolve.conf which contained the nameserver ip address is updated

and the Wifi device is ready

Important:

In case you are connected and it seems to take a very long time to access any web sites, take a lokk at the /etc/resolv.conf file:

[root@localhost ~]# more /etc/resolv.conf

nameserver 172.16.0.1

nameserver 192.168.1.1

In this such cases as shown above there are two nameservers. That is reason why it takes a very long time to access any sites. This is because the first IP address is a private IP address. You need to remove this IP address. The other IP address 192..168.1.1 eventhough it’s a private IP but it is the IP address of the modem router which is connected to the Internet.

Another command to show the routing table is:

[root@localhost ~]# ip route show

192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.101 metric 35

172.16.0.0/16 dev eth0 proto kernel scope link src 172.16.0.2 metric 10

169.254.0.0/16 dev eth0 scope link metric 10

169.254.0.0/16 dev wlan1 scope link metric 35

default via 172.16.0.1 dev eth0 metric 10

default via 192.168.1.1 dev wlan1 metric 35

In the output above, the network ID 172.16 has a lower metric value than the 192.168.1 network, which means the routing of the packets to the Internet will take the 172.16 path.

The solution is to remove the nameserver entry which read 172.16.0.1. You can edit thile but any changes will be overwritten by the Nework Manager. So I suggest you use Network Center to disconnect the eth0. After I disconnect eth0, the /etc/resolv.conf looks like the one below:

[root@localhost ~]# more /etc/resolv.conf

nameserver 192.168.1.1

With that you can definitely access the Internet.

Another way which you could stop eth0, is by typing:

[root@localhost ~]# ifconfig eth0 down

Then check that the routing table is updated

[root@localhost ~]# ip route show

192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.101 metric 35

169.254.0.0/16 dev wlan1 scope link metric 35

default via 192.168.1.1 dev wlan1 metric 35

Yes the network 172.16 network is gone.

But sadly the /etc/resolv.conf is not updated and ifconfig eth0 also shows that it still have the IP address assigned as shown below:

[root@localhost ~]# more /etc/resolv.conf

nameserver 172.16.0.1

nameserver 192.168.1.1

[root@localhost ~]# ifconfig eth0

eth0 Link encap:Ethernet HWaddr 00:E0:4D:69:5B:94

inet addr:172.16.0.2 Bcast:172.16.255.255 Mask:255.255.0.0

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:

So you have to disconnect eth0 by Network Manager

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: