On 08/21/2016 08:23 PM, Andrei Borzenkov wrote:
22.08.2016 05:17, fastcpu пишет:
When connected to a VPN via OpenVPN, I am getting these messages when viewing journalctl, and they occur every few minutes:
Aug 21 19:01:24 linux-6uhj kernel: IPv4: martian source 192.168.1.5 from 1.1.1.1, on dev enp7s0 Aug 21 19:01:24 linux-6uhj kernel: ll header: 00000000: ff ff ff ff ff ff b8 a3 86 57 78 f5 08 06 .........Wx...
Please show "ifconfig -a" output with VPN connected.
I have tried researching on Google what IPv4: martian source means and have not came up with much information, besides not to turn off Marian Source logging because if you ever do get attacked you want it on. How would I go about figuring out what these errors mean and how to stop them?
They don't seem to happen when not connected to the VPN. Thanks
# 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:191554552 (182.6 Mb) What I ended up doing was going into YaST2 Networking and turning off IPv6 and then rebooting, and that seems to have stopped the IPv4: martian source errors. I guess it shouldn't be enabled when I'm not using IPv6 at all, but I thought it wouldn't matter since it never caused any harm being left on. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org