On 11/09/2015 04:30 AM, Andrei Borzenkov wrote:

09.11.2015 01:45, Carlos E. R пишет:

...

What can I do about it?

This is a fresh install of leap 42.1, for testing. Networking is via wifi and network manager. I don't see those entries on other computers, as far as I recall.

Minas-Anor:~ # ping6 -i wlan0 "fe80::eee:e6ff:fed7:bb5f" ping: bad timing interval Minas-Anor:~ # whois "fe80::eee:e6ff:fed7:bb5f" Unknown AS number or IP network. Please upgrade this program. Minas-Anor:~ #

This is link-local address; if you cannot ping it, probably you have IPv6 disabled? I observe these messages when interface comes up and goes down. In your case it looks like it attempts to configure IPv6 permanently.

Is iPv6 enabled globally and in interface properties?

ifconfig wlan0 Link encap:Ethernet HWaddr 0C:EE:E6:D7:BB:5F inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::eee:e6ff:fed7:bb5f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3852 errors:0 dropped:0 overruns:0 frame:0 TX packets:6926 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1302603 (1.2 Mb) TX bytes:1240524 (1.1 Mb) Minas-Anor:~ # ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default 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: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 00:26:9e:95:62:d9 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0c:ee:e6:d7:bb:5f brd ff:ff:ff:ff:ff:ff inet 192.168.1.50/24 brd 192.168.1.255 scope global dynamic wlan0 valid_lft 41333sec preferred_lft 41333sec inet6 fc00::8002/128 scope global dynamic valid_lft 86404sec preferred_lft 86404sec inet6 fe80::eee:e6ff:fed7:bb5f/64 scope link valid_lft forever preferred_lft forever Minas-Anor:~ # Minas-Anor:~ # ip route default via 192.168.1.1 dev wlan0 proto static metric 600 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.50 metric 600 Minas-Anor:~ # Huh. fe80::eee:e6ff:fed7:bb5f/64 seems to be myself. -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 11/09/2015 05:39 PM, Per Jessen wrote:

Yup, fe80 is link-local, can't be routed. Every device has one when IPv6 is enabled.

