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

    Problem with a second pfSense in LAN

    IPv6
    2
    4
    812
    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.
    • maxxerM
      maxxer
      last edited by

      hi.
      My office pfsense happily works with an IPv6 tunnel since months.
      right now I'm preparing a new server in my lab, and it's running pfSense 2.2.4.
      I don't have IPv6 enabled on this new box, nor DHCP of any kind (relay/server), nevertheless when it's running my client DHCPv6 gets crazy and keeps looping, even if it receives a lease.
      If I shut down the second pfSense everything returns to normality.
      It's not the first time it happens to me, when there's a second pfSense in LAN (even if the second pfSense has a fixed IP in another subnet) the network misbehaves.

      What could it be?
      I'm attaching here a log of the DHCP client.

      P.S. pfSense is not acting as a DHCPv6 but just as RA

      Aug  6 13:46:12 dharma dbus[895]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug  6 13:46:12 dharma nm-dispatcher: Dispatching action 'dhcp6-change' for wlan0
Aug  6 13:46:12 dharma systemd[1]: Started Network Manager Script Dispatcher Service.
Aug  6 13:46:30 dharma NetworkManager[885]: <info>Activation (wlan0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Aug  6 13:46:30 dharma NetworkManager[885]: <info>Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Aug  6 13:46:30 dharma NetworkManager[885]: <info>dhclient started with pid 11561
Aug  6 13:46:30 dharma NetworkManager[885]: <info>(wlan0): DHCPv6 state changed nbi -> preinit6
Aug  6 13:46:31 dharma dhclient: XMT: Confirm on wlan0, interval 1070ms.
Aug  6 13:46:31 dharma dhclient: RCV: Reply message on wlan0 from fe80::5054:ff:fecb:dd27.
Aug  6 13:46:31 dharma dhclient: message status code Success: "all addresses still on link"
Aug  6 13:46:31 dharma NetworkManager[885]: <info>(wlan0): DHCPv6 state changed preinit6 -> bound6
Aug  6 13:46:31 dharma NetworkManager[885]: <info>valid_lft 7500
Aug  6 13:46:31 dharma NetworkManager[885]: <info>preferred_lft 7200
Aug  6 13:46:31 dharma NetworkManager[885]: <info>address 2001:1:2:858b::ff2f
Aug  6 13:46:31 dharma NetworkManager[885]: <info>nameserver '2001:1:2:858b::190'
Aug  6 13:46:31 dharma dbus[895]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Aug  6 13:46:31 dharma systemd[1]: Starting Network Manager Script Dispatcher Service...
Aug  6 13:46:31 dharma dbus[895]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Aug  6 13:46:31 dharma systemd[1]: Started Network Manager Script Dispatcher Service.
Aug  6 13:46:31 dharma nm-dispatcher: Dispatching action 'dhcp6-change' for wlan0
Aug  6 13:46:32 dharma avahi-daemon[858]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::8a53:2eff:fe90:6aa5.
Aug  6 13:46:32 dharma avahi-daemon[858]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2001:1:2:858b::ff2f.
Aug  6 13:46:32 dharma avahi-daemon[858]: Registering new address record for 2001:1:2:858b::ff2f on wlan0.*.
Aug  6 13:46:32 dharma avahi-daemon[858]: Withdrawing address record for fe80::8a53:2eff:fe90:6aa5 on wlan0.
Aug  6 13:46:32 dharma NetworkManager[885]: <info>dhclient started with pid 11575
Aug  6 13:46:33 dharma NetworkManager[885]: <info>(wlan0): canceled DHCP transaction, DHCP client pid 11561
Aug  6 13:46:33 dharma NetworkManager[885]: <info>Activation (wlan0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Aug  6 13:46:33 dharma NetworkManager[885]: <info>Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Aug  6 13:46:33 dharma NetworkManager[885]: <info>dhclient started with pid 11576
Aug  6 13:46:33 dharma NetworkManager[885]: <info>Writing DNS information to /sbin/resolvconf
Aug  6 13:46:33 dharma dnsmasq[1957]: impostazione del server upstream da DBus
Aug  6 13:46:33 dharma dnsmasq[1957]: utilizzo del server dei nomi 2001:1:2:858b::190#53
Aug  6 13:46:33 dharma dnsmasq[1957]: utilizzo del server dei nomi 10.1.1.190#53
Aug  6 13:46:34 dharma dhclient: XMT: Info-Request on wlan0, interval 1080ms.
Aug  6 13:46:34 dharma dhclient: RCV: Reply message on wlan0 from fe80::5054:ff:fecb:dd27.
Aug  6 13:46:34 dharma NetworkManager[885]: <info>(wlan0): DHCPv6 state changed nbi -> renew6
Aug  6 13:46:34 dharma NetworkManager[885]: <info>nameserver '2001:1:2:858b::190'
Aug  6 13:46:34 dharma NetworkManager[885]: <info>(wlan0): DHCPv6 client pid 11576 exited with status 0
Aug  6 13:46:35 dharma dnsmasq[1919]: reading /etc/resolv.conf
Aug  6 13:46:35 dharma dnsmasq[1919]: using nameserver 127.0.1.1#53
Aug  6 13:46:42 dharma NetworkManager[885]: <info>Activation (wlan0) Stage 3 of 5 (IP Configure Start) starting DHCPv6 as requested by IPv6 router...
Aug  6 13:46:42 dharma NetworkManager[885]: <info>Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Aug  6 13:46:42 dharma NetworkManager[885]: <info>dhclient started with pid 11639
Aug  6 13:46:42 dharma NetworkManager[885]: <info>(wlan0): DHCPv6 state changed nbi -> preinit6
Aug  6 13:46:42 dharma dhclient: XMT: Confirm on wlan0, interval 1030ms.
Aug  6 13:46:42 dharma dhclient: RCV: Reply message on wlan0 from fe80::5054:ff:fecb:dd27.
Aug  6 13:46:42 dharma dhclient: message status code Success: "all addresses still on link"
Aug  6 13:46:42 dharma NetworkManager[885]: <info>(wlan0): DHCPv6 state changed preinit6 -> bound6
Aug  6 13:46:42 dharma NetworkManager[885]: <info>valid_lft 7500
Aug  6 13:46:42 dharma NetworkManager[885]: <info>preferred_lft 7200
Aug  6 13:46:42 dharma NetworkManager[885]: <info>address 2001:1:2:858b::ff2f
Aug  6 13:46:42 dharma NetworkManager[885]: <info>nameserver '2001:1:2:858b::190'</info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info></info>
      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        You might want to prevent the NetworkManager beep from "managing" your IPv6 at least… Never worked properly, only causing giant borkage.

        1 Reply Last reply Reply Quote 0
        • maxxerM
          maxxer
          last edited by

          @doktornotor:

          You might want to prevent the NetworkManager beep from "managing" your IPv6 at least… Never worked properly, only causing giant borkage.

          indeed I never loved it… but how would you do without it on the desktop?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            IIRC from last time I touched this damned thing - there are tabs to separately disable the IPv6 stuff only. Might be distro, NM version and init specific though. Probably better asked elsewhere.

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