Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Apinger uses IPv6 Link Local IP to ping global alternative IP

    Scheduled Pinned Locked Moved 2.1.1 Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      athurdent
      last edited by

      I'm trying to use an alternative monitor IP on a DHCPv6 interface. The IP is a global one but sadly the apinger conf gets generated with a Link Local source IP like this:

      target "2001:838:2:1::30:67" {
              description "WAN2_DHCP6"
              srcip "fe80::290:bff:****:****%em2"
              alarms override "loss","delay","down";
              rrd file "/var/db/rrd/WAN2_DHCP6-quality.rrd"
      }
      
      

      As a result the gateway is offline.

      I'm on
      2.1.1-PRERELEASE (i386)
      built on Sat Mar 1 03:30:07 EST 2014
      FreeBSD 8.3-RELEASE-p14

      1 Reply Last reply Reply Quote 0
      • E Offline
        eri--
        last edited by

        It would be more informative and helpful to state your configuration.

        1 Reply Last reply Reply Quote 0
        • A Offline
          athurdent
          last edited by

          The initial tests were done with my Multi WAN setup but I could also reproduce that on my secondary gateway. That uses only one WAN connection and is a KVM.
          To reproduce the problem I just switch on DHCP6 on the WAN interface, does not matter if I request a prefix or not. The WAN interface is behind an AVM FritzBox 7390 (fe80::c225:::890e) which takes care of the AICCU tunnel. The box is set to do DHCPv6 and hand out a delegated prefix out of my /48 from SixXS.

          pfSense Version:

          2.1.1-PRERELEASE (amd64)
          built on Fri Mar 7 18:35:38 EST 2014
          FreeBSD 8.3-RELEASE-p14
          

          Relevant IP config:

          IPv6 Link Local		fe80::dcad:beff:feef:a043%em3  
          IPv6 address		2001:4dd0:****:0:dcad:beff:feef:a043  
          Subnet mask IPv6	64
          Gateway IPv6		fe80::c225:****:****:890e 
          

          The standard config pinging the AVM box works fine but does not really help me, I'd like to know if the tunnel is OK:

          target "fe80::c225:****:****:890e%em3" {
                  description "WAN2_DHCP6"
                  srcip "fe80::dcad:beff:feef:a043%em3"
                  alarms override "loss","delay","down";
                  rrd file "/var/db/rrd/WAN2_DHCP6-quality.rrd"
          }
          

          Switching the monitor IP to 2001:838:2:1::30:67, which should be a better choice to test if the tunnel is really up & running results in:

          target "2001:838:2:1::30:67" {
                  description "WAN2_DHCP6"
                  srcip "fe80::dcad:beff:feef:a043%em3"
                  alarms override "loss","delay","down";
                  rrd file "/var/db/rrd/WAN2_DHCP6-quality.rrd"
          }
          

          and the gateway is marked down.

          There is however no problem pinging that IP from the shell:

          ping6 2001:838:2:1::30:67
          PING6(56=40+8+8 bytes) 2001:4dd0:****:0:dcad:beff:feef:a043 --> 2001:838:2:1::30:67
          16 bytes from 2001:838:2:1::30:67, icmp_seq=0 hlim=56 time=29.593 ms
          16 bytes from 2001:838:2:1::30:67, icmp_seq=1 hlim=56 time=25.703 ms
          16 bytes from 2001:838:2:1::30:67, icmp_seq=2 hlim=56 time=25.522 ms
          16 bytes from 2001:838:2:1::30:67, icmp_seq=3 hlim=56 time=25.909 ms
          

          If you need any more info, please let me know.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.