Then why am I getting thousands of log lines about it in the log? (repeats on less than 10 seconds) Nov 8 23:24:30 Minas-Anor dbus-daemon[737]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Nov 8 23:24:30 Minas-Anor dbus-daemon[737]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::eee:e6ff:fed7:bb5f. Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Joining mDNS multicast group on interface wlan0.IPv6 with address fc00::8002. Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Registering new address record for fc00::8002 on wlan0.*. Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Withdrawing address record for fe80::eee:e6ff:fed7:bb5f on wlan0. Nov 8 23:24:32 Minas-Anor avahi-daemon[738]: Withdrawing address record for fc00::8002 on wlan0. Nov 8 23:24:32 Minas-Anor avahi-daemon[738]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fc00::8002. Nov 8 23:24:32 Minas-Anor avahi-daemon[738]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::eee:e6ff:fed7:bb5f. Nov 8 23:24:32 Minas-Anor avahi-daemon[738]: Registering new address record for fe80::eee:e6ff:fed7:bb5f on wlan0.*. When I kill the avahi daemon, I get this, about once per minute: Nov 9 02:09:16 Minas-Anor dbus-daemon[737]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Nov 9 02:09:16 Minas-Anor dbus-daemon[737]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' That's a lot of noise. :-( -- Cheers/Saludos Carlos E. R. (openSUSE Leap 42.1, test at Minas-Anor) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2015-11-10 08:57, Per Jessen wrote:

Systemd is also being a bit noisy, every 15 minutes I get this:

Yes, that part appears also on 13.1. Too noisy for my liking. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

Op dinsdag 10 november 2015 09:06:01 schreef Per Jessen:

Carlos E. R wrote:

...

Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::eee:e6ff:fed7:bb5f. Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Joining mDNS multicast group on interface wlan0.IPv6 with address fc00::8002. Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Registering new address record for fc00::8002 on wlan0.*. Nov 8 23:24:31 Minas-Anor avahi-daemon[738]: Withdrawing address record for fe80::eee:e6ff:fed7:bb5f on wlan0.

This would appear to show that your interface wlan0 is switching between two addresses, the fe80 and the fc00 prefix.

I would like to know where the fc00 address is coming from.

fe80 addresses are only usable in the broadcast domain of the network (link local address). fc00::/7 is a prefix used in a network of local importance, like a company network (for an international company this can be worldwide). It is a bit comparable with the 10 network for IPv4. Its purpose is to have simple filters on the edge of the network. Routers in the local network provide the prefix used for this type of address on the link. So apparently your system is connected to a router which is part of such a company network. In that case your system should have at least 3 IPv6 addresses, a fe80, a fc00 and a global address if your router is also connected to a world global IPv6 network. You may even have more than one world global network addresses, the last 64 bits derived from your MAC address, randomly generated and a fixed one received from a DHCP6 server or defined on your system.

I'm not familiar with the avahi-daemon at all, but I think it's only doing what it's supposed to do.

It is mainly used in Microsoft networks to spread information on available services. Not much used in Linux networks. So you may experiment with disabling it. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2015-11-10 12:02, Per Jessen wrote:

Freek de Kruijf wrote:

...

Op dinsdag 10 november 2015 09:06:01 schreef Per Jessen:

...

...

This would appear to show that your interface wlan0 is switching between two addresses, the fe80 and the fc00 prefix.

I thought so, but was unsure. I know very little about IPv6.

...

...

I would like to know where the fc00 address is coming from.

fe80 addresses are only usable in the broadcast domain of the network (link local address). fc00::/7 is a prefix used in a network of local importance, like a company network (for an international company this can be worldwide). It is a bit comparable with the 10 network for IPv4. Its purpose is to have simple filters on the edge of the network. Routers in the local network provide the prefix used for this type of address on the link. So apparently your system is connected to a router which is part of such a company network. In that case your system should have at least 3 IPv6 addresses, a fe80, a fc00 and a global address if your router is also connected to a world global IPv6 network. You may even have more than one world global network addresses, the last 64 bits derived from your MAC address, randomly generated and a fixed one received from a DHCP6 server or defined on your system.

Oh :-o

That makes two questions then -

a) why does Carlos have an FC00 address on his network? b) why does it change/toggle all the time?

Carlos, sounds like it might be coming from your router.

It is a home router provided by my ISP, with fibre entry. It also routes TV service, with some sort of invisible tunnel or whatever. I believe it also routes VoIp (SIP), which the entry gadget (prior to the router) converts to POTS. Stupid, they should provide real SIP, way much more powerful. But I have a suspicion... I have two routers in service. The ISP router gives lousy WiFi signal, so I disabled it and connected another router handling the WiFi part. It is possible that this other router tries to hand over IPv6 addresses, too. I will look now. The ISP router (Movistar-broadcom?) has a section in the config (untouched) named "IPv6 autoconfig". I don't know what addresses it hands out, if any. LAN IPv6 Link-Local Address Configuration EUI-64 The "secondary" router (TP-Link Model No. TD-W8970), used as WiFi AP only, has this config (I mark active options with «»): +++........................... The parameters of IPv6 LAN can be configured on this page. Note: Only default group supports IPv6 now. Group: Default Address Autoconfiguration Type: RADVD «DHCPv6 Server» Start IPv6 Address: fC00:0:0:0::«7FFF» (1~FFFE) End IPv6 Address: fC00:0:0:0::«FFFE» (1~FFFE) Leased Time: «86400» seconds (The default value is 86400) Site Prefix Configuration Type: Delegated «Static» Site Prefix: «fC00:0:0:0::» Site Prefix Length: «64» ...........................++- So the fc00 address is coming from the secondary router. I don't know how to disable this router trying to hand over IPv6 addresses. It should be done by the ISP router only. The DHCP (IPv4) is disabled, of course. I have just switched in the above shown config to «RADVD», and the avahi noise has stopped :-)) The noise about "org.freedesktop.nm_dispatcher" continues, though, but it is slower. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On Tue, Nov 10, 2015 at 3:37 PM, Per Jessen wrote:

Carlos E. R. wrote:

...

It is a home router provided by my ISP, with fibre entry. It also routes TV service, with some sort of invisible tunnel or whatever. I believe it also routes VoIp (SIP), which the entry gadget (prior to the router) converts to POTS. Stupid, they should provide real SIP, way much more powerful.

