So after some tests I figure out that dnsmasq might be the one that is causing the problem. I've read the boot log from other posts and it seems like DHCP request was sent but no response sent to client for some reason. If I manually set the network IP via CLIENT_IP in bootloader I can get the device boot from network without issue.
The only difference I can think of is I'm using the dnsmasq instance running on docker container in my server. I've use --privileged flag and --net host option in my server but the issue still persists.
Can somebody help me on this?
Edit: Add in tcpdump output from eth0. It repeat Discover and Offer request twice then it move on.
The only difference I can think of is I'm using the dnsmasq instance running on docker container in my server. I've use --privileged flag and --net host option in my server but the issue still persists.
Can somebody help me on this?
Edit: Add in tcpdump output from eth0. It repeat Discover and Offer request twice then it move on.
Code:
00:56:57.164863 IP (tos 0x0, ttl 64, id 20588, offset 0, flags [none], proto UDP (17), length 350) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:1f:02:a5 (oui Unknown), length 322, xid 0x74aa6dd7, Flags [none] Client-Ethernet-Address e4:5f:01:1f:02:a5 (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: Discover Parameter-Request (55), length 14: Subnet-Mask (1), Default-Gateway (3), Vendor-Option (43), Vendor-Class (60) TFTP (66), BF (67), Unknown (128), Unknown (129) Unknown (130), Unknown (131), Unknown (132), Unknown (133) Unknown (134), Unknown (135) Vendor-Class (60), length 32: "PXEClient:Arch:00000:UNDI:002001" ARCH (93), length 2: 0 NDI (94), length 3: 1.2.1 GUID (97), length 17: 0.52.105.80.82.20.49.176.0.1.31.2.165.112.94.174.6800:56:57.166106 IP (tos 0xc0, ttl 64, id 23126, offset 0, flags [none], proto UDP (17), length 342) 192.168.25.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314, xid 0x74aa6dd7, Flags [Broadcast] Client-Ethernet-Address e4:5f:01:1f:02:a5 (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: Offer Server-ID (54), length 4: 192.168.25.1 Vendor-Class (60), length 9: "PXEClient" GUID (97), length 17: 0.52.105.80.82.20.49.176.0.1.31.2.165.112.94.174.68 Vendor-Option (43), length 32: 6.1.3.10.4.0.80.88.69.9.20.0.0.17.82.97.115.112.98.101.114.114.121.32.80.105.32.66.111.111.116.25500:57:13.164692 IP (tos 0x0, ttl 64, id 20590, offset 0, flags [none], proto UDP (17), length 350) 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from e4:5f:01:1f:02:a5 (oui Unknown), length 322, xid 0x74aa6dd7, Flags [none] Client-Ethernet-Address e4:5f:01:1f:02:a5 (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: Discover Parameter-Request (55), length 14: Subnet-Mask (1), Default-Gateway (3), Vendor-Option (43), Vendor-Class (60) TFTP (66), BF (67), Unknown (128), Unknown (129) Unknown (130), Unknown (131), Unknown (132), Unknown (133) Unknown (134), Unknown (135) Vendor-Class (60), length 32: "PXEClient:Arch:00000:UNDI:002001" ARCH (93), length 2: 0 NDI (94), length 3: 1.2.1 GUID (97), length 17: 0.52.105.80.82.20.49.176.0.1.31.2.165.112.94.174.6800:57:13.166533 IP (tos 0xc0, ttl 64, id 25647, offset 0, flags [none], proto UDP (17), length 342) 192.168.25.1.bootps > 255.255.255.255.bootpc: BOOTP/DHCP, Reply, length 314, xid 0x74aa6dd7, Flags [Broadcast] Client-Ethernet-Address e4:5f:01:1f:02:a5 (oui Unknown) Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message (53), length 1: Offer Server-ID (54), length 4: 192.168.25.1 Vendor-Class (60), length 9: "PXEClient" GUID (97), length 17: 0.52.105.80.82.20.49.176.0.1.31.2.165.112.94.174.68 Vendor-Option (43), length 32: 6.1.3.10.4.0.80.88.69.9.20.0.0.17.82.97.115.112.98.101.114.114.121.32.80.105.32.66.111.111.116.255Statistics: Posted by rasp14 — Fri Mar 22, 2024 1:30 am