Strange, fluctuating network connectivity

pelskikker · May 28, 2014, 7:17pm

For some reason my Opensuse OS (latest version) will not connect to the internet. I googled a lot and the best advice I found was doing:

systemctl stop network.service
systemctl --force enable NetworkManager.service
systemctl start network.service

This worked out great the first time, good the second time and every time after that it works less great. For some reason it takes longer and longer for the system to get an ethernet connection (wired, not wireless). Just today I tried this four times and nothing worked, I continued my linux lessons offline (using books) and after about 15 minutes the connection just worked out of itself.

I installed Opensuse a few days back, I first tried Centos but under Centos I never had any internet (the same issue).
The fact that the issues are the same makes me believe it is not as much a configuration issue but more hardware related.
Under Windows it was no problem, network functionality worked right at the start.

Under Centos the best help I found online was to use the command

dhclient eth0

This worked great the first time, after the first reboot the command no longer worked and the system staid offline. I reinstalled Centos and used the command and poof internet, I rebooted the system and nothing brought internet back online. At that point I decided against keeping to reinstall it every day :).
Under centos I tried every modification I could google (editing a number of configuration files).

Using dhclient enp3s0 in Suse (what was wrong with eth0 that in Opensuse such a strange name is used) does not work under Opensuse as I get an error stating that a path cannot be found. However, I notice that in the path at some point there are two slashes (//) and I assume that makes any path unfindable, the system says → ls: cannot access /var/run/netconfig//wlp4s6/: No such file or directory

Furthermore, older linux varieties normally had no problem (as far as I can remember) with my network. I assume both Centos and Opensuse use a more current Kernel and if I read correctly hardware support is - at least to some extend - handled in the Kernel. Could it be that my motherboard integrated networkcard is no longer fully supported? I run an about 3 years old Gigabyte UDH-3 mainboard for AMD (I will try to find the exact mainboard type somewhere). I would assume that 3 years old is still within the scope of what Linux supports. I mean, afaik systems at the age of 10 are still supported.

Any help is appreciated.

Regards,

Bart

deano_ferrari · May 28, 2014, 10:53pm

None of the poking around with the commands you’ve been invoking should be necessary. Starting from the top, tell us the following

openSUSE version and desktop environment you’re using
Tell us more about your network hardware

/usr/sbin/hwinfo --netcard

/usr/sbin/hwinfo --network

*Please make sure to enclose your output within

...[/CO..] tags


> Using dhclient enp3s0 in Suse (what was wrong with eth0 that in Opensuse such a strange name is used) does not work under Opensuse as I get an error stating that a path cannot be found.

This is known predictable naming. (It is possible to disable  this and use the older naming scheme, but I wouldn't recommend it for now.)

http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

pelskikker · May 29, 2014, 4:45pm

Hello Deano_Ferrari,
Thanks for replying. Here is the requested info.

By the way, the system gives info about both the ethernet card as well as the wifi adapter. My computer is out of range of wifi, it barely connects to it but cannot transfer data as the connection is too bad. For some reason the wifi adapter does work (at least it immediately finds networks and is capable of connecting) and only the ethernet connection does not. Or better said, it takes about 20 minutes before an ethernet connection is established if I don’t do anything. In the meantime it constantly says the cable is not connected. I know I said the connection fluctuates as that it sometimes works and sometimes not, but now after another day it is that I believe stopping and starting the network is not what makes it work but just the 20 minute wait. After the connection is made it functions continuously.

The version of OpenSuse is 13.1 (called Bottle) running Kernel 3.11.10-11 (according to the CLI login screen)
I am running the KDE desktop

Output of /usr/sbin/hwinfo --netcard

X1:/home/bart # /usr/sbin/hwinfo --netcard
34: PCI 300.0: 0200 Ethernet controller                         
  [Created at pci.319]
  Unique ID: UOJ9.YNURYwd7hn8
  Parent ID: bSAa.8EaoC3U4NBD
  SysFS ID: /devices/pci0000:00/0000:00:0a.0/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
  SubVendor: pci 0x1458 "Giga-byte Technology"
  SubDevice: pci 0xe000 "GA-EP45-DS5 Motherboard"
  Revision: 0x03
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp3s0
  I/O Ports: 0xce00-0xceff (rw)
  Memory Range: 0xfdfff000-0xfdffffff (ro,non-prefetchable)
  Memory Range: 0xfdff8000-0xfdffbfff (ro,non-prefetchable)
  Memory Range: 0xfdf00000-0xfdf1ffff (ro,non-prefetchable,disabled)
  IRQ: 50 (28281 events)
  HW Address: 1c:6f:65:3c:c9:71
  Link detected: yes
  Module Alias: "pci:v000010ECd00008168sv00001458sd0000E000bc02sc00i00"
  Driver Info #0:
    Driver Status: r8169 is active
    Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #30 (PCI bridge)

35: PCI 406.0: 0282 WLAN controller
  [Created at pci.319]
  Unique ID: HaOD.OZDZtb7P420
  Parent ID: qscc.UsCA9N2eQqB
  SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:04:06.0
  SysFS BusID: 0000:04:06.0
  Hardware Class: network
  Model: "RaLink RT2800 802.11n PCI"                                                                                                                                               
  Vendor: pci 0x1814 "RaLink"                                                                                                                                                      
  Device: pci 0x0601 "RT2800 802.11n PCI"                                                                                                                                          
  SubVendor: pci 0x1737 "Linksys"                                                                                                                                                  
  SubDevice: pci 0x0067 
  Driver: "rt2800pci"
  Driver Modules: "rt2800pci"
  Device File: wlp4s6
  Features: WLAN
  Memory Range: 0xfdde0000-0xfddeffff (rw,non-prefetchable)
  IRQ: 20 (2341 events)
  HW Address: 68:7f:74:fb:45:e3
  Link detected: no
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 36 38 40 44 46 48 149 151 153 157 159 161 165
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 5.18 5.19 5.2 5.22 5.23 5.24 5.745 5.755 5.765 5.785 5.795 5.805 5.825
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:v00001814d00000601sv00001737sd00000067bc02sc80i00"
  Driver Info #0:
    Driver Status: rt2800pci is active
    Driver Activation Cmd: "modprobe rt2800pci"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #20 (PCI bridge)

Output of /usr/sbin/hwinfo --network

X1:/home/bart # /usr/sbin/hwinfo --network
44: None 00.0: 10701 Ethernet                                   
  [Created at net.124]
  Unique ID: yDf5.ndpeucax6V1
  Parent ID: HaOD.M6wFxmxKwZC
  SysFS ID: /class/net/wlp4s6
  SysFS Device Link: /devices/pci0000:00/0000:00:14.4/0000:04:06.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "rt2800pci"
  Driver Modules: "rt2800pci"
  Device File: wlp4s6
  HW Address: 68:7f:74:fb:45:e3
  Link detected: no
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #28 (Ethernet controller)

45: None 00.0: 10701 Ethernet
  [Created at net.124]
  Unique ID: 92a1.ndpeucax6V1
  Parent ID: UOJ9.YNURYwd7hn8
  SysFS ID: /class/net/enp3s0
  SysFS Device Link: /devices/pci0000:00/0000:00:0a.0/0000:03:00.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: enp3s0
  HW Address: 1c:6f:65:3c:c9:71
  Link detected: yes
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #27 (Ethernet controller)

46: None 00.0: 10700 Loopback
  [Created at net.124]
  Unique ID: ZsBS.GQNx7L4uPNA
  SysFS ID: /class/net/lo
  Hardware Class: network interface
  Model: "Loopback network interface"
  Device File: lo
  Link detected: yes
  Config Status: cfg=no, avail=yes, need=no, active=unknown

deano_ferrari · May 30, 2014, 1:12am

You might try plugging in your ethernet cable and observe the output from

tail -f /var/log/messages

Since you’re using Network Manager, the following should also be of value

tail -f /var/log/NetworkManager

robin_listas · May 30, 2014, 2:12am

On 2014-05-29 16:46, pelskikker wrote:


> --------------------
>     X1:/home/bart # /usr/sbin/hwinfo --netcard
>   34: PCI 300.0: 0200 Ethernet controller
>   [Created at pci.319]
>   Unique ID: UOJ9.YNURYwd7hn8
>   Parent ID: bSAa.8EaoC3U4NBD
>   SysFS ID: /devices/pci0000:00/0000:00:0a.0/0000:03:00.0
>   SysFS BusID: 0000:03:00.0
>   Hardware Class: network
>   Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
>   Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
>   Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
>   SubVendor: pci 0x1458 "Giga-byte Technology"
>   SubDevice: pci 0xe000 "GA-EP45-DS5 Motherboard"

I have that same device, but from another maker. Works out of the box.


Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
SubVendor: pci 0x1462 "Micro-Star International Co., Ltd."
SubDevice: pci 0x516c
Revision: 0x02
Driver: "r8169"

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

pelskikker · May 30, 2014, 6:25pm

Today the machine got to networking in less then 3 minutes, that is pretty fast compared to the other days. I included the uptime command, maybe the time it takes the system to do something can tell you something.

tail -f /var/log/messages

X1:/home/bart # tail -f /var/log/messages
2014-05-30T18:15:53.693757+02:00 X1 kernel:   180.611361] fuse init (API version 7.22)
2014-05-30T18:15:53.694740+02:00 X1 systemd[1]: Mounting FUSE Control File System...
2014-05-30T18:15:53.700021+02:00 X1 systemd[1]: Mounted FUSE Control File System.
2014-05-30T18:15:59.922152+02:00 X1 systemd[974]: Time has been changed
2014-05-30T18:15:59.922535+02:00 X1 systemd[1336]: Time has been changed
2014-05-30T18:15:59.922846+02:00 X1 systemd[1]: Time has been changed
2014-05-30T18:16:12.905387+02:00 X1 kernel:   200.078846] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
2014-05-30T18:16:47.346120+02:00 X1 su: (to bart) bart on none
2014-05-30T18:16:47.347231+02:00 X1 su: pam_unix(su:session): session opened for user root by bart(uid=1000)
2014-05-30T18:16:47.349546+02:00 X1 su: pam_systemd(su:session): pam_putenv: delete non-existent entry; XDG_RUNTIME_DIR

