From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom London Subject: Re: return of ip_rt_bug() Date: Fri, 5 Aug 2011 06:37:48 -0700 Message-ID: References: <20110802170942.GA17164@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Dave Jones , netdev@vger.kernel.org To: Julian Anastasov Return-path: Received: from mail-qy0-f181.google.com ([209.85.216.181]:48695 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753008Ab1HENhs convert rfc822-to-8bit (ORCPT ); Fri, 5 Aug 2011 09:37:48 -0400 Received: by qyk34 with SMTP id 34so393122qyk.19 for ; Fri, 05 Aug 2011 06:37:48 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Aug 5, 2011 at 6:30 AM, Tom London wrote: > On Fri, Aug 5, 2011 at 6:18 AM, Tom London wrote: >> On Fri, Aug 5, 2011 at 12:56 AM, Julian Anastasov wrote: >>> >>> =A0 =A0 =A0 =A0Hello, >>> >>> On Thu, 4 Aug 2011, Tom London wrote: >>> >>>> So, my router is just giving my wired NIC different addresses.... >>>> >>>> More I can provide? >>> >>> =A0 =A0 =A0 =A0Thanks! Can you check in dmesg or in another log >>> about the first IP address in such line: >>> >>> printk(KERN_DEBUG "ip_rt_bug: %pI4 -> %pI4, %s\n" >>> >>> =A0 =A0 =A0 =A0Is it now 192.168.2.6 ? >>> >>> Regards >>> >>> -- >>> Julian Anastasov >>> >> >> Sorry, don't see those messages. =A0I guess I'll have to reboot with >> 'debug' to see that. >> >> Before I do that, I booted this time with the RFKILL switch set to >> kill the radio (both BT and WIFI), and reran the above tests. >> >> Here is what 'ip monitor' said: >> >> [root@tlondon ~]# ip monitor >> 192.168.2.1 dev eth0 lladdr 00:1c:df:e2:3e:e9 STALE >> 192.168.2.1 dev eth0 lladdr 00:1c:df:e2:3e:e9 REACHABLE >> 192.168.2.1 dev eth0 lladdr 00:1c:df:e2:3e:e9 STALE >> 192.168.2.1 dev eth0 lladdr 00:1c:df:e2:3e:e9 STALE >> ff02::fb via ff02::fb dev eth0 =A0metric 0 >> =A0 =A0cache >> 192.168.2.1 dev eth0 lladdr 00:1c:df:e2:3e:e9 STALE >> >> Here is what 'inotail -f /var/log/messages' said: >> >> >> Aug =A05 06:12:21 tlondon kernel: [ =A0536.727187] usb 3-1: new full= speed >> USB device number 2 using uhci_hcd >> Aug =A05 06:12:21 tlondon kernel: [ =A0537.315296] usb 3-1: New USB = device >> found, idVendor=3D04b8, idProduct=3D010a >> Aug =A05 06:12:21 tlondon kernel: [ =A0537.315308] usb 3-1: New USB = device >> strings: Mfr=3D1, Product=3D2, SerialNumber=3D0 >> Aug =A05 06:12:21 tlondon kernel: [ =A0537.315317] usb 3-1: Product:= Perfection1640 >> Aug =A05 06:12:21 tlondon kernel: [ =A0537.315323] usb 3-1: Manufact= urer: EPSON >> Aug =A05 06:12:21 tlondon mtp-probe: checking bus 3, device 2: >> "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1" >> Aug =A05 06:12:22 tlondon mtp-probe: bus: 3, device: 2 was not an MT= P device >> >> So, no WARN_ON messages. >> >> I'd like to conclude that this is due to UDP casting on the wlan. >> I'll reboot with the radio on and in debug mode to see what happens. >> >> tom >> -- >> Tom London >> > > Hmmm, first attempt at recreating in debug mode didn't actually > produce any WARN_ON reports. > > 'ip monitor' did say: > > [root@tlondon ~]# ip monitor > 239.255.255.250 dev eth0 lladdr 01:00:5e:7f:ff:fa NOARP > 3: wlan0: > =A0 =A0link/ether > ff02::2 dev wlan0 lladdr 33:33:00:00:00:02 NOARP > ff02::16 dev wlan0 lladdr 33:33:00:00:00:16 NOARP > ff02::1:ffac:c692 dev wlan0 lladdr 33:33:ff:ac:c6:92 NOARP > 192.168.2.1 dev eth0 lladdr 00:1c:df:e2:3e:e9 STALE > 3: wlan0: > =A0 =A0link/ether > > Will try one more time. > > tom > > -- > Tom London > Can't seem to reproduce this when I boot with 'debug' on the boot line. Here is what 'ip monitor' says: [root@tlondon ~]# ip monitor ff02::1:ffac:c692 dev wlan0 lladdr 33:33:ff:ac:c6:92 NOARP ff02::16 dev wlan0 lladdr 33:33:00:00:00:16 NOARP ff02::2 dev wlan0 lladdr 33:33:00:00:00:02 NOARP 3: wlan0: link/ether tom --=20 Tom London