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

    SG2100 - Unable to get DHCP WAN IP on GPON interface

    Scheduled Pinned Locked Moved Hardware
    28 Posts 4 Posters 1.4k 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.
    • keyserK
      keyser Rebel Alliance @stealthmode
      last edited by

      @stealthmode VendorID might be the only setting needed - it might not. Sometimes not everything is outputted in Shell command like that. But try

      Love the no fuss of using the official appliances :-)

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by stephenw10

        Mmm, what did you run to get that? I can't decide if that's what the server sent rather than the client.

        S 1 Reply Last reply Reply Quote 0
        • S
          stealthmode @stephenw10
          last edited by

          @stephenw10 The router has a banner

          "RDK (A Yocto Project based Distro) 2.0 GEN8"

          I ran cd wan and then show

          I've configured the PFSense wan interface in this way

          • On mvneta0.12 WAN interface, enabled Advanced Configuration and Configuration Override
          • Set the file as "/root/dhcp-config/dhcp.conf"
          • The file contents are the following:
          interface "mvneta0.12" {
                timeout 60;
                retry 15;
                select-timeout 0;
                send dhcp-class-identifier "meods00";
          }
          
          • Restarted PFsense
          • still don't appear to be getting the WAN IP

          Do you think my configuration is correct here?

          keyserK 1 Reply Last reply Reply Quote 0
          • keyserK
            keyser Rebel Alliance @stealthmode
            last edited by

            @stealthmode Probably, but it’s hard to tell if your setup works as intended unless you do a packet capture.

            I would instead not enable configuration override, and just insert:

            Dhcp-class-identifier “meods00”

            In the send options dialog. Then we know it will be included in the standard DHCP process from pfSense (it will also be fully restorable from a config file if you ever reinstall or move to a different device)

            Love the no fuss of using the official appliances :-)

            S 1 Reply Last reply Reply Quote 2
            • S
              stealthmode @keyser
              last edited by

              @keyser Thank you!

              I followed what you said, and the DHCP options are being sent in the request but I still don't get a WAN IP.

              So it's back to the drawing board for me :|

              IMG_4717 (1).jpg

              1 Reply Last reply Reply Quote 0
              • JonathanLeeJ
                JonathanLee
                last edited by

                The ISP may require the MAC address of the ISP provided router. This would require you to spoof the MAC address into the WAN interface. Do you know if it is locked down to the original router MAC address?

                Make sure to upvote

                S 1 Reply Last reply Reply Quote 1
                • S
                  stealthmode @JonathanLee
                  last edited by

                  @JonathanLee Thank you for your reply. I tried that now, and that didn't help either :(

                  The packet capture shows that I've spoofed the MAC address to that of the ISP router WAN interface

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    stealthmode @stealthmode
                    last edited by

                    I took the static IP which was assigned to the ISP router and manually assigned it to the pfsense WAN interface. By changing the DHCP to Static.

                    After that, in "Status > Interface", I couldn't see any increments on the "In" packets counter. The out packets counter was increasing. Basically, I still didn't have internet access via PFsense.

                    This makes me think that the GPON ONU stick might still not be "fully" authenticated...

                    keyserK 1 Reply Last reply Reply Quote 0
                    • keyserK
                      keyser Rebel Alliance @stealthmode
                      last edited by

                      @stealthmode I don’t think the GPON ONU “authentication” is the issue. When you reach state 5 it is connected and accepted into the GPON tree. I’m pretty sure you are not passing authentication with your ISP on the protocol level. IPoE is specifically authentication via DHCP, and if your DHCP request frame does not pass authentication, the other end (ISP ONT) does not open/pass traffic, and to you that seems like a dead link (no traffic seen/passed).
                      Setting a static IP just makes sure you do not pass authentication - as you are not sending a DHCP frame to Authenticate on :-)

                      I’m quite sure the problem is you are not providing all the options needed. Usually IPoE also requires options that descibes the FX. The circuitID and a authentication password/code.

                      In my setup there is specifically two options that sends a deviceID and a anthentication code - which is why you need a capture of the ISP routers DHCP exchange - otherwise it will be impossible to replay the needed settings.

                      Love the no fuss of using the official appliances :-)

                      S 1 Reply Last reply Reply Quote 2
                      • S
                        stealthmode @keyser
                        last edited by

                        @keyser Thank you very much for your detailed insights... I really appreciate the information that you've provided. It makes sense.

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