Skip to main content
Raudi
New Member
April 12, 2019
Question

IPv6 WAN router advertisements?

  • April 12, 2019
  • 5 replies
  • 22522 views

Hi,

 

a few days ago i updated from 6.0.4 to 6.2 and now i got every 10 sec's this messages in the system log:

 

our AdvOtherConfigFlag on wan1 doesn't agree with fe80::1 our AdvManagedFlag on wan1 doesn't agree with fe80::1 our AdvOtherConfigFlag on wan2 doesn't agree with fe80::1 our AdvManagedFlag on wan2 doesn't agree with fe80::1

 

What is this message telling me?

 

Is the FG sending router advertisements to the wan interface and is reporting that it also get informations from fe80::1?

 

fe80::1 is the gateway IP on both WAN interfaces. (The provider)

 

The WAN interfaces are configured with DHCP.

 

Regards

Stefan

    5 replies

    Raudi
    RaudiAuthor
    New Member
    April 12, 2019

    I made a capture on the WAN interface, every time at the same time i got the error message the FG, i received this frame:

    What goes wrong?

     

    Raudi
    RaudiAuthor
    New Member
    April 12, 2019

    o.k Regarding the frame, there are two ICMPv6 flags set with "1":

     

    - Managed address configuration - Other configuration

     

    This two are logged in the FG system log.

     

    So i searched at google for this:

     

    The “Managed” address config flag specifies whether “Stateful configuration” is to be used. Stateful configuration would typically be understood to mean DHCPv6. The “Other” stateful config flag means that nodes on this link (local network) should use Stateful configuration (DHCPv6) for things other than address assignment.

     

    The WAN interfaces are in DHCP mode, so i don't see what's wrong.

     

    In 6.0.4 i don't got this message, so i think there is a possibility that this a bug in 6.2.

     

    I also made a support ticket...

    Raudi
    RaudiAuthor
    New Member
    April 17, 2019

    O.k. got a feedback from support, it's known bug...

    GeekBrownBear
    New Member
    December 20, 2021

    On 7.0.3 and seeing it as well.

    CDC-IT
    Explorer
    February 20, 2022

    7.0.5 Confirmed too

    OGPlugBone
    New Member
    March 16, 2022

    Have it here on 7.0.2. Thought disabling IPv6 via Comcast would free up the issue. Nope. 

    vboul
    New Member
    September 4, 2022

    try this command if you dont need ipv6. it will stop logging

    diag ipv6 devconf disable_ipv6 1