Yes, but people would have to buy themselves a new SIP-capable telephone or an adapter.

...

I have just switched in the above shown config to «RADVD», and the avahi noise has stopped :-))

Does your interface still get the fc00 address?

MN can be configured to ignore RA; Carlos, what are settings for IPv6 in NM? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

10.11.2015 16:16, Carlos E. R. пишет:

On 11/10/2015 01:41 PM, Andrei Borzenkov wrote:

I don't remember if I said that I do not get this "log noise" on 13.1. Ah, wait, there I use a static address.

...

...

...

I have just switched in the above shown config to «RADVD», and the avahi noise has stopped :-))

Does your interface still get the fc00 address?

MN can be configured to ignore RA; Carlos, what are settings for IPv6 in NM?

Whatever is the default. Let me see...

Method: automatic Addresses, dns, search domains : blank IPv6 privacy extensions: disabled. Require IPv6... disabled. Routes: blank.

I don't want to disable IPv6, but to ignore the configurations handed over by the second "router" - if that is possible at all.

You can set method to link-local if you do not need global connectivity. If you do need global connectivity, you must use either DHCP or RA to obtain valid prefix (automatic tries both as far as I know). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2015-11-10 13:37, Per Jessen wrote:

Carlos E. R. wrote:

...

It is a home router provided by my ISP, with fibre entry. It also routes TV service, with some sort of invisible tunnel or whatever. I believe it also routes VoIp (SIP), which the entry gadget (prior to the router) converts to POTS. Stupid, they should provide real SIP, way much more powerful.

Yes, but people would have to buy themselves a new SIP-capable telephone or an adapter.

Right. I should have said "as an option".

...

I have just switched in the above shown config to «RADVD», and the avahi noise has stopped :-))

Does your interface still get the fc00 address?

Wait... [ssh] cer@Minas-Anor:~> ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default 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: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 00:26:9e:95:62:d9 brd ff:ff:ff:ff:ff:ff 3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0c:ee:e6:d7:bb:5f brd ff:ff:ff:ff:ff:ff inet 192.168.1.50/24 brd 192.168.1.255 scope global dynamic wlan0 valid_lft 37389sec preferred_lft 37389sec inet6 fc00::eee:e6ff:fed7:bb5f/128 scope global dynamic valid_lft 298sec preferred_lft 118sec inet6 fe80::eee:e6ff:fed7:bb5f/64 scope link valid_lft forever preferred_lft forever cer@Minas-Anor:~> Previously I had: 3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 0c:ee:e6:d7:bb:5f brd ff:ff:ff:ff:ff:ff inet 192.168.1.50/24 brd 192.168.1.255 scope global dynamic wlan0 valid_lft 41333sec preferred_lft 41333sec inet6 fc00::8002/128 scope global dynamic valid_lft 86404sec preferred_lft 86404sec inet6 fe80::eee:e6ff:fed7:bb5f/64 scope link valid_lft forever preferred_lft forever but: cer@Minas-Anor:~> ping6 -i wlan "fe80::eee:e6ff:fed7:bb5f" ping: bad timing interval cer@Minas-Anor:~> ping6 -i wlan0 "fc00::eee:e6ff:fed7:bb5f" ping: bad timing interval cer@Minas-Anor:~> cer@Telcontar:~> ping6 -i eth0 "fe80::eee:e6ff:fed7:bb5f" ping: bad timing interval. cer@Telcontar:~> ping6 -i eth0 "fc00::eee:e6ff:fed7:bb5f" ping: bad timing interval. cer@Telcontar:~> I'm unsure if I'm doing it right :-? -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On 2015-11-10 14:17, Andrei Borzenkov wrote:

On Tue, Nov 10, 2015 at 4:09 PM, Carlos E. R. wrote:

...

cer@Telcontar:~> ping6 -i eth0 "fc00::eee:e6ff:fed7:bb5f" ping: bad timing interval. cer@Telcontar:~>

I'm unsure if I'm doing it right :-?

Capital I.

man ping6

