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

    Long time to get IP gateway from dhcp

    Scheduled Pinned Locked Moved DHCP and DNS
    19 Posts 3 Posters 749 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
      mathais @mathais
      last edited by

      @mathais
      Thank you for your help.

      My other wifi is from a TP-Link Archer AX53 with dhcp disabled and static IP.
      I set a static IP to my new AP. When a client try to connect, pfsense attribute an IP to the clients through the wifi, but it’s really long…
      I have to wait about 2 minutes… In first, when I join my SSID wifi, I can access to the AP web interface instantly, but I have to wait more for internet access… on mac the wifi icon displays an exclamation point with the message “no internet access”. But I can ping local machines on my Lan… but can’t ping the pfsense gateway… That’s really weird…

      Here is my dhcp log through TP-Link Archer AX53

      Mar 17 07:33:03	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_LEASE_ALLOC [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272061: lease 192.168.2.59 has been allocated for 7200 seconds
Mar 17 07:33:03	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:33:03	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:33:03	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:33:03	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt5_0 evaluated to 1
Mar 17 07:33:02	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_LEASE_ADVERT [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272061: lease 192.168.2.59 will be advertised
Mar 17 07:33:02	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:33:02	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:33:02	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:33:02	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt5_0 evaluated to 1
Mar 17 07:32:50	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_LEASE_ALLOC [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272060: lease 192.168.2.59 has been allocated for 7200 seconds
Mar 17 07:32:50	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:32:50	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:32:50	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:32:50	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt5_0 evaluated to 1
Mar 17 07:32:49	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea15f00] DHCP4_LEASE_ADVERT [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272060: lease 192.168.2.59 will be advertised
Mar 17 07:32:49	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea15f00] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:32:49	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea15f00] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:32:49	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea15f00] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:32:49	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea15f00] EVAL_RESULT Expression pool_opt5_0 evaluated to 1

      And Here, my dhcp log through Tenda AP.

      Mar 17 07:40:11	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_LEASE_ALLOC [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272063: lease 192.168.2.59 has been allocated for 7200 seconds
Mar 17 07:40:11	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:40:11	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:40:11	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:40:11	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt5_0 evaluated to 1
Mar 17 07:40:10	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_LEASE_ADVERT [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272063: lease 192.168.2.59 will be advertised
Mar 17 07:40:10	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:40:10	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:40:10	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:40:10	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt5_0 evaluated to 1
Mar 17 07:40:04	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_LEASE_ALLOC [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272062: lease 192.168.2.59 has been allocated for 86400 seconds
Mar 17 07:40:04	kea-dhcp4	49666	INFO [kea-dhcp4.leases.0x31952ea17400] DHCP4_INIT_REBOOT [hwtype=1 9c:3e:53:XX:XX:XX], cid=[01:9c:3e:53:XX:XX:XX], tid=0x1f272062: client is in INIT-REBOOT state and requests address 192.168.2.59
Mar 17 07:40:04	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt6_0 evaluated to 1
Mar 17 07:40:04	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt2_0 evaluated to 1
Mar 17 07:40:04	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt3_0 evaluated to 1
Mar 17 07:40:04	kea-dhcp4	49666	INFO [kea-dhcp4.dhcpsrv.0x31952ea17400] EVAL_RESULT Expression pool_opt5_0 evaluated to 1

      Capture d’écran 2024-03-17 à 07.47.16.png

      johnpozJ 1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator @mathais
        last edited by

        @mathais switch back to isc dhcp.. Kea is PREVIEW... Atleast can understand those logs better.

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        M 2 Replies Last reply Reply Quote 0
        • M
          mathais @johnpoz
          last edited by

          @johnpoz ok I tried it and it doesn’t solved my problem.

          I will test again and past the log here.

          1 Reply Last reply Reply Quote 0
          • M
            mathais @johnpoz
            last edited by

            @johnpoz said in Long time to get IP gateway from dhcp:

            @mathais switch back to isc dhcp.. Kea is PREVIEW... Atleast can understand those logs better.

            So,

            Here the log when I plug the AP to the Switch :

            Mar 17 13:44:56	dhcpd	91366	DHCPACK on 192.168.2.12 to 58:d9:d5:e0:XX:XX via bridge0
Mar 17 13:44:56	dhcpd	91366	DHCPREQUEST for 192.168.2.12 (192.168.2.1) from 58:d9:d5:e0:XX:XX via bridge0
Mar 17 13:44:55	dhcpd	91366	DHCPOFFER on 192.168.2.12 to 58:d9:d5:e0:XX:XX via bridge0
Mar 17 13:44:55	dhcpd	91366	DHCPDISCOVER from 58:d9:d5:e0:XX:XX via bridge0

            Here the log when I join the network through the AP :

            Mar 17 13:09:03	dhcpd	91366	DHCPACK on 192.168.2.59 to 9c:3e:53:72:XX:XX via bridge0
Mar 17 13:09:03	dhcpd	91366	DHCPREQUEST for 192.168.2.59 (192.168.2.1) from 9c:3e:53:72:XX:XX via bridge0
Mar 17 13:09:03	dhcpd	91366	uid lease 192.168.2.101 for client 9c:3e:53:72:XX:XX is duplicate on 192.168.2.0/24
Mar 17 13:09:02	dhcpd	91366	DHCPOFFER on 192.168.2.59 to 9c:3e:53:72:XX:XX via bridge0
Mar 17 13:09:02	dhcpd	91366	DHCPDISCOVER from 9c:3e:53:72:XX:XX via bridge0
Mar 17 13:09:02	dhcpd	91366	uid lease 192.168.2.101 for client 9c:3e:53:72:XX:XX is duplicate on 192.168.2.0/24

            Here the log when I join the network through AP with another device (SmartPhone) :

            Mar 17 14:11:21	dhcpd	91366	DHCPDISCOVER from 42:a3:1d:77:XX:XX via bridge0
Mar 17 14:11:22	dhcpd	91366	DHCPOFFER on 192.168.2.123 to 42:a3:1d:77:XX:XX via bridge0
Mar 17 14:11:23	dhcpd	91366	DHCPREQUEST for 192.168.2.123 (192.168.2.1) from 42:a3:1d:77:XX:XX via bridge0
Mar 17 14:11:23	dhcpd	91366	DHCPACK on 192.168.2.123 to 42:a3:1d:77:XX:XX via bridge0
            johnpozJ 1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @mathais
              last edited by

              @mathais said in Long time to get IP gateway from dhcp:

              id lease 192.168.2.101 for client 9c:3e:53:72:XX:XX is duplicate on 192.168.2.0/24

              Sure looks like you got a duplicate IP issue..

              An intelligent man is sometimes forced to be drunk to spend time with his fools
              If you get confused: Listen to the Music Play
              Please don't Chat/PM me for help, unless mod related
              SG-4860 24.11 | Lab VMs 2.8, 24.11

              M 1 Reply Last reply Reply Quote 0
              • M
                mathais @johnpoz
                last edited by

                @johnpoz said in Long time to get IP gateway from dhcp:

                9c:3e:53:72

                I saw this line, but I really don't understand why this happens.
                I only have one computer. I don't understand why he is trying to connect with two IP addresses?

                IP address 192.168.2.101 is from DHCP Range.
                IP address 192.168.2.59 is from the Static IP from DHCP static table.

                johnpozJ M 3 Replies Last reply Reply Quote 0
                • johnpozJ
                  johnpoz LAYER 8 Global Moderator @mathais
                  last edited by

                  @mathais said in Long time to get IP gateway from dhcp:

                  IP address 192.168.2.59 is from the Static IP from DHCP static table.

                  Huh??

                  An intelligent man is sometimes forced to be drunk to spend time with his fools
                  If you get confused: Listen to the Music Play
                  Please don't Chat/PM me for help, unless mod related
                  SG-4860 24.11 | Lab VMs 2.8, 24.11

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

                    @mathais DHCP.jpg
                    Yes, look at this screenshot.
                    And I have the same log when I connect through my other router TP-LINK and it works well...

                    To try, I ordered and receive tomorow the same tenda I29 and the NetGear WAX615...

                    1 Reply Last reply Reply Quote 0
                    • johnpozJ
                      johnpoz LAYER 8 Global Moderator @mathais
                      last edited by

                      @mathais If you have network 192.168.2 and some client X 9c:3e:53:72:XX:XX.. Doesn't matter if this client talks to the 192.168.2 network through AP X or AP Y... This client would always get the reservation you set..

                      How exactly do you have these AP connected? You have them connected via some bridge in pfsense?

                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                      If you get confused: Listen to the Music Play
                      Please don't Chat/PM me for help, unless mod related
                      SG-4860 24.11 | Lab VMs 2.8, 24.11

                      GertjanG M 2 Replies Last reply Reply Quote 0
                      • GertjanG
                        Gertjan @johnpoz
                        last edited by

                        @johnpoz said in Long time to get IP gateway from dhcp:

                        You have them connected via some bridge in pfsense?

                        @mathais said in Long time to get IP gateway from dhcp:

                        But my pfsense lan is a bridge from two interfaces.

                        No "help me" PM's please. Use the forum, the community will thank you.
                        Edit : and where are the logs ??

                        1 Reply Last reply Reply Quote 0
                        • M
                          mathais @johnpoz
                          last edited by

                          @johnpoz I'm not looking to connect multiple access points. I want to connect a single access point replacing my existing access point.

                          I only have one bridge network from 2 physical interfaces and it works well since 1 year. The bridge is plugged to a switch for all my computers.
                          I want to connect the access point like a computer through an ethernet port.

                          I don't understand your comments regarding reservations...

                          On the network connection (bridge) I have all my network infrastructure connected and it works very well. The access point connects to this network to distribute the network connection to Wi-Fi. It works very well with my old Wi-Fi router, but not with the new access point, even though I am configured exactly the same.

                          johnpozJ 1 Reply Last reply Reply Quote 0
                          • johnpozJ
                            johnpoz LAYER 8 Global Moderator @mathais
                            last edited by

                            @mathais said in Long time to get IP gateway from dhcp:

                            I don't understand your comments regarding reservations...

                            A reservation - this is what it actually is.. You reserve IP address xyz for device with mac 123..

                            What AP you use has zero to do with that.. Look in your lease table.. Do you have a lease for this mac address 9c:3e:53:72:XX:XX (btw there is little reason to hide that mac) not sure what you think someone would be able to do with it?

                            Here are the macs of many of my devices - what would anyone be able to do with those? They are unique to said device, and are only ever seen on the local layer 2 network they are attached too.

                            macs.jpg

                            Look in your lease table - remove any old lease(s), and that error should go away.

                            An intelligent man is sometimes forced to be drunk to spend time with his fools
                            If you get confused: Listen to the Music Play
                            Please don't Chat/PM me for help, unless mod related
                            SG-4860 24.11 | Lab VMs 2.8, 24.11

                            1 Reply Last reply Reply Quote 0
                            • M
                              mathais @johnpoz
                              last edited by

                              @johnpoz
                              My other wifi is from a TP-Link Archer AX53 with dhcp disabled and static IP.

                              I set a static IP to my new AP. When a client try to connect, pfsense attribute an IP to the clients through the wifi, but it’s really long…

                              I have to wait about 2 minutes… In first, when I join my SSID wifi, I can access to the AP web interface instantly, but I have to wait more for internet access… on mac the wifi icon displays an exclamation point with the message “no internet access”.

                              But I can ping local machines on my Lan… but can’t ping the pfsense gateway…

                              That’s really weird…

                              johnpozJ 1 Reply Last reply Reply Quote 0
                              • johnpozJ
                                johnpoz LAYER 8 Global Moderator @mathais
                                last edited by johnpoz

                                @mathais said in Long time to get IP gateway from dhcp:

                                I set a static IP to my new AP

                                Not sure why you think the IP address of your AP has anything to do with anything - its not involved with anything to do with some client and pfsense. The AP is just a bridge between the wireless and the wired connection it has just passes info on.. Its IP or mac never comes into play.

                                Here..

                                Mar 17 09:07:18 	dhcpd 	81584 	DHCPACK on 192.168.7.103 to 00:bd:3e:ac:c9:da via igb5
Mar 17 09:07:18 	dhcpd 	81584 	DHCPREQUEST for 192.168.7.103 (192.168.7.253) from 00:bd:3e:ac:c9:da via igb5
Mar 17 09:07:18 	dhcpd 	81584 	DHCPOFFER on 192.168.7.103 to 00:bd:3e:ac:c9:da via igb5
Mar 17 09:07:17 	dhcpd 	81584 	DHCPDISCOVER from 00:bd:3e:ac:c9:da via igb5

                                Here is a discover from my wireless TV wanting an IP via one of my AP.. The whole process from discover to over to request to ack is like 1 second.

                                Nowhere in this conversation is the AP IP or mac address even involved.. If you see the discover and then offer done by dhcp running on pfsense happen quickly - anything else going on has nothing to do with pfsense... If you see the discover and then no offer or a very large delay then ok something is going on with pfsense.

                                Maybe your AP is doing something with the dhcp? They quite often have different feature sets for dhcp.. They have dhcp snooping options, guarding options, etc.. But from pfsense point of view it has zero clue to if that dhcp came in via a wire or over wifi.. Its just answering what it sees.. And putting it back out on the wire.. If you see it send the offer and your client doesn't accept it, or never sees it because something on your AP.. That has zero to do with pfsense.

                                An intelligent man is sometimes forced to be drunk to spend time with his fools
                                If you get confused: Listen to the Music Play
                                Please don't Chat/PM me for help, unless mod related
                                SG-4860 24.11 | Lab VMs 2.8, 24.11

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  mathais @johnpoz
                                  last edited by

                                  @johnpoz Hi,
                                  Thank for your help, but today, I can confirm that the problem is from the TENDA I29 AP... This AP is so weird.
                                  The web interface has few options. I don't know what's going on, but the access point refuses to connect to the LAN...

                                  Today, I received a second TENDA I29 access point, and the problem is the same.

                                  I also received a NETGEAR WAX615 hotspot today. And guess what?!

                                  Miracle ! Everything works on the first try...
                                  I performed the same operations:

                                  • Set a static IP
                                  • Set mask
                                  • Define the gateway and DNS1 to my pfsense...

                                  Everything works the first time.
                                  I even configured my VLANs for my different SSIDs, all in less than 15 minutes!!

                                  I have no explanation regarding the TENDA access points... I performed the Firmware updates, but it didn't change anything...

                                  I will send them back to Amazon...

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