IPv6 on PPPoE - experiences requested

Comments

7 comments

  • Avatar
    Firewalla

    It is absolutely not possible for FWG to send logs to your ISP ... Did you configure any Syslog to them? or they did do something to your FWG? or is it their own system that's acting up? <= I assume it is this they are talking about

    If it is their own system printing out the messages to their own servers, then we need to know exactly why the logs are there. That is the reason that our staff is asking for details, only them or their vendors knows why the message is getting printed out.

     

    0
    Comment actions Permalink
  • Avatar
    Radagast82

    I'm not saying that FWG sends log of course, but it generates some kind of error which are printed in their system. Error is about DHCP, and occurs every 30 seconds (i sent the exact message to your support, i can't write it here because it contains my ipv6). So imagine an error printed in a log system every 30 sec... I just asked ISP to understand if those errors were present since the beginning or started later from a specific date

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Usually, if their system is spiting out errors, they have to interpret it and tell us (or you) what the problem was (or if it is a problem at all, or just programmers printing out stuff ... because ... our developers does that too ... :) )

     

    0
    Comment actions Permalink
  • Avatar
    Radagast82

    guys, I don't want to accuse anyone. All the information I have are available to your support team, which is amazing since they helped me with the previous issue with IPv6. Everything that is known by my ISP is (and will be) shared. If my ISP says that there is something on my config which is causing this, then I ask you what can it be, given the fact that the current implementation of IPv6 with PPPoE is not so smooth and the error seems to be not "common", at least there is no trace on similar issues on the web...

    I just want to be sure that someone is looking into this. even if it's not a problem itself (my connection works good on both the stacks) it's causing problems to isp log system

    many thanks

     

    0
    Comment actions Permalink
  • Avatar
    Radagast82

    Some update. While fw support is looking into dhcpv6, I managed to get ipv6 partially working. Given the fact that my isp provides a static /56, I set static instead of dhcp in the wan setup, using as ip address the provided class ending in ::2, prefix 56. Gateway has been manually set with a link-local address, as per PPPoE standard. With this setup, ISP does not log any error: also looking at /var/log/dhcpcd.log there is no error event recorded (while using dhcpv6 instead of static generates errors every 30 sec, visible on said log...).

    So, first evidence is that dhcpv6 on wan is somehow not working so good.

    Here comes the tricky part: if I enable ipv6 on my main LAN (eth port #2), i have to set the exact class ending in ::2, prefix 56 and dhcp enabled (on LAN). Doing this, devices in that Lan correctly receive a valid ipv6 address (also a link-local address as it should), all ipv6 test are passed (test-ipv6.com and similar). Doing the same on a VLAN (i got 3 vlan, all in eth port#2), keeping the lan config as above, results in:

    1) VLAN devices are not receiving a valid ipv6 address, using ::1, ::3, ::4 etc. No test are passed (easy to check for me, xbox connects only in ipv4)

    2) The entire connection drops, even the ipv4 (and i have a dual stack...) for every device in the entire network, setting ::2 (same as LAN and WAN)

    So, until now, seems like I'm able to have ipv6 working, without errors or other, only on 1 LAN/VLAN at my choice. 

    All the above has been already shared with FW support, I'm writing here to mainly ask for some help/advice from anyone in this forum, as long as IPV6 for me is both a blessing and a curse :D

    0
    Comment actions Permalink
  • Avatar
    Radagast82

    Guys, an important update. 

    First of all, let me say sorry. Sorry to Firewalla team. The above problem wasn't due to FWG or anything else on that side, but my crappy (previous) ISP. 

    Today I finalized the switch to a new one (2.5gb by the way). Same connection protocol (PPPoE), IPv6 enabled on wan and lan. Perfectly working, no workaround needed (like the manual setting of the gateway etc). All my devices obtain a valid IPv6 address, all test passed, and all without a manual setting or other.

    On "hardware" side, I just put on the Ubuntu 22 image, but I guess it's not a reason for everything working now. 

    Again, sorry 

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    Thank you for the update @Radagast82!

    0
    Comment actions Permalink

Please sign in to leave a comment.