I did have a look at it yesterday. O:-) Ah, ok, no need for the "-i". Without it, it works. Funny... cer@Telcontar:~> ping6 "fc00::eee:e6ff:fed7:bb5f" PING fc00::eee:e6ff:fed7:bb5f(fc00::eee:e6ff:fed7:bb5f) 56 data bytes 64 bytes from fc00::eee:e6ff:fed7:bb5f: icmp_seq=1 ttl=64 time=58.4 ms 64 bytes from fc00::eee:e6ff:fed7:bb5f: icmp_seq=2 ttl=64 time=1.71 ms 64 bytes from fc00::eee:e6ff:fed7:bb5f: icmp_seq=3 ttl=64 time=1.60 ms 64 bytes from fc00::eee:e6ff:fed7:bb5f: icmp_seq=4 ttl=64 time=8.12 ms ^C --- fc00::eee:e6ff:fed7:bb5f ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 1.602/17.475/58.459/23.808 ms cer@Telcontar:~> ping6 "fe80::eee:e6ff:fed7:bb5f" connect: Invalid argument cer@Telcontar:~> Why the second one fails, I can not imagine. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On Tue, Nov 10, 2015 at 1:29 PM, Freek de Kruijf wrote:

fc00::/7 is a prefix used in a network of local importance, like a company network (for an international company this can be worldwide). It is a bit comparable with the 10 network for IPv4. Its purpose is to have simple filters on the edge of the network. Routers in the local network provide the prefix used for this type of address on the link.

fc00::0/7 already *is* *the* prefix, so routers need not provide it. Do not confuse it with prefix in RA (router advertisement). fc00::0/7 is so called Unique Local Unicast Address. See https://tools.ietf.org/html/rfc4193 for details. Initially fc00/7 was reserved for addresses provided by global registration authority; currently these addresses are reserved and undefined. So the question still remains - where this address comes from and who tries to configure it and why this configuration attempt is apparently unsuccessful and is retried permanently. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Nov 10, 2015 at 3:20 PM, Carlos E. R. wrote:

On 2015-11-10 13:14, Andrei Borzenkov wrote:

...

So the question still remains - where this address comes from and who tries to configure it and why this configuration attempt is apparently unsuccessful and is retried permanently.

See my other post, it explains it.

Only partially - it still does not explain why it is retried permanently. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op dinsdag 10 november 2015 15:14:39 schreef Andrei Borzenkov:

On Tue, Nov 10, 2015 at 1:29 PM, Freek de Kruijf wrote:

...

fc00::/7 is a prefix used in a network of local importance, like a company network (for an international company this can be worldwide). It is a bit comparable with the 10 network for IPv4. Its purpose is to have simple filters on the edge of the network. Routers in the local network provide the prefix used for this type of address on the link.

fc00::0/7 already *is* *the* prefix, so routers need not provide it. Do not confuse it with prefix in RA (router advertisement).

No, the router needs to provide the 64 bits prefix which begins with fc or fd (fc00::/7) on the link, which should be unique in the company network, provided this is a link without further routers.

fc00::0/7 is so called Unique Local Unicast Address. See https://tools.ietf.org/html/rfc4193 for details. Initially fc00/7 was reserved for addresses provided by global registration authority; currently these addresses are reserved and undefined.

So the question still remains - where this address comes from and who tries to configure it and why this configuration attempt is apparently unsuccessful and is retried permanently.

This has been answered already, the Wi-Fi router provides them, so this should be disabled. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2015-11-10 13:27, Freek de Kruijf wrote:

This has been answered already, the Wi-Fi router provides them, so this should be disabled.

But there is no option in the router to disable them. What I did is select RADVD instead of DHCPv6 Server, seems to work - but I don't know what other consequences it might have. The current configuration is: Default Address Autoconfiguration Type: «RADVD» DHCPv6 Server Site Prefix Configuration Type: Delegated «Static» Site Prefix: fC00:0:0:0:: Site Prefix Length: 64 What I would do now is to select "delegated". Then I get: Site Prefix Configuration Type: «Delegated» Static Prefix Delegated WAN Connection: No available interface. But on click "save" I get "No available WAN connection, please set one". But that is impossible, there is no WAN in the second router, intentionally not connected. Ie, I use the router as switch. This router is stupidly clever, it does not allow options that it /thinks/ will not work. All because I want to keep my beloved money and not buy a standalone AP. Sigh... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)