Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Hi, wrt http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595265 This was fixed in 2.6.36 with the following commit: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fccec10b33503a2b1197c8e7a3abd30443bedb08 Are you still using oldstable and would be in a position to test the patch for the squeeze kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130711194937.gc22...@inutil.org
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Ben Hutchings b...@decadent.org.uk : [...] Arnout Boelens reported that his RTL8111/8168B fails to link-up after suspend and resume, both under Debian's kernel based on 2.6.32 and under 2.6.36-rc6. Full details are at http://bugs.debian.org/595265, though the log isn't very informative: [31837.396594] PM: Finishing wakeup. [31837.396597] Restarting tasks ... done. [31840.267267] r8169: eth0: link down Can you suggest how to investigate this further? Something like the patch made by Stanislaw at : https://bugzilla.redhat.com/show_bug.cgi?id=502974 -- Ueimor -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101018214536.ga14...@electric-eye.fr.zoreil.com
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Eric Dumazet eric.duma...@gmail.com :
Le lundi 18 octobre 2010 à 23:45 +0200, Francois Romieu a écrit :
[...]
Something like the patch made by Stanislaw at :
https://bugzilla.redhat.com/show_bug.cgi?id=502974
Seems to be down at this moment, patch is also here (and included in
2.6.36-rc8 ) :
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=aeb19f6052b5e5c8a24aa444fbff73b84341beac
It's from the same author but it is not included in 2.6.36-stg yet :
Subject: [PATCH] r8169 init phy when resume
For unknown reasons some r8169 devices after resume operate at
100 Mb/s speed instead of 1000 Mb/s like before suspend. To fix
reset phy during resume.
Signed-off-by: Stanislaw Gruszka sgrus...@redhat.com
---
drivers/net/r8169.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c
index 17382c3..a4ce127 100644
--- a/drivers/net/r8169.c
+++ b/drivers/net/r8169.c
@@ -4847,6 +4847,9 @@ static int rtl8169_resume(struct device *device)
{
struct pci_dev *pdev = to_pci_dev(device);
struct net_device *dev = pci_get_drvdata(pdev);
+ struct rtl8169_private *tp = netdev_priv(dev);
+
+ rtl8169_init_phy(dev, tp);
if (!netif_running(dev))
goto out;
--
1.7.1
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20101019230647.ga17...@electric-eye.fr.zoreil.com
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Mon, 2010-10-18 at 23:45 +0200, Francois Romieu wrote: Ben Hutchings b...@decadent.org.uk : [...] Arnout Boelens reported that his RTL8111/8168B fails to link-up after suspend and resume, both under Debian's kernel based on 2.6.32 and under 2.6.36-rc6. Full details are at http://bugs.debian.org/595265, though the log isn't very informative: [31837.396594] PM: Finishing wakeup. [31837.396597] Restarting tasks ... done. [31840.267267] r8169: eth0: link down Can you suggest how to investigate this further? Something like the patch made by Stanislaw at : https://bugzilla.redhat.com/show_bug.cgi?id=502974 Thanks. Arnout, please test the patch https://bugzilla.redhat.com/attachment.cgi?id=454034, following the instructions at http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Le lundi 18 octobre 2010 à 23:45 +0200, Francois Romieu a écrit : Ben Hutchings b...@decadent.org.uk : [...] Arnout Boelens reported that his RTL8111/8168B fails to link-up after suspend and resume, both under Debian's kernel based on 2.6.32 and under 2.6.36-rc6. Full details are at http://bugs.debian.org/595265, though the log isn't very informative: [31837.396594] PM: Finishing wakeup. [31837.396597] Restarting tasks ... done. [31840.267267] r8169: eth0: link down Can you suggest how to investigate this further? Something like the patch made by Stanislaw at : https://bugzilla.redhat.com/show_bug.cgi?id=502974 Seems to be down at this moment, patch is also here (and included in 2.6.36-rc8 ) : http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=aeb19f6052b5e5c8a24aa444fbff73b84341beac -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1287442257.2361.11.ca...@edumazet-laptop
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Sunday 10 October 2010 21:27:01 Ben Hutchings wrote: On Tue, 2010-09-21 at 16:24 -0400, Arnout Boelens wrote: On Sunday 19 September 2010 20:59:59 Ben Hutchings wrote: On Wed, 2010-09-08 at 10:45 -0400, Arnout Boelens wrote: On Friday 03 September 2010 19:00:24 Ben Hutchings wrote: On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. Oops.. See below: [...] Unfortunately that didn't add much information. However, I did notice that we accidentally removed a bug fix to r8169 in version 2.6.32-19, which I have restored in version 2.6.32-23. Can you test version 2.6.32-23 (currently in unstable)? I just updated to kernel 2.6.32-23 but I am having the same issue. Could you test Linux 2.6.36-rc6 from experimental? Still the same thing happening.. A. Ben. smime.p7s Description: S/MIME cryptographic signature
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Arnout Boelens reported that his RTL8111/8168B fails to link-up after suspend and resume, both under Debian's kernel based on 2.6.32 and under 2.6.36-rc6. Full details are at http://bugs.debian.org/595265, though the log isn't very informative: [31837.396594] PM: Finishing wakeup. [31837.396597] Restarting tasks ... done. [31840.267267] r8169: eth0: link down Can you suggest how to investigate this further? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Tue, 2010-09-21 at 16:24 -0400, Arnout Boelens wrote: On Sunday 19 September 2010 20:59:59 Ben Hutchings wrote: On Wed, 2010-09-08 at 10:45 -0400, Arnout Boelens wrote: On Friday 03 September 2010 19:00:24 Ben Hutchings wrote: On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. Oops.. See below: [...] Unfortunately that didn't add much information. However, I did notice that we accidentally removed a bug fix to r8169 in version 2.6.32-19, which I have restored in version 2.6.32-23. Can you test version 2.6.32-23 (currently in unstable)? I just updated to kernel 2.6.32-23 but I am having the same issue. Could you test Linux 2.6.36-rc6 from experimental? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Sunday 19 September 2010 20:59:59 Ben Hutchings wrote: On Wed, 2010-09-08 at 10:45 -0400, Arnout Boelens wrote: On Friday 03 September 2010 19:00:24 Ben Hutchings wrote: On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. Oops.. See below: [...] Unfortunately that didn't add much information. However, I did notice that we accidentally removed a bug fix to r8169 in version 2.6.32-19, which I have restored in version 2.6.32-23. Can you test version 2.6.32-23 (currently in unstable)? I just updated to kernel 2.6.32-23 but I am having the same issue. Arnout Ben. smime.p7s Description: S/MIME cryptographic signature
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Wed, 2010-09-08 at 10:45 -0400, Arnout Boelens wrote: On Friday 03 September 2010 19:00:24 Ben Hutchings wrote: On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. Oops.. See below: [...] Unfortunately that didn't add much information. However, I did notice that we accidentally removed a bug fix to r8169 in version 2.6.32-19, which I have restored in version 2.6.32-23. Can you test version 2.6.32-23 (currently in unstable)? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Friday 03 September 2010 19:00:24 Ben Hutchings wrote: On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. Oops.. See below: [31830.208110] PM: Syncing filesystems ... done. [31832.102114] PM: Preparing system for mem sleep [31832.102371] Freezing user space processes ... (elapsed 0.04 seconds) done. [31832.152316] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [31832.152364] PM: Entering mem sleep [31832.152381] Suspending console(s) (use no_console_suspend to debug) [31832.177489] btusb_intr_complete: hci0 urb c98b0980 failed to resubmit (1) [31832.178485] btusb_bulk_complete: hci0 urb c98b0b00 failed to resubmit (1) [31832.179484] btusb_bulk_complete: hci0 urb c98b0800 failed to resubmit (1) [31832.224053] sd 0:0:0:0: [sda] Synchronizing SCSI cache [31832.543124] sd 0:0:0:0: [sda] Stopping disk [31833.634094] sdhci-pci :04:01.2: PCI INT B disabled [31833.972152] ata2: port disabled. ignoring. [31833.972232] ata_piix :00:1f.1: PCI INT A disabled [31833.972248] ehci_hcd :00:1d.7: PCI INT A disabled [31833.972259] uhci_hcd :00:1d.3: PCI INT D disabled [31833.972270] uhci_hcd :00:1d.2: PCI INT C disabled [31833.972281] uhci_hcd :00:1d.1: PCI INT B disabled [31833.972292] uhci_hcd :00:1d.0: PCI INT A disabled [31834.180111] HDA Intel :00:1b.0: PCI INT A disabled [31834.196659] r8169 :02:00.0: PME# enabled [31834.228613] ACPI: Preparing to enter system sleep state S3 [31834.400012] Disabling non-boot CPUs ... [31834.400034] CPU0 attaching NULL sched-domain. [31834.400037] CPU1 attaching NULL sched-domain. [31834.464015] CPU0 attaching NULL sched-domain. [31834.568025] CPU 1 is now offline [31834.568029] SMP alternatives: switching to UP code [31834.573035] Back to C! [31834.573035] CPU0: Thermal monitoring enabled (TM2) [31834.573035] Force enabled HPET at resume [31834.573035] Enabling non-boot CPUs ... [31834.573035] SMP alternatives: switching to SMP code [31834.577941] Booting processor 1 APIC 0x1 ip 0x6000 [31834.572686] Initializing CPU#1 [31834.572686] CPU: L1 I cache: 32K, L1 D cache: 32K [31834.572686] CPU: L2 cache: 2048K [31834.572686] CPU: Physical Processor ID: 0 [31834.572686] CPU: Processor Core ID: 1 [31834.572686] CPU1: Thermal monitoring enabled (TM2) [31834.668111] CPU1: Genuine Intel(R) CPU T2300 @ 1.66GHz stepping 08 [31834.668221] CPU0 attaching NULL sched-domain. [31834.696018] CPU0 attaching sched-domain: [31834.696022] domain 0: span 0-1 level MC [31834.696024] groups: 0 1 [31834.696029] CPU1 attaching sched-domain: [31834.696032] domain 0: span 0-1 level MC [31834.696034] groups: 1 0 [31834.696603] CPU1 is up [31834.697041] ACPI: Waking up from system sleep state S3 [31834.953155] pcieport :00:01.0: restoring config space at offset 0xf (was 0xa0100, writing 0xa010b) [31834.953163] pcieport :00:01.0: restoring config space at offset 0xa (was 0xf, writing 0x0) [31834.953169] pcieport :00:01.0: restoring config space at offset 0x8 (was 0xfdf0, writing 0xfdf0fdf0) [31834.953223] HDA Intel :00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [31834.953258] pcieport :00:1c.0: restoring config space at offset 0xf (was 0x20100, writing 0x20105) [31834.953280] pcieport :00:1c.0: restoring config space at offset 0x3 (was 0x81, writing 0x810008) [31834.953331] pcieport :00:1c.3: restoring config space at offset 0xf (was 0x20400, writing 0x20403) [31834.953347] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x1010, writing 0x20001010) [31834.953358] pcieport :00:1c.3: restoring config space at offset 0x3 (was 0x81, writing 0x810008) [31834.953472] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 0x280, writing 0x281) [31834.953539] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 0x290, writing 0x292) [31834.953563] pci :00:1e.0: restoring config space at offset 0xf (was 0x2, writing 0x200ff) [31834.953640] pci :00:1f.0: power state changed by ACPI to D0 [31834.953683] pci :00:1f.0: power state changed by ACPI to D0 [31834.953756] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 0x281, writing 0x2880005) [31834.953790] radeon :01:00.0: restoring config space at offset 0x1 (was 0x100400, writing 0x100407) [31834.953843] r8169 :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [31834.953856] r8169 :02:00.0: restoring config space at offset 0xc (was 0x1, writing 0xfe0e) [31834.953875] r8169 :02:00.0: restoring config space
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
On Thu, 2010-09-02 at 11:43 -0400, Arnout Boelens wrote: Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. Can you send a kernel log covering the time when you suspend and resume? The log section included in your original report is full of firewall warnings. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#595265: linux-image-2.6.32-5-686: Nerwork card fails to come up again after suspend
Package: linux-2.6 Version: 2.6.32-21 Severity: normal After suspending my laptop my network card fails to come back up again. As workaround I unload the kernel module for my card (r8169) and reload it again. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed Aug 25 14:28:12 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/laptop-root ro kopt=root=/dev/mapper/laptop-root ro ipv6.disable=1 quiet ** Not tainted ** Kernel log: [50418.395549] r8169: eth0: link down [50419.925248] r8169: eth0: link up [50423.369277] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1d:92:75:61:d2:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=32 ID=17978 PROTO=UDP SPT=68 DPT=67 LEN=308 [50424.633601] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1e:37:82:92:fa:08:00 SRC=172.30.68.245 DST=172.30.71.255 LEN=229 TOS=0x00 PREC=0x00 TTL=128 ID=51332 PROTO=UDP SPT=138 DPT=138 LEN=209 [50424.697994] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1a:a0:9a:03:ef:08:00 SRC=172.30.70.126 DST=255.255.255.255 LEN=68 TOS=0x00 PREC=0x00 TTL=128 ID=11999 PROTO=UDP SPT=1027 DPT=1947 LEN=48 [50424.715038] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC= SRC=172.30.68.46 DST=224.0.0.251 LEN=93 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=73 [50425.693236] AIF:ICMP-request: IN=eth0 OUT= MAC=00:17:31:c1:7e:4d:00:1f:29:58:2b:47:08:00 SRC=172.30.70.254 DST=172.30.68.46 LEN=48 TOS=0x00 PREC=0x00 TTL=255 ID=39957 PROTO=ICMP TYPE=8 CODE=0 ID=55935 SEQ=0 [50433.463867] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:32:c1:d6:4e:08:00 SRC=172.30.68.119 DST=172.30.71.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=38623 PROTO=UDP SPT=50416 DPT=137 LEN=58 [50435.026440] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:25:00:a1:ec:64:08:00 SRC=172.30.70.189 DST=224.0.0.251 LEN=1168 TOS=0x00 PREC=0x00 TTL=255 ID=23131 PROTO=UDP SPT=5353 DPT=5353 LEN=1148 [50435.754268] AIF:Connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:01:ac:67:06:0f:e3:d0:08:00 SRC=172.30.70.39 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xA0 TTL=1 ID=3994 PROTO=2 [50435.755368] AIF:Connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:80:77:cb:12:5e:08:00 SRC=128.119.70.33 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=36574 PROTO=2 [50435.755448] AIF:Connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:26:4a:0e:5d:94:08:00 SRC=172.31.70.57 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=46461 PROTO=2 [50436.768282] AIF:Connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:0e:7f:42:b3:af:08:00 SRC=128.119.70.83 DST=224.0.0.251 LEN=28 TOS=0x00 PREC=0x00 TTL=1 ID=35010 PROTO=2 [50443.396679] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:dd:08:cb:30:b6:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=338 TOS=0x00 PREC=0x00 TTL=128 ID=0 PROTO=UDP SPT=68 DPT=67 LEN=318 [50445.077406] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:22:19:fd:43:01:08:00 SRC=172.30.71.24 DST=172.30.71.255 LEN=264 TOS=0x00 PREC=0x00 TTL=128 ID=12186 PROTO=UDP SPT=6646 DPT=6646 LEN=244 [50453.482057] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:22:19:fd:43:01:08:00 SRC=172.30.71.24 DST=172.30.71.255 LEN=96 TOS=0x00 PREC=0x00 TTL=128 ID=12403 PROTO=UDP SPT=137 DPT=137 LEN=76 [50455.243887] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:23:32:cc:d2:6e:08:00 SRC=172.30.69.114 DST=255.255.255.255 LEN=179 TOS=0x00 PREC=0x00 TTL=64 ID=23363 PROTO=UDP SPT=17500 DPT=17500 LEN=159 [50463.696195] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:1f:16:16:ef:0a:08:00 SRC=172.30.69.7 DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=128 ID=4522 PROTO=UDP SPT=68 DPT=67 LEN=308 [50466.694457] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:23:32:cc:d2:6e:08:00 SRC=172.30.69.114 DST=224.0.0.251 LEN=922 TOS=0x18 PREC=0x00 TTL=255 ID=28953 PROTO=UDP SPT=5353 DPT=5353 LEN=902 [50473.600832] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:24:be:b0:fb:f6:08:00 SRC=172.30.70.105 DST=172.30.71.255 LEN=96 TOS=0x00 PREC=0x00 TTL=128 ID=108 PROTO=UDP SPT=137 DPT=137 LEN=76 [50475.712655] AIF:UNPRIV connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:00:23:32:cc:d2:6e:08:00 SRC=172.30.69.114 DST=224.0.0.251 LEN=922 TOS=0x18 PREC=0x00 TTL=255 ID=48916 PROTO=UDP SPT=5353 DPT=5353 LEN=902 [50483.420922] AIF:PRIV connect attempt: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:64:b9:e8:cb:c1:18:08:00 SRC=172.30.71.190 DST=172.30.71.255 LEN=78 TOS=0x00 PREC=0x00 TTL=64 ID=12767 PROTO=UDP SPT=53857 DPT=137 LEN=58 [50484.231369] AIF:Connect attempt: IN=eth0 OUT= MAC=01:00:5e:00:00:fb:7c:c5:37:a7:31:b8:08:00 SRC=172.30.70.202 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=35965 PROTO=2 [50485.226728] AIF:UNPRIV