tail -f /var/log/NetworkManager

X1:/home/bart # tail -f /var/log/NetworkManager
2014-05-30T18:15:48.163671+02:00 X1 NetworkManager[706]: <info>   nameserver '192.168.2.1'
2014-05-30T18:15:48.163903+02:00 X1 NetworkManager[706]: <info>   domain name 'Belkin'
2014-05-30T18:15:48.164196+02:00 X1 NetworkManager[706]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
2014-05-30T18:15:48.164435+02:00 X1 NetworkManager[706]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4 Commit) started...
2014-05-30T18:15:49.164907+02:00 X1 NetworkManager[706]: <info> (enp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
2014-05-30T18:15:49.165970+02:00 X1 NetworkManager[706]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4 Commit) complete.
2014-05-30T18:15:49.166759+02:00 X1 NetworkManager[706]: <info> (enp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
2014-05-30T18:15:49.170176+02:00 X1 NetworkManager[706]: <info> NetworkManager state is now CONNECTED_GLOBAL
2014-05-30T18:15:49.170817+02:00 X1 NetworkManager[706]: <info> Policy set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS.
2014-05-30T18:15:49.175475+02:00 X1 NetworkManager[706]: <info> Activation (enp3s0) successful, device activated.

uptime

X1:/home/bart # uptime
 18:21  up   0:08,  3 users,  load average: 0,14, 0,17, 0,10

tsu2 · May 30, 2014, 7:03pm

Is your wireless adapter physically turned off?
If you also have an available wireless network, then your two connections to the Internet (does not matter whether through your same ISP or another network) will alternately be used and cause the problem you describe.

If available on your device, a hardware switch should be used to turn off the wireless adapter.
If a hardware switch doesn’t exist, in openSUSE you can install rfkill to turn your adapter(s) on or off.

You can always display what network adapters are active and available (not always actively connected but still bad) by either

ifconfig

ip addr

TSU

deano_ferrari · May 30, 2014, 11:26pm

I’d wondered about this too, but the wired interface is supposed to be preferred over the wireless as far as NM is concerned.

zoop · May 31, 2014, 1:48am

Have you tried getting a capture from the network card to see what it sees when the system is trying to get an IP?

You can use tcpdump. So in your case.

tcpdump -i enp3s0 -n

You should see the system sending out DHCP requests. I would imagine that you do not see replies. From there if that is the case I would look at the other side of it. See if it is recieving the Request from the computer. If you do see the reply and the computer is just ignoring it, I guess post back here with what you find.

Blazertr · June 2, 2014, 5:01am

Similar problem with r8169, Ip4v Gateway = No IP Gateway.
With iftub no problem for connection network/internet but with no other device connected same ip.
My devices are static ip’s. In Windows no problem…

My Devices is

Ipad 192.168.1.100 (wireless connect/MacID filtered)
Iphone 192.168.1.101 (wireless connect/MacID filtered)
Samsung Galaxy 192.168.1.102 (wireless connect/MacID filtered)
Linux-Blazer 192.168.1.111 (wired connect)
IBMPc 192.168.1.112 (wireless connect/MacID filtered)
GirlsPC 192.168.1.113 (wireless connect/MacID filtered)

Connect all Cisco Router same time
Probleme only in Linux - Blazer Suse 13.1 uptodate

192.168.1.111
255.255.255.0 Probleme in iftub ip change to 192.168.1.111/24 - 255.255.255.0 is disparu
192.168.1.1
77.92.1.4 -77.92.1.16

http://uploadingit.com/file/rqwglqal06yawpbi/snapshot1.png

in network manager Ip4v Gateway = No IP Gateway. internet connection ok but opened port close for tcp and udp.

Blazertr · June 2, 2014, 5:17am

http://uploadingit.com/file/ueavbrd8vwv27xo9/snapshot2.png

Ipv6 Disabled

deano_ferrari · June 2, 2014, 5:53am

@Blazertr: It is good practice to start your own thread when seeking help for an issue no matter how similar you believe it may be.

alanbortu · June 2, 2014, 6:41am

deano ferrari wrote:

>
> @Blazertr: It is good practice to start your own thread when seeking
> help for an issue no matter how similar you believe it may be.
>
>

And it never hurts to link to a thread related to the problem in your post
stating what happens when you try the suggested solution. That way people
can help you figure out if you made a mistake or if its a different problem.

pelskikker · June 2, 2014, 11:16pm

Here I am again, this weekends weather was so good I didn’t go back inside to the computer.

For some reason it seems the problem has in one way or another solved itself or better said it is workable now. The last three times I booted the system it did take way too much time to connect, but with about 3 minutes until a network connection is made it is doable. This makes me think that I actually might have made the problem worse by using those ’ systemctl start / force enable / stop commands’ which might have been the cause of having to wait 15 to 20 minutes each time. Probably because every other minute I was giving those commands as I was used to connecting in mere seconds with windows and this might have ‘reset’ whatever it is that takes my system a few minutes to establish a connection. Also, that under CentOS a connection was impossible might be a different problem (and in my mind I connected the dots when Opensuse had networking issues with my system too right after I switched from CentOS to Opensuse).

Still, I ofcourse tried all you guys suggested as something is not okay and if there are any good ideas I still love to hear them. Although it works, those 3 minutes are still mighty annoying :).
By the way, when doing the tcpdump I noticed the output header read ‘link-type EN10MB (Ethernet)’, after some googling I noticed that this can mean any speed 10/100/1000 but after doing:

