Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 128 replies
  • Answers 2 answers
  • Subscribers 10 subscribers
  • Views 296697 views
  • Users 0 members are here
Options
Suggested

Open IPv6 Issues / questions

Ben

- will the fix for issue NUTM-7187 be included with 9.5?

- is there a fix in the works for IPv6 Connections where the WAN Port is supposed to use an address out of the delegated prefix? Currently users of such ISPs do not get any IPv6 address. (for esxample KPN netherlands)

- what about the ability to change/edit the UID for IPv6 Delegation Requests?

- what about long standing feature requests such as 6tunnel integration, lets encrypt - is that on the roadmap? Users, myself included had high hopes for 9.5 but this seems to be more than a maintance release.

 

thank you in advance.

Parents
  • +1

    Hi Ben, please see my answers inline below:

    Ben said:

    - will the fix for issue NUTM-7187 be included with 9.5?

     [BL]: The fix for NUTM-7187 is not included in this current UTM 9.5 beta version. We are actively working on the fix right now though, so as soon as we have a confirmed fix it will be included in a subsequent release.

    - is there a fix in the works for IPv6 Connections where the WAN Port is supposed to use an address out of the delegated prefix? Currently users of such ISPs do not get any IPv6 address. (for esxample KPN netherlands)

    [BL]: This should be supported today, unless the ISP is doing both stateless & stateful. Is that the case for you? If so, we are fixing that as part of NUTM-7187 as well.

    - what about the ability to change/edit the UID for IPv6 Delegation Requests?

    [BL]: Unfortunately this isn't part of this 9.5 release.

    - what about long standing feature requests such as 6tunnel integration, lets encrypt - is that on the roadmap? Users, myself included had high hopes for 9.5 but this seems to be more than a maintance release.

    [BL]: Lets Encrypt is on our current roadmap, but it's mainly planned as a WAF feature. As for 6tunnel integration, it's currently not planned for any specific release.

     

    thank you in advance.

     

  • 0 in reply to bobbylam

    Hi Bobby,

    Normally the ISPs router will then request /48 prefix and use a /64 from that prefix for the wan interface and a /64for the lan interface. So there are no other global ipv6 addresses than the ones from that /48.

    On the Sophos UTM, in my case I will only receive a link local IPv6 address via PPPoE. Using a tcpdump I have verified the UTM is not sending out a prefix request after the PPPoE has been established. Is it waiting for a advertised IPv6 address for the WAN interface first before it will do this? Because in this case it will never get it... And thus a IPv6 prefix will never be requested.

    If you want to have a look at my Sophos VM, or need some tcpdumps of the PPPoE setup let me know!

    Rene

  • 0 in reply to Duc Le

    Hi Le,

    Just sent you the login details for my UTM. 
    Already added the two ip6table rules. Tried to ping6 google.com, dmesg output attached.

    Kind regards,

    Sander

    Fullscreen dmesg.txt Download 
    [32711.333847] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=553 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=57757 LEN=513
