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

    Telenet requires dhcp-server-identifier

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 1 Posters 2.7k 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.
    • X
      xtofh
      last edited by

      Hi all,

      I am having a similar problem as http://forum.pfsense.org/index.php/topic,19149.msg107275.html#msg107275.

      Our ISP (Telenet in Belgium, office access subscription) does not always respond when the dhcp renewal request goes out (to the ip of the dhcp server). It does respond (and renews the ip) immediately when dhcp requests go to 255.255.255.255.

      This is a "known" issue over here, I solve it with "supersede dhcp-server-identifier 255.255.255.255;" on linux. It can take up to a few minutes if we don't use this work around.

      Is there a way to do this on pfSense?

      Ps, using latest stable (1.2.3)

      Thanks in advance for any suggestions,

      Kristof

      1 Reply Last reply Reply Quote 0
      • X
        xtofh
        last edited by

        Okay, I have logged some more on this issue. The appliance we use (from applianceshop.eu) is using the network cards: VIA VT6105M Rhine III 10/100BaseTX, 3 of them.

        Every hour this passes by in the system logs:

        Dec 6 09:54:43 	dhclient[57082]: bound to xx.xx.xx.xx -- renewal in 3600 seconds.
        Dec 6 10:54:43 	dhclient[57082]: DHCPREQUEST on vr1 to 195.130.132.102 port 67
        Dec 6 10:54:43 	dhclient[57082]: SENDING DIRECT
        ...
        Dec 6 10:55:36 	dhclient[57082]: DHCPREQUEST on vr1 to 195.130.132.102 port 67
        Dec 6 10:55:36 	dhclient[57082]: SENDING DIRECT
        Dec 6 10:55:50 	dhclient[57082]: DHCPREQUEST on vr1 to 255.255.255.255 port 67
        Dec 6 10:55:50 	dhclient[57082]: DHCPACK from 81.82.zz.zz
        Dec 6 10:55:51 	dhclient[57082]: bound to xx.xx.xx.xx -- renewal in 3600 seconds.
        
        Dec 6 11:55:50 	dhclient[57082]: DHCPREQUEST on vr1 to 195.130.132.102 port 67
        Dec 6 11:55:50 	dhclient[57082]: SENDING DIRECT
        ...
        Dec 6 11:56:33 	dhclient[57082]: DHCPREQUEST on vr1 to 195.130.132.102 port 67
        Dec 6 11:56:33 	dhclient[57082]: SENDING DIRECT
        Dec 6 11:56:52 	dhclient[57082]: DHCPREQUEST on vr1 to 255.255.255.255 port 67
        Dec 6 11:56:52 	dhclient[57082]: DHCPACK from 81.82.zz.zz
        Dec 6 11:56:52 	dhclient[57082]: bound to xx.xx.xx.xx -- renewal in 3600 seconds.
        

        On a similar setup (same provider) but with Linux and using the parameter "supersede dhcp-server-identifier 255.255.255.255;", I see this:

        Dec  6 12:04:29 fw dhclient: DHCPREQUEST on eth4 to 255.255.255.255 port 67
        Dec  6 12:04:29 fw dhclient: DHCPACK from 81.82.zz.zz
        Dec  6 12:04:29 fw dhclient: bound to yy.yy.yy.yy -- renewal in 3592 seconds.
        

        Any workaround to get the same behaviour on pfsense 1.2.3 ?

        Cheers,
        Kristof.

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