ethtool enp3s0 I got the following

X1:/home/bart # ethtool enp3s0
Settings for enp3s0:
        Supported ports:  TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Half 1000baseT/Full 
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full 
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Speed: 10Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: yes

This means my system is running Full duplex @ 10 Mbit. The switch is set to auto negotiate, but if both the switch and the card support 100Mbit it is strange the system reverts to 10Mbit. I believe under windows I ran 100Mbit all the time, but this makes me wonder. I won’t reach 1Gbit as I am using the older cat 5 cables (quite an old cable), but for 100Mbit it should suffice. If I recall correctly when there is a problem between the switch and the NIC they can fall back to a half-duplex 10Mbit setting, so as the system is still running full duplex I am assuming the fact that the system runs at 10Mbit has nothing to do with a networking issue. It even registers no 100Mbit possibility on the switch which is mighty strange. As it is almost midnight here (about five hours ago my neighbor came for a short talk and I just returned) I will check the switch tomorrow to make sure it used to run 100Mbit. Maybe my memory is lagging. On the other hand, as the network is dead for about 3 minutes after which it runs at 10Mbit, it could be a networking problem. But if so, it is a networking problem under linux as under windows there is no problem at all. And during that 3 minute dead zone, tcpdump fails to register anything. As such it looks like the entire networking system is out. I mean, it should at least register something? Broadcasts enough on this network.

