On 08/22/2016 02:16 AM, Andrei Borzenkov wrote:
On Mon, Aug 22, 2016 at 7:32 AM, sdm <fastcpu@openmailbox.org> wrote:
On 08/21/2016 09:01 PM, sdm wrote:
# ifconfig -a
enp7s0 Link encap:Ethernet HWaddr 8C:89:A5:6F:52:B3 inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::8e89:a5ff:fe6f:52b3/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14158669 errors:0 dropped:0 overruns:0 frame:0 TX packets:9738576 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16524867515 (15759.3 Mb) TX bytes:2457738636 (2343.8 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:1479602 errors:0 dropped:0 overruns:0 frame:0 TX packets:1479602 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:1079782831 (1029.7 Mb) TX bytes:1079782831 (1029.7 Mb)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.8.8.50 P-t-P:10.8.8.49 Mask:255.255.255.255 inet6 addr: fe80::5363:69c5:d73a:2b47/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:3588841 errors:0 dropped:0 overruns:0 frame:0 TX packets:2188042 errors:0 dropped:81 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:4406775220 (4202.6 Mb) TX bytes:1915
I may have spoken too soon as I'm not sure if turning IPv6 off in YaST2 Networking solved the problem or not. I think I still saw some IPv4: martian source errors when watching journalctl, but it may have slowed down. I will be keeping an eye on it, but any other suggestions appreciated.
This packet comes from device with MAC b8:a3:86:57:78:f5; OUI appears to belong to D-Link. are you aware of any device with this MAC and type in your network?
You cannot really do anything about this messages from openSUSE site - it is just messenger. Some device sends ARP request over LAN segment your interface is connected to and this device's IP does not belong to your interface's subnet. It may or may not indicate a problem. You need to find out what is this device first and check its configuration (if possible - i.e. if this device is under your control).
The D-Link is my client bridge router running DD-WRT. I only get these errors when the VPN connection is active, so the client bridge router could be the culprit. The only way I can think of right now to find out, is to try connecting a TW box to the main router, not to the CBR, run OpenVPN and connect, and see if the martian source errors appear. Then run the same box connected to the CBR and see if they appear in the journal. I have also tried WDS, and get the same errors. Client Bridge mode is sort of a "hack" in how it's implemented from what I know, so for whatever reason the problem only crops up when the VPN is connected. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org