[opensuse] Now I get martians on wlan0
Hi, After configuring eth0 to also have an IPv6 addresses, I get martians on wlan, which configured to get address via dhcp6 only, in order to detect when/if the ISP provides it. And of course, it never gets one. Isengard:~ # iwconfig lo no wireless extensions. wlan0 IEEE 802.11 ESSID:"......." Mode:Managed Frequency:2.437 GHz Access Point: 70:8B:CD:59:88:3C Bit Rate=150 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=62/70 Signal level=-48 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:17 Missed beacon:0 eth0 no wireless extensions. Isengard:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 4c:cc:6a:61:50:a1 brd ff:ff:ff:ff:ff:ff inet 192.168.1.16/24 brd 192.168.1.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fc00::16/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4ecc:6aff:fe61:50a1/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:d3:7a:82:b3:4c brd ff:ff:ff:ff:ff:ff inet6 fe80::a2d3:7aff:fe82:b34c/64 scope link valid_lft forever preferred_lft forever Isengard:~ # Isengard:~ # systemctl status network ● wicked.service - wicked managed network interfaces Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled) Active: active (exited) since Tue 2019-06-25 14:15:54 CEST; 1 months 13 days ago Process: 29081 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS) Main PID: 1232 (code=exited, status=0/SUCCESS) CPU: 56ms Jun 25 14:15:54 Isengard systemd[1]: Started wicked managed network interfaces. Aug 08 00:16:49 Isengard systemd[1]: Reloading wicked managed network interfaces. Aug 08 00:17:20 Isengard wicked[24538]: eth0 device-ready Aug 08 00:17:20 Isengard wicked[24538]: eth0 up Aug 08 00:17:20 Isengard wicked[24538]: wlan0 setup-in-progress Aug 08 00:17:20 Isengard systemd[1]: Reloaded wicked managed network interfaces. Aug 08 02:37:32 Isengard systemd[1]: Reloading wicked managed network interfaces. Aug 08 02:38:03 Isengard wicked[29081]: wlan0 device-ready Aug 08 02:38:03 Isengard wicked[29081]: wlan0 setup-in-progress Aug 08 02:38:03 Isengard systemd[1]: Reloaded wicked managed network interfaces. Isengard:~ # Why the martians? How do I stop them? <3.6> 2019-08-08T02:38:03.342398+02:00 Isengard wicked 29081 - - wlan0 device-ready <3.6> 2019-08-08T02:38:03.343768+02:00 Isengard wicked 29081 - - wlan0 setup-in-progress <3.6> 2019-08-08T02:38:03.344335+02:00 Isengard systemd 1 - - Reloaded wicked managed network interfaces. <0.4> 2019-08-08T02:42:34.133900+02:00 Isengard kernel - - - [3760166.225960] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:34.133934+02:00 Isengard kernel - - - [3760166.225966] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:35.977964+02:00 Isengard kernel - - - [3760168.069377] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:35.977996+02:00 Isengard kernel - - - [3760168.069383] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:35.978000+02:00 Isengard kernel - - - [3760168.070591] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:35.978003+02:00 Isengard kernel - - - [3760168.070594] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:38.129903+02:00 Isengard kernel - - - [3760170.219883] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:38.129933+02:00 Isengard kernel - - - [3760170.219889] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-08T02:42:38.129938+02:00 Isengard kernel - - - [3760170.222373] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-08T02:42:38.129941+02:00 Isengard kernel - - - [3760170.222379] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... 192.168.1.16 is the same machine. 192.168.1.3 is the printer. (machine runs Leap 15.0) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 08/08/2019 07.25, David C. Rankin wrote:
On 08/07/2019 07:47 PM, Carlos E. R. wrote:
Why the martians? How do I stop them?
They come in peace -- nothing to worry about :)
No, they don't, they spam the log! Grrr! -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 08/08/2019 07.25, David C. Rankin wrote:
On 08/07/2019 07:47 PM, Carlos E. R. wrote:
Why the martians? How do I stop them?
They come in peace -- nothing to worry about :)
No, they don't, they spam the log! Grrr!
Use 'sysctl -a| grep martians' and set to zero.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/08/2019 12.44, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 08/08/2019 07.25, David C. Rankin wrote:
On 08/07/2019 07:47 PM, Carlos E. R. wrote:
Why the martians? How do I stop them?
They come in peace -- nothing to worry about :)
No, they don't, they spam the log! Grrr!
Use 'sysctl -a| grep martians' and set to zero....
Interesting program! Isengard:~ # sysctl net.ipv4.conf.wlan0.log_martians=0 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ # sysctl -a| grep martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ # Still remains the question of why am I getting IPv4 martians on an interface without IPv4 address... Huh. Does not work, they keep coming. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 08/08/2019 13.03, Carlos E. R. wrote:
On 08/08/2019 12.44, Peter Suetterlin wrote:
Carlos E. R. wrote:
On 08/08/2019 07.25, David C. Rankin wrote:
On 08/07/2019 07:47 PM, Carlos E. R. wrote:
Why the martians? How do I stop them?
They come in peace -- nothing to worry about :)
No, they don't, they spam the log! Grrr!
Use 'sysctl -a| grep martians' and set to zero....
Interesting program!
Isengard:~ # sysctl net.ipv4.conf.wlan0.log_martians=0 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ # sysctl -a| grep martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ #
Still remains the question of why am I getting IPv4 martians on an interface without IPv4 address...
Huh. Does not work, they keep coming.
Only thing that works, not knowing what else to do: Isengard:~ # ifdown wlan0 wlan0 device-ready Isengard:~ # -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Thu, Aug 8, 2019 at 2:03 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Isengard:~ # sysctl net.ipv4.conf.wlan0.log_martians=0 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ # sysctl -a| grep martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ #
Still remains the question of why am I getting IPv4 martians on an interface without IPv4 address...
Exactly because interface does not have IPv4 address so any IP packet on this interface is impossible.
Huh. Does not work, they keep coming.
--><-- log_martians for the interface will be enabled if at least one of conf/{all,interface}/log_martians is set to TRUE, --><-- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/08/2019 14.54, Andrei Borzenkov wrote:
On Thu, Aug 8, 2019 at 2:03 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Isengard:~ # sysctl net.ipv4.conf.wlan0.log_martians=0 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ # sysctl -a| grep martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ #
Still remains the question of why am I getting IPv4 martians on an interface without IPv4 address...
Exactly because interface does not have IPv4 address so any IP packet on this interface is impossible.
Oh, I see. So it would work if it also had an IPv4 address.
Huh. Does not work, they keep coming.
--><-- log_martians for the interface will be enabled if at least one of conf/{all,interface}/log_martians is set to TRUE, --><--
Mmmm... Now I understand, thanks. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 08/08/2019 16.16, Carlos E. R. wrote:
On 08/08/2019 14.54, Andrei Borzenkov wrote:
On Thu, Aug 8, 2019 at 2:03 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Isengard:~ # sysctl net.ipv4.conf.wlan0.log_martians=0 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ # sysctl -a| grep martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 net.ipv4.conf.wlan0.log_martians = 0 Isengard:~ #
Still remains the question of why am I getting IPv4 martians on an interface without IPv4 address...
Exactly because interface does not have IPv4 address so any IP packet on this interface is impossible.
Oh, I see. So it would work if it also had an IPv4 address.
Well, it doesn't work. Isengard:~ # ip addr ... 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether a0:d3:7a:82:b3:4c brd ff:ff:ff:ff:ff:ff inet 192.168.1.134/24 brd 192.168.1.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::a2d3:7aff:fe82:b34c/64 scope link valid_lft forever preferred_lft forever Log: <0.4> 2019-08-15T19:38:48.796906+02:00 Isengard kernel - - - [ 4215.537770] IPv4: martian source 192.168.1.255 from 192.168.1.134, on dev wlan0 <0.4> 2019-08-15T19:38:48.796946+02:00 Isengard kernel - - - [ 4215.537776] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-15T19:40:30.785007+02:00 Isengard kernel - - - [ 4317.528637] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-15T19:40:30.785037+02:00 Isengard kernel - - - [ 4317.528643] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... <0.4> 2019-08-15T19:40:32.936966+02:00 Isengard kernel - - - [ 4319.678998] IPv4: martian source 192.168.1.255 from 192.168.1.16, on dev wlan0 <0.4> 2019-08-15T19:40:32.937002+02:00 Isengard kernel - - - [ 4319.679008] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 ......L.jaP... What works is: nmcli radio wifi off -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2019-08-15 at 19:49 +0200, Carlos E. R. wrote:
What works is:
nmcli radio wifi off
Nay, it doesn't. Isengard:~ # nmcli radio wifi off Error: NetworkManager is not running. Isengard:~ # ifdown wlan0 wlan0 device-ready Isengard:~ # That one does. No more wlan interface till next boot. - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXVWbvBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV2MQAoIo/u7fedLDMWDh/Lo8D J6gc1jDsAJ9n+Di86bW7kEG6wr0ThBOTAWcdDw== =VB6e -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R. <robin.listas@telefonica.net> [08-15-19 13:57]:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday, 2019-08-15 at 19:49 +0200, Carlos E. R. wrote:
What works is:
nmcli radio wifi off
Nay, it doesn't.
Isengard:~ # nmcli radio wifi off Error: NetworkManager is not running. Isengard:~ # ifdown wlan0 wlan0 device-ready Isengard:~ #
That one does. No more wlan interface till next boot.
why would you expect a NetworkManager command to work when you are running wicked? if you switch to NetworkManager, ifdown will no longer work. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 15/08/2019 20.06, Patrick Shanahan wrote:
* Carlos E. R. <> [08-15-19 13:57]:
On Thursday, 2019-08-15 at 19:49 +0200, Carlos E. R. wrote:
What works is:
nmcli radio wifi off
Nay, it doesn't.
Isengard:~ # nmcli radio wifi off Error: NetworkManager is not running. Isengard:~ # ifdown wlan0 wlan0 device-ready Isengard:~ #
That one does. No more wlan interface till next boot.
why would you expect a NetworkManager command to work when you are running wicked?
Because I did not remember that nmcli was a network manager command. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 2019-08-08 01:25 AM, David C. Rankin wrote:
On 08/07/2019 07:47 PM, Carlos E. R. wrote:
Why the martians? How do I stop them? They come in peace -- nothing to worry about :)
Yep, they're only here to serve man. ;-) https://en.wikipedia.org/wiki/To_Serve_Man_(The_Twilight_Zone) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin -
James Knott -
Patrick Shanahan -
Peter Suetterlin