[32711.456834] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=259 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=51561 LEN=219
[32712.044663] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=521 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=65523 LEN=481
[32712.051273] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=531 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=64634 LEN=491
[32716.015921] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=64 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
[32716.340549] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
[32719.602387] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27397 SEQ=1
[32719.602415] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27397 SEQ=1
[32720.014982] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=64 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
[32720.609683] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27397 SEQ=2
[32721.617441] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27397 SEQ=3
[32722.625206] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27397 SEQ=4
[32723.632963] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=27397 SEQ=5
[32724.536578] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=448 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=61611 LEN=408
[32724.546787] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=460 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=62161 LEN=420
[32725.026543] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
[32727.044946] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=560 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=56127 LEN=520
[32727.064740] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=520 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=65449 LEN=480
[32727.065520] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 DST=2a02:26f0:007b:048a:0000:0000:0000:1abd LEN=72 TC=0 HOPLIMIT=63 FLOWLBL=62641 PROTO=TCP SPT=49897 DPT=80 WINDOW=64800 RES=0x00 SYN URGP=0
[32730.169517] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 DST=2605:0380:0032:0351:0000:0000:0000:000e LEN=72 TC=0 HOPLIMIT=63 FLOWLBL=55324 PROTO=TCP SPT=49898 DPT=5938 WINDOW=64800 RES=0x00 SYN URGP=0
[32733.090322] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 DST=2a02:26f0:007b:048c:0000:0000:0000:201a LEN=72 TC=0 HOPLIMIT=63 FLOWLBL=840252 PROTO=TCP SPT=49899 DPT=80 WINDOW=64800 RES=0x00 SYN URGP=0
[32735.011479] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=64 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
[32742.415121] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=259 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=53 DPT=53744 LEN=219
[32743.774562] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=33541 SEQ=1
[32743.774595] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=33541 SEQ=1
[32744.559620] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=108 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=68
[32744.559640] ICMP_POST:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=108 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=UDP SPT=547 DPT=546 LEN=68
[32744.564693] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
[32744.774004] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=33541 SEQ=2
[32745.009590] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=ff02:0000:0000:0000:0000:0000:0000:0001 LEN=120 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=134 CODE=0
[32745.509003] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
[32745.773781] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=33541 SEQ=3
[32746.508762] ICMP_OUTPUT:IN= OUT=eth0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0
[32746.581196] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 DST=2a01:0111:2003:0000:0000:0000:0000:0052 LEN=72 TC=0 HOPLIMIT=63 FLOWLBL=656277 PROTO=TCP SPT=49923 DPT=80 WINDOW=64800 RES=0x00 SYN URGP=0
[32746.773595] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=33541 SEQ=4
[32747.421369] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
[32747.611615] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 DST=2a01:0111:f330:1790:0000:0000:0000:0a01 LEN=72 TC=0 HOPLIMIT=63 FLOWLBL=712704 PROTO=TCP SPT=49926 DPT=443 WINDOW=64800 RES=0x00 SYN URGP=0
[32747.773307] ICMP_OUTPUT:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:0000:0000:0000:0001 DST=2a00:1450:4009:080f:0000:0000:0000:200e LEN=104 TC=0 HOPLIMIT=64 FLOWLBL=0 PROTO=ICMPv6 TYPE=128 CODE=0 ID=33541 SEQ=5
[32748.087268] ICMP_POST:IN= OUT=ppp0 SRC=2001:0981:9d6e:0001:d5c2:a358:31e0:a6e7 DST=2a02:26f0:007b:048f:0000:0000:0000:1abd LEN=72 TC=0 HOPLIMIT=63 FLOWLBL=719581 PROTO=TCP SPT=49927 DPT=80 WINDOW=64800 RES=0x00 SYN URGP=0
[32749.564888] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=72 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=135 CODE=0
[32750.007995] ICMP_OUTPUT:IN= OUT=eth0 SRC=fe80:0000:0000:0000:021a:8cff:fe49:1608 DST=fe80:0000:0000:0000:9584:0a8e:371a:73ee LEN=64 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=136 CODE=0

  • 0 in reply to Duc Le

    Hello Le,

    thank you for taking care of leftover issues with IPv6. Just the other day i was talking to someone who has "Deutsche Glasfaser" (one of the larger direct fiber providers in north-west germany). Appearently they are using 6rd for IPv6 Dual Stack. Would supporting 6rd be more of a feature request or do you want to address this aswell within this bugfix? (i don't know much about 6rd as i did not run into this issue before)

    thank you again for you work on this.

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0 in reply to Ben

    @  

    Thanks so much for your help for the capture (dmesg). The ping6 traffics was hitting the ppp0 3 times. But why there is no reply? This is still a puzzle.

    I sent a PM wrt login info. Thanks again.

    @ Ben

    Team decision is needed for 6rd support. I will pass your request on.

    Your comments and help are appreciated. Thanks again.

  • 0 in reply to Duc Le

    Le,

    will all these ipv6 improvement also go into the Sophos XG? I noticed that ipv6 is "completly broken" there. While i have no interested in switching, i was wondering if these things will be adressed there aswell.

    thank you again for the information and work on the ipv6 fixes on the UTM.

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0 in reply to Ben

    Hi Ben,

     

    Since the architecture for XG is fundamentally different than the UTM, these changes are not easily portable to XG, and will have to be worked on separately.

    Please be assured though we are also working hard to improve the functionality on XG, it's just the fixes won't be a direct/easy port from UTM to XG.

  • 0 in reply to SanderRutten

    Hi SanderRutten,

       Thanks a lot for allowing ssh into the UTM.

       Here is a quick summary:

       1) When I inherited the system from this morning, the ping6 to google.com did not work despite

            the facts all seemed to be fine with UTM.

            a) ip6table logging indicated that the ip6table passed all the ICMPv6 to the hardware interface

            b) The tcpdump indicated that it captured ICMPv6 on the hardware interface

            However there were never responses from google.com 

             UNTIL

        2) About 5 hours into debugging the system, i.e. verifying system thru:

            a) dmesg to see the ip6table logging of ICMPv6 traffic

            b) ip -6 route see the default route for PPPoE

            c) tcpdump -i eth1 for pppoe traffics

            d) tcpdump -i ppp0 for ICMPv6 traffics

            e) ps -elaf | egrep 'dhc|watch|ppp'

             They all indicated that the traffics were sent to the other end of PPPoE connection but there was no response,

     

             THEN out of no where, ping6 started to work like a charm. It has been going strong for over 1 hour now.

             I will let it go for a while and let you know when I am back tomorrow.

     

             Hence at this point, it is a puzzle while it started to work; everything from UTM seemed to indicate that it should

             work. So going forward, is there anyway can you confirm that the ICMPv6 packets do get on the wire, i.e.

             port mirroring on the upstream switch (if there is a switch between UTM and ISP) or somehow working with ISP to

             determine it; I just want to make sure that UTM sends out the ICMPv6 packet to eliminate upstream issue.

     

              That's all for now. Please let me know your comments, ideas or questions.

              Again, thanks so much for your help.

     

  • 0 in reply to Duc Le

    Hello Le,
    Thanks again for looking into the problem!
    Can try a port mirror, although I have never used it. (I'm not a standard home user but neither a network tech :P)

    My network setup is: ISP > Switch Port1 > Switch Port2 > Sophos SG125w WAN port
    I have setup a port mirror for port 2. When I'm home tonight I can hopefully capture with my laptop attached to the mirrored port and run wireshark.

    I sure hope we will find something, but to be honest I doubt that we will find a cause here.
    When I connect my OpenWRT router, IPv6 works. If I power on my OPNSense firewall, it also works. When testing PFSense for a short while, it also worked.

  • 0 in reply to SanderRutten

    Hi SanderRutten,

       Thanks for your help.

       The ping6 testing is still going strong for almost 16 hours now. Every ping was fine (about 56000).

     

       I am in the same boat with you, i.e. I don't feel comfortable when things start not to work and start to work

       without any apparent reasons. So I am not letting up this issue. On my side, I am still looking for possible hypothesis

       as to why it does not work. I will update ASAP.

     

       Thanks for the port mirroring work. Good luck.

        Also, please let me know your thinking. It is appreciated. Thx.

     

    Edit:

    New additional info updated at 2:00PM Vancouver time and 10:00PM German Time:

    1) The ping6 is going strong for full 24 hours now; sending out close to 80K pings without problem

    2) At this time, the prefix renew was also successful for the same prefix after 12 hour renewal interval from 10:00AM to 10:00PM German time

    So far so good.

  • 0 in reply to Duc Le

    Hi Le,

    Little update on the 6rd: 

    I was in touch with a fellow sophos community member. He is using "Deutsche Glasfaser" which offers IPv6 via 6rd.

    We managed to get an IPv6 Address for the WAN Interface so far which is working fine. What does not work is getting a route for the Internal LAN Interfaces (but we didnt really try cause of time issue)

    For the 6rd i think we can manage to establish that with a small script that calculates the own prefix via the CGN IPv4 and the Provider /32 IPv6 network. 

    If an integration into the UTM Webadmin was to happen it would probably be required beeing able to enter the Provider IPv6 Prefix, 6rd IPv4 Gateway and Netmask into a GUI mask. Since the Kernel requirements and basic working is allready in, maybe it would be easier to considerate integrating this.

    ---

    Sophos UTM 9.3 Certified Engineer

  • 0 in reply to rklomp

    Hi Rene,

       I really appreciate that you can give us some update wrt your default route issue.

       Is there anyway I can have access into tour UTM to debug with you?

       Thanks for your time and help.

Reply Children
No Data
Unfiltered HTML