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

    BT Business Broadand - Bridged Mode - DHCP6 not working?

    Scheduled Pinned Locked Moved IPv6
    5 Posts 2 Posters 510 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.
    • M
      MHall 0
      last edited by MHall 0

      Hi All,

      i've recently had a backup internet connection installed using BT Business in the UK,

      The supplied router has been changed to bridged mode, and i'm able to PPPoE login fine over IPv4, however, the IPv6 isn't working for me,

      i've tried numerous combinations of the check boxes (in combinations found by web searches) but don't seem to get an address / delegation.

      has any one got a working implementation?,
      ideally i want to be able to run NPt on the IPv6 range received if at all possible,
      with my VLAN's running seperate /64's

      here's the log from PPP for the following config
      09607ea3-8b2a-4d21-b85f-9a03097fe5d6-image.png
      and a vlan lan interface setting
      d210b60a-534d-4185-a4b3-c49d4975ae18-image.png

      Mar 12 15:30:42 ppp 58133 [wan] 86.148.xxx.xxx -> 172.16.11.100
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: LayerUp
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: state change Ack-Rcvd --> Opened
      Mar 12 15:30:42 ppp 58133 [wan] IPADDR 172.16.11.100
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: SendConfigAck #213
      Mar 12 15:30:42 ppp 58133 [wan] 172.16.11.100 is OK
      Mar 12 15:30:42 ppp 58133 [wan] IPADDR 172.16.11.100
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: rec'd Configure Request #213 (Ack-Rcvd)
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: state change Req-Sent --> Ack-Rcvd
      Mar 12 15:30:42 ppp 58133 [wan] IPADDR 86.148.xxx.xxx
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: rec'd Configure Ack #3 (Req-Sent)
      Mar 12 15:30:42 ppp 58133 [wan] IPADDR 86.148.xxx.xxx
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: SendConfigReq #3
      Mar 12 15:30:42 ppp 58133 [wan] 86.148.xxx.xxx is OK
      Mar 12 15:30:42 ppp 58133 [wan] IPADDR 86.148.xxx.xxx
      Mar 12 15:30:42 ppp 58133 [wan] IPCP: rec'd Configure Nak #2 (Req-Sent)
      Mar 12 15:30:42 ppp 58133 [wan] IFACE: Add description "WAN2_BT"
      Mar 12 15:30:42 ppp 58133 [wan] IFACE: Rename interface ng0 to pppoe0
      Mar 12 15:30:42 ppp 58133 [wan] IFACE: Up event
      Mar 12 15:30:40 ppp 58133 [wan] 0208:a2ff:xxx:xxxx -> 427c:7dff:xxxx:xxxx
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: LayerUp
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: state change Ack-Sent --> Opened
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: rec'd Configure Ack #1 (Ack-Sent)
      Mar 12 15:30:40 ppp 58133 [wan] IPADDR 0.0.0.0
      Mar 12 15:30:40 ppp 58133 [wan] IPCP: SendConfigReq #2
      Mar 12 15:30:40 ppp 58133 [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
      Mar 12 15:30:40 ppp 58133 [wan] IPCP: rec'd Configure Reject #1 (Req-Sent)
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: state change Req-Sent --> Ack-Sent
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: SendConfigAck #29
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: rec'd Configure Request #29 (Req-Sent)
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: SendConfigReq #1
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: state change Starting --> Req-Sent
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: Up event
      Mar 12 15:30:40 ppp 58133 [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
      Mar 12 15:30:40 ppp 58133 [wan] IPADDR 0.0.0.0
      Mar 12 15:30:40 ppp 58133 [wan] IPCP: SendConfigReq #1
      Mar 12 15:30:40 ppp 58133 [wan] IPCP: state change Starting --> Req-Sent
      Mar 12 15:30:40 ppp 58133 [wan] IPCP: Up event
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: LayerStart
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: state change Initial --> Starting
      Mar 12 15:30:40 ppp 58133 [wan] IPV6CP: Open event

      also interface status
      6b4c09ea-d71a-4c3d-90f6-c6a0ab48b41d-image.png

      and the internal interface with ipv6 set to track interface
      c48740c4-45d4-4e32-a778-8a02f798cd9a-image.png

      1 Reply Last reply Reply Quote 0
      • M
        MHall 0
        last edited by

        huh... so had to enable router advertisements as well on the VLAN Lan 45 interface,
        then it assigned it an ip address out of pressumably the range recieved.

        37f589af-6ecf-4cd3-bc03-0a17f67d38a4-image.png

        doesn't solve what i want, (which may be impossible?)

        which is to use ULA internally (already set up with fd16:: ranges on the LAN / internal VLANS)
        and use NPt to map onto the external WAN IPv6 ranges.

        VioletDragonV 1 Reply Last reply Reply Quote 0
        • VioletDragonV
          VioletDragon @MHall 0
          last edited by

          @MHall-0 are you using BT Fibre Modem by chance? White box ? If so. The White Fibre modem doesn’t work with IPv6 when I was testing it.

          M 1 Reply Last reply Reply Quote 0
          • M
            MHall 0 @VioletDragon
            last edited by

            @VioletDragon No,

            Bt Smart Hub 2

            for now i've backed out of bridged mode,
            i've gone back to NAT'ing everything through the addresses the BT router gives pfSense

            VioletDragonV 1 Reply Last reply Reply Quote 0
            • VioletDragonV
              VioletDragon @MHall 0
              last edited by

              @MHall-0 double NAT will cause problems. I have held off with IPv6 with both ISPs I am with. The Smarthub I have doesn’t have Bridge mode support. Can you get IPv6 working if you use a Windows or Linux ? That would be something to test.

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