So here is the output:

ifconfig

X1:/home/bart # ifconfig
enp3s0    Link encap:Ethernet  HWaddr 1C:6F:65:3C:C9:71  
          inet addr:192.168.2.15  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fe80::1e6f:65ff:fe3c:c971/64 Scope:Link
          inet6 addr: 2002:5ed3:8eee:1234:1e6f:65ff:fe3c:c971/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11035 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7562 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:10929816 (10.4 Mb)  TX bytes:1189269 (1.1 Mb)

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:65536  Metric:1
          RX packets:42 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2804 (2.7 Kb)  TX bytes:2804 (2.7 Kb)

ip addr


X1:/home/bart # ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 1c:6f:65:3c:c9:71 brd ff:ff:ff:ff:ff:ff
    inet 192.168.2.15/24 brd 192.168.2.255 scope global enp3s0
       valid_lft forever preferred_lft forever
    inet6 2002:5ed3:8eee:1234:1e6f:65ff:fe3c:c971/64 scope global dynamic 
       valid_lft 292sec preferred_lft 112sec
    inet6 fe80::1e6f:65ff:fe3c:c971/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp4s6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 68:7f:74:fb:45:e3 brd ff:ff:ff:ff:ff:ff

Is the wireless adapter physically turned off?
Unfortunately that is impossible, as it is an internal card with an antenna sticking out the back of the system. I could remove the card from the case, but I doubt the problem is there as in NetworkManager the setting ‘draadloos activeren’ which is Dutch for ‘enable wireless’ is off and the wireless connection is - trough all the commands I have seen - unavailable. It is guaranteed not granted an ip and there is guaranteed no connection. Everytime I activate wireless I also need to enter a password for KWallet so it can connect (probably for the wireless password), I only get this box when I manually tick the ‘enable wireless’ option. Also, the wireless connection says ‘unavailable’ until I click the enable button after which it becomes ‘disconnected’. The last two words are translations, so if it actually says something else in English sorry :). But you’ll get what I mean.

