-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.20.1603211939040.14097@Grypbagne.inyvabe> On Monday, 2016-03-21 at 06:32 +0300, Andrei Borzenkov wrote:
produce the same result (empty page). In fact, when I enter
Well, that's not exactly convincing. Show packet trace from client where you tried it. ...
And you were right. See the other post when we found it was the wireless router by unplugging everything from the switch and pinging, then connecting things back...
Let's try. [...] It refuses. It wants me to specify a WAN connection, and there is none. I could set the "Site Prefix Configuration Type" to static, but then I have to enter a site prefix and I have no idea what to type there. And it has to be something that does not interfer with the ISP Router to the outside.
Do you actually need IPv6? If not, nothing you enter here can interfere with anything. In any case, you had site prefix already, as shown in one of your previous mail; why not use it (it had been set there all the time)?
Ah! I do not actually need it, but that router config page does not allow removing it. Wait, site prefix was always blank. I have entered "0:0:0:0::". Messages do not stop. <3.4> 2016-03-21T19:43:46+01:00 router radvd 675 - - our AdvManagedFlag on br0 doesn't agree with fe80::8cae:84ff:fe43:27d4 <1.4> 2016-03-21T19:43:53.768558+01:00 oldrouter - - - IGMP: V2 igmp router occured! Not matching ours V3. <3.4> 2016-03-21T19:43:55+01:00 router radvd 675 - - our AdvManagedFlag on br0 doesn't agree with fe80::8cae:84ff:fe43:27d4
+++····························· IPv6 LAN Settings
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
Packet trace showing RA in both cases would be definitely helpful to understand what it actually does.
Dificult...
Start IPv6 Address: ::7FFF(1~FFFE) End IPv6 Address: ::7FFE(1~FFFE) Leased Time: 86400 seconds (The default value is 86400)
Site Prefix Configuration Type: ( ) Delegated (*) Static Site Prefix: [ ] <================================== Site Prefix Length: 64 ·····························++-
I need a "Site Prefix" to make this work. Without it, it does not accept "Save" the config.
Use the same site prefix as was configured before.
There was never anything there. I tried, if I leave it to automatics it is not filled.
The configuration on the ISP router is below (and the above should not conflict with the below config):
+++····························· IPv6 LAN Auto Configuration Note: Stateful DHCPv6 is supported based on the assumption of prefix length less than or equal to 64. Interface ID does NOT support ZERO COMPRESSION "::". Please enter the complete information. For exampe: Please enter "0:0:0:2" instead of "::2". LAN IPv6 Link-Local Address Configuration (*) EUI-64 ( ) User Setting Interface Identifier: 0:0:0:1
Static LAN IPv6 Address Configuration Interface Address (prefix length is required): [_____]
IPv6 LAN Applications [X] Enable DHCPv6 Server (*) Stateless Refresh Time (sec): 1440 ( ) Stateful Start interface ID: 0:0:0:21 End interface ID: 0:0:0:FE Leased Time (second):
[X] Enable RADVD RA interval Min(sec): 3 RA interval Max(sec): 10 Reachable Time(ms): 0 Default Preference: Low [ ] MTU (bytes): [ ] Enable Prefix Length Relay
[ ] Enable ULA Prefix Advertisement ( ) Randomly Generate ( ) Statically Configure Prefix: [_____] Preferred Life Time (hour): -1 Valid Life Time (hour): -1
[ ] Enable MLD Snooping
·····························++-
If the only problem is to avoid these log messages from router, you may simply reconfigure it to use DHCP + RADVD.
It is either DHCP exclusive or RADVD, in the wifi AP. The ISP router as shown above I must not touch. The ISP router is in fact using both DHCP and RADV. What I could do is flash this "oldrouter" aka wifi AP with open software - - I forgot the exact name -, which probably allows me to do this without complaints. I have done it on another brand/model. But I wanted to avoid this hassle, the experience was not uneventfull (it needed lots of resources, the control web page would not run). - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlbwQfAACgkQtTMYHG2NR9W8iwCdGvaGiznlj7xZ+troAgKEZgSd 7iEAnjTYX6D6GB1WNytDlcwGCG6GhLQB =fJWD -----END PGP SIGNATURE-----