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

    One DHCP server is not working correctly

    Scheduled Pinned Locked Moved DHCP and DNS
    9 Posts 3 Posters 627 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.
    • K
      kaiserfranzjosef
      last edited by kaiserfranzjosef

      Hello community,

      I have a PfSense CE running with many interfaces.

      Three interfaces have static IP/4 adresses and are configured to host a DHCP server. Each interface is a different network segment. Every interface is plugged into a different switch.
      Interface A: 192.168.0.254/24
      Interface B: 10.99.99.254/24
      Interface C: 10.219.1.254/24.

      DHCP servers A and B are working, they are handing out addresses and PCs are accepting them.

      DHCP server C tries to hand out addresses but the PC wont take them. I can see this in the DHCP log: DHCPDISCOVERY and DHCPOFFER is working but there is no DHCPACK! No matter which PC (Windows, Linux) I try to connect, i just wont take the offered address. Evene static IP wont help. I just cannot connect to the firewall.

      EDIT: If I try to plug one of the PCs which didnt get an IP from server C into a switch which is connected to server B: Boom, DHCP address!, Same on the switch which is connected to server A.

      What am I missing?
      Would you please help me in this case and point me in the right direction?

      Thank you very much!
      Greetings from Vienna!

      Kaiserfranzjosef

      S V 2 Replies Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @kaiserfranzjosef
        last edited by

        @kaiserfranzjosef is the subnet mask correct on the interface?

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        K 1 Reply Last reply Reply Quote 0
        • K
          kaiserfranzjosef @SteveITS
          last edited by kaiserfranzjosef

          @SteveITS

          Yes, its set to 255.255.255.0.

          I also tried to replace the switch but no luck.

          1 Reply Last reply Reply Quote 0
          • V
            viragomann @kaiserfranzjosef
            last edited by

            @kaiserfranzjosef said in One DHCP server is not working correctly:

            DHCP server C tries to hand out addresses but the PC wont take them. I can see this in the DHCP log: DHCPDISCOVERY and DHCPOFFER is working but there is no DHCPACK! No matter which PC (Windows, Linux) I try to connect, i just wont take the offered address. Evene static IP wont help. I just cannot connect to the firewall

            Would be interesting to see traffic of the whole DHCP session.
            Can you capture the DHCP traffic on interface C (ports 67, 68) and post the output here, please?

            K 1 Reply Last reply Reply Quote 0
            • K
              kaiserfranzjosef @viragomann
              last edited by kaiserfranzjosef

              @viragomann

              /usr/sbin/tcpdump -ni vtnet1 -c 1000 -U -w - '((port 67 and port 68)) and ((not vlan))'

              08:06:21.665582 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:06:22.670445 IP 10.219.1.254.67 > 10.219.1.100.68: UDP, length 300
08:06:27.765732 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:06:27.765867 IP 10.219.1.254.67 > 10.219.1.100.68: UDP, length 300
08:06:38.188561 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:06:38.188684 IP 10.219.1.254.67 > 10.219.1.100.68: UDP, length 300
08:06:51.940380 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:06:51.940470 IP 10.219.1.254.67 > 10.219.1.100.68: UDP, length 300
08:07:09.575816 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:07:09.575907 IP 10.219.1.254.67 > 10.219.1.100.68: UDP, length 300
08:07:11.930972 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:07:12.931743 IP 10.219.1.254.67 > 10.219.1.102.68: UDP, length 300
08:07:15.223590 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:07:15.223686 IP 10.219.1.254.67 > 10.219.1.102.68: UDP, length 300
08:07:24.162804 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:07:24.162900 IP 10.219.1.254.67 > 10.219.1.102.68: UDP, length 300
08:07:40.133377 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:07:40.133512 IP 10.219.1.254.67 > 10.219.1.102.68: UDP, length 300
08:08:13.142473 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:08:13.142560 IP 10.219.1.254.67 > 255.255.255.255.68: UDP, length 300
08:08:16.498816 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:08:16.498909 IP 10.219.1.254.67 > 255.255.255.255.68: UDP, length 300
08:08:23.946407 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:08:23.946482 IP 10.219.1.254.67 > 255.255.255.255.68: UDP, length 300
08:08:40.445228 IP 0.0.0.0.68 > 255.255.255.255.67: UDP, length 300
08:08:40.445357 IP 10.219.1.254.67 > 255.255.255.255.68: UDP, length 300

              The DHCP log looks like this:

              Nov 14 08:08:40 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:40 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:37 	dhclient 	92115 	Creating resolv.conf