tcpdump -i enp3s0 -n (after starting the system I could not remember what came after tcpdump so I gave the tcpdump command only)
I’d wish I could put some text in here, but right up to the point the connection was made there was nothing. When ctrl+c ended the command it gave 0 packets on all three options (captured, received, dropped). After the connection was made the screen got filled very fast. That however was something I already noticed back on windows with Wireshark, quite a busy line. And this is a dedicated line into the switch, so only direct addressed packets and broadcasts. I sometimes even see web domains passing trough that haven’t been opened in quite a while on the system. By the way, it is almost impossible that this system is infected with something. It is just too freshly installed.

I did a timed tcpdump of exactly 1 minute and it gave me the lines below. I do know a lot of network traffic happens even when you don’t do anything and I also noticed that it was a lot less busy then right after the connection. But still, this is quite a lot if you think about it that during the entire capture I did not touch a single button. I did however keer this window open. Info, 0 dropped packages.
The command was tcpdump -w outputtcpdump -nnvvvSe (the read with XX added). After I copy/pasted this into the code field I feel like hte only thing I did was occupy some server space on opensuse.org that probably could have been used better.


18:34:21.618580 1c:6f:65:3c:c9:71 > 00:22:75:24:39:b4, ethertype IPv4 (0x0800), length 90: (tos 0xc0, ttl 64, id 59916, offset 0, flags [DF], proto UDP (17), length 76)
    192.168.2.15.123 > 83.98.201.133.123: [udp sum ok] NTPv4, length 48
        Client, Leap indicator:  (0), Stratum 3 (secondary reference), poll 6 (64s), precision -23
        Root Delay: 0.013381, Root dispersion: 0.028121, Reference-ID: 85.12.35.12
          Reference Timestamp:  3610715424.632168948 (2014/06/02 18:30:24)
          Originator Timestamp: 3610715594.625965595 (2014/06/02 18:33:14)
          Receive Timestamp:    3610715594.630614876 (2014/06/02 18:33:14)
          Transmit Timestamp:   3610715661.618533253 (2014/06/02 18:34:21)
            Originator - Receive Timestamp:  +0.004649272
            Originator - Transmit Timestamp: +66.992567658
        0x0000:  0022 7524 39b4 1c6f 653c c971 0800 45c0  ."u$9..oe<.q..E.
        0x0010:  004c ea0c 4000 4011 7035 c0a8 020f 5362  .L..@.@.p5....Sb
        0x0020:  c985 007b 007b 0038 b5f4 2303 06e9 0000  ...{.{.8..#.....
        0x0030:  036d 0000 0733 550c 230c d737 2520 a1d5  .m...3U.#..7%...
        0x0040:  d2f8 d737 25ca a03f 4823 d737 25ca a16f  ...7%..?H#.7%..o
        0x0050:  f9fc d737 260d 9e58 31b8                 ...7&..X1.
18:34:21.630690 00:22:75:24:39:b4 > 1c:6f:65:3c:c9:71, ethertype IPv4 (0x0800), length 90: (tos 0x0, ttl 52, id 27457, offset 0, flags [DF], proto UDP (17), length 76)
    83.98.201.133.123 > 192.168.2.15.123: [udp sum ok] NTPv4, length 48
        Server, Leap indicator:  (0), Stratum 2 (secondary reference), poll 6 (64s), precision -23
        Root Delay: 0.002487, Root dispersion: 0.021072, Reference-ID: 193.67.79.202
          Reference Timestamp:  3610715653.842456400 (2014/06/02 18:34:13)
          Originator Timestamp: 3610715661.618533253 (2014/06/02 18:34:21)
          Receive Timestamp:    3610715661.625648736 (2014/06/02 18:34:21)
          Transmit Timestamp:   3610715661.625682592 (2014/06/02 18:34:21)
            Originator - Receive Timestamp:  +0.007115493
            Originator - Transmit Timestamp: +0.007149379
        0x0000:  1c6f 653c c971 0022 7524 39b4 0800 4500  .oe<.q."u$9...E.
        0x0010:  004c 6b41 4000 3411 fbc0 5362 c985 c0a8  .LkA@.4...Sb....
        0x0020:  020f 007b 007b 0038 86f1 2402 06e9 0000  ...{.{.8..$.....
        0x0030:  00a3 0000 0565 c143 4fca d737 2605 d7ab  .....e.CO..7&...
        0x0040:  3888 d737 260d 9e58 31b8 d737 260d a02a  8..7&..X1..7&..*
        0x0050:  83e4 d737 260d a02c bc69                 ...7&..,.i
18:34:22.679020 00:22:fa:1b:ca:28 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 165: (tos 0x0, ttl 1, id 22740, offset 0, flags [none], proto UDP (17), length 151)
    192.168.2.2.63053 > 239.255.255.250.1900: [udp sum ok] UDP, length 123
        0x0000:  0100 5e7f fffa 0022 fa1b ca28 0800 4500  ..^...."...(..E.
        0x0010:  0097 58d4 0000 0111 addd c0a8 0202 efff  ..X.............
        0x0020:  fffa f64d 076c 0083 9c96 4d2d 5345 4152  ...M.l....M-SEAR
        0x0030:  4348 202a 2048 5454 502f 312e 310d 0a48  CH.*.HTTP/1.1..H
        0x0040:  6f73 743a 3233 392e 3235 352e 3235 352e  ost:239.255.255.
        0x0050:  3235 303a 3139 3030 0d0a 5354 3a75 726e  250:1900..ST:urn
        0x0060:  3a73 6368 656d 6173 2d75 706e 702d 6f72  :schemas-upnp-or
        0x0070:  673a 6465 7669 6365 3a53 7769 6674 5365  g:device:SwiftSe
        0x0080:  7276 6572 3a31 0d0a 4d61 6e3a 2273 7364  rver:1..Man:"ssd
        0x0090:  703a 6469 7363 6f76 6572 220d 0a4d 583a  p:discover"..MX:
        0x00a0:  330d 0a0d 0a                             3....
18:34:25.680269 00:22:fa:1b:ca:28 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 165: (tos 0x0, ttl 1, id 22934, offset 0, flags [none], proto UDP (17), length 151)
    192.168.2.2.63053 > 239.255.255.250.1900: [udp sum ok] UDP, length 123
        0x0000:  0100 5e7f fffa 0022 fa1b ca28 0800 4500  ..^...."...(..E.
        0x0010:  0097 5996 0000 0111 ad1b c0a8 0202 efff  ..Y.............
        0x0020:  fffa f64d 076c 0083 9c96 4d2d 5345 4152  ...M.l....M-SEAR
        0x0030:  4348 202a 2048 5454 502f 312e 310d 0a48  CH.*.HTTP/1.1..H
        0x0040:  6f73 743a 3233 392e 3235 352e 3235 352e  ost:239.255.255.
        0x0050:  3235 303a 3139 3030 0d0a 5354 3a75 726e  250:1900..ST:urn
        0x0060:  3a73 6368 656d 6173 2d75 706e 702d 6f72  :schemas-upnp-or
        0x0070:  673a 6465 7669 6365 3a53 7769 6674 5365  g:device:SwiftSe
        0x0080:  7276 6572 3a31 0d0a 4d61 6e3a 2273 7364  rver:1..Man:"ssd
        0x0090:  703a 6469 7363 6f76 6572 220d 0a4d 583a  p:discover"..MX:
        0x00a0:  330d 0a0d 0a                             3....
18:34:25.839848 00:22:75:24:39:b4 > 01:80:c2:00:00:00, 802.3, length 60: LLC, dsap STP (0x42) Individual, ssap STP (0x42) Command, ctrl 0x03: STP 802.1d, Config, Flags [none], bridge-id 8000.00:22:75:24:39:b4.8001, length 43
        message-age 0.00s, max-age 20.00s, hello-time 30.00s, forwarding-delay 1.00s
        root-id 8000.00:22:75:24:39:b4, root-pathcost 0
        0x0000:  0180 c200 0000 0022 7524 39b4 0026 4242  ......."u$9..&BB
        0x0010:  0300 0000 0000 8000 0022 7524 39b4 0000  ........."u$9...
        0x0020:  0000 8000 0022 7524 39b4 8001 0000 1400  ....."u$9.......
        0x0030:  1e00 0100 a5a5 a5a5 a5a5 a5a5            ............

<As is maxed out on room, I deleted the rest. A 15.000 character maximum, never thought I'd run out of space this soon.>