Nov 14 08:08:37 	dhclient 	91824 	RENEW
Nov 14 08:08:23 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:23 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:16 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:16 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:13 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:08:13 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:47 	dhclient 	49312 	FAIL
Nov 14 08:07:40 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:40 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:35 	dhclient 	48393 	FAIL
Nov 14 08:07:34 	dhclient 	47953 	FAIL
Nov 14 08:07:34 	dhclient 	47411 	FAIL
Nov 14 08:07:31 	dhclient 	47091 	FAIL
Nov 14 08:07:24 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:24 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:15 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:15 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:12 	dhcpd 	20050 	DHCPOFFER on 10.219.1.102 to 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:11 	dhcpd 	20050 	DHCPDISCOVER from 54:ee:75:bc:44:d4 (Laptop-Tec05) via vtnet1
Nov 14 08:07:09 	dhcpd 	20050 	DHCPOFFER on 10.219.1.100 to 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:07:09 	dhcpd 	20050 	DHCPDISCOVER from 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:51 	dhcpd 	20050 	DHCPOFFER on 10.219.1.100 to 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:51 	dhcpd 	20050 	DHCPDISCOVER from 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:38 	dhcpd 	20050 	DHCPOFFER on 10.219.1.100 to 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:38 	dhcpd 	20050 	DHCPDISCOVER from 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:31 	dhclient 	2189 	FAIL
Nov 14 08:06:27 	dhcpd 	20050 	DHCPOFFER on 10.219.1.100 to 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:27 	dhcpd 	20050 	DHCPDISCOVER from 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:25 	dhclient 	1330 	Creating resolv.conf
Nov 14 08:06:25 	dhclient 	704 	RENEW
Nov 14 08:06:22 	dhcpd 	20050 	DHCPOFFER on 10.219.1.100 to 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
Nov 14 08:06:21 	dhcpd 	20050 	DHCPDISCOVER from 6c:62:6d:d2:26:c2 (nut-server) via vtnet1
              V 1 Reply Last reply Reply Quote 0
              • V
                viragomann @kaiserfranzjosef
                last edited by

                @kaiserfranzjosef
                If you capture with full details level you can see to the whole DHCP communication.
                My hope was to get here more than just DHCPDISCOVER und DHCPOFFER.

                K 1 Reply Last reply Reply Quote 0
                • K
                  kaiserfranzjosef @viragomann
                  last edited by

                  @viragomann

                  Sorry, missed that option. Here is the output with full view.

                  09:52:49.461224 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24162, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0x5c68d56c, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
09:52:50.461590 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5c68d56c, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
09:52:53.943418 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24163, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0x5c68d56c, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
09:52:53.943510 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5c68d56c, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
09:52:57.928232 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24164, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0x5c68d56c, secs 768, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
09:52:57.928368 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5c68d56c, secs 768, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
09:53:06.222604 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24165, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0x5c68d56c, secs 3072, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
09:53:06.222724 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0x5c68d56c, secs 3072, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
                  V 1 Reply Last reply Reply Quote 0
                  • V
                    viragomann @kaiserfranzjosef
                    last edited by

                    @kaiserfranzjosef
                    No idea, why the offer doesn't make the client happy. All values look plausible. Seems like it never gets it, since the client just sends a new discover.
                    Maybe you can sniff the traffic on the clients interface to get sure.

                    Is it the same if you connect the device to the pfSense interface directly?

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kaiserfranzjosef @viragomann
                      last edited by kaiserfranzjosef

                      @viragomann

                      This is the traffic when the client is connected directly to the pfsense interface:

                      12:40:52.281149 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24190, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0xb049fc35, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
12:40:52.281282 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0xb049fc35, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
12:40:56.489241 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24191, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0xb049fc35, secs 1024, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
12:40:56.489346 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0xb049fc35, secs 1024, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
12:41:04.459938 54:ee:75:bc:44:d4 > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x0, ttl 128, id 24192, offset 0, flags [none], proto UDP (17), length 328)
    0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 54:ee:75:bc:44:d4, length 300, xid 0xb049fc35, secs 3072, Flags [none] (0x0000)
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Discover
	    Client-ID Option 61, length 7: ether 54:ee:75:bc:44:d4
	    Hostname Option 12, length 12: "Laptop-Tec05"
	    Vendor-Class Option 60, length 8: "MSFT 5.0"
	    Parameter-Request Option 55, length 14: 
	      Subnet-Mask, Default-Gateway, Domain-Name-Server, Domain-Name
	      Router-Discovery, Static-Route, Vendor-Option, Netbios-Name-Server
	      Netbios-Node, Netbios-Scope, Option 119, Classless-Static-Route
	      Classless-Static-Route-Microsoft, Option 252
12:41:04.460023 ca:7d:67:06:40:f4 > 54:ee:75:bc:44:d4, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
    10.219.1.254.67 > 10.219.1.102.68: [udp sum ok] BOOTP/DHCP, Reply, length 300, xid 0xb049fc35, secs 3072, Flags [none] (0x0000)
	  Your-IP 10.219.1.102
	  Client-Ethernet-Address 54:ee:75:bc:44:d4
	  Vendor-rfc1048 Extensions
	    Magic Cookie 0x63825363
	    DHCP-Message Option 53, length 1: Offer
	    Server-ID Option 54, length 4: 10.219.1.254
	    Lease-Time Option 51, length 4: 86400
	    Subnet-Mask Option 1, length 4: 255.255.255.0
	    Default-Gateway Option 3, length 4: 10.219.1.254
	    Domain-Name-Server Option 6, length 4: 10.219.1.254
	    Domain-Name Option 15, length 12: "home.technik"
                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post
                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.