Filing this again since I do not see it in the list archive from yesterday. Not sure where it went... Apologies if duplicated somewhere.
I am having issues with TFTP booting. DHCP reservation works fine, packets show next-server (Server-IP) and filename (file) being sent correctly:
09:35:46.597484 d0:67:e5:99:49:9a > 00:50:56:b0:2d:6c, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 17, id 26679, offset 0, flags [none], proto UDP (17), length 576)
172.23.41.127.bootpc > 172.22.129.101.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:50:56:a4:13:6d, length 548, hops 1, xid 0x57a4136d, secs 4, Flags [Broadcast] (0x8000)
Gateway-IP 172.23.41.127
Client-Ethernet-Address 00:50:56:a4:13:6d
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Request
Requested-IP Option 50, length 4: 172.23.41.91
Parameter-Request Option 55, length 24:
Subnet-Mask, Time-Zone, Default-Gateway, IEN-Name-Server
Domain-Name-Server, RL, Hostname, BS
Domain-Name, SS, RP, EP
Vendor-Option, Server-ID, Vendor-Class, BF
Option 128, Option 129, Option 130, Option 131
Option 132, Option 133, Option 134, Option 135
MSZ Option 57, length 2: 1260
Server-ID Option 54, length 4: 172.22.129.101
GUID Option 97, length 17: 0.66.36.89.8.124.188.159.93.239.28.84.34.11.193.72.120
ARCH Option 93, length 2: 0
NDI Option 94, length 3: 1.2.1
Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
END Option 255, length 0
PAD Option 0, length 0, occurs 200
09:35:46.597557 00:50:56:b0:2d:6c > d0:67:e5:99:49:9a, ethertype IPv4 (0x0800), length 359: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 345)
172.22.129.101.bootps > 172.23.41.124.bootps: [bad udp cksum 26c8!] BOOTP/DHCP, Reply, length 317, hops 1, xid 0x57a4136d, secs 4, Flags [Broadcast] (0x8000)
Your-IP 172.23.41.91
Server-IP 172.22.129.101
Gateway-IP 172.23.41.124
Client-Ethernet-Address 00:50:56:a4:13:6d
file "pxelinux.0"
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: ACK
Server-ID Option 54, length 4: 172.22.129.101
Lease-Time Option 51, length 4: 43200
Subnet-Mask Option 1, length 4: 255.255.255.0
Default-Gateway Option 3, length 4: 172.23.41.1
Domain-Name-Server Option 6, length 8: 172.20.0.111,172.20.0.112
Hostname Option 12, length 22: "pxetftp2.lab.beer.town"
Domain-Name Option 15, length 13: "lab.beer.town"
END Option 255, length 0
However, the Gateway-IP is incorrect. It should be 172.23.41.1. and (I think) because of this, the server never makes it to the TFTP server.
dhcpd.conf:
# dhcpd.conf
interfaces="eth0";
ping-check true;
option domain-name "lab.beer.town";
option domain-name-servers 172.20.0.111, 172.20.0.112;
option ntp-servers 172.22.82.100;
omapi-port 7911;
key omapi_key {
algorithm HMAC-MD5;
secret ""; #<-The output from the generated key above.
}
omapi-key omapi_key;
default-lease-time 43200;
max-lease-time 86400;
ddns-update-style none;
allow booting;
allow bootp;
authoritative;
log-facility local7;
include "/etc/dhcp/dhcpd.hosts";
#################################
# lab.beer.town
#################################
subnet 172.22.129.0 netmask 255.255.255.0 {
range 172.22.129.101 172.22.129.101;
option subnet-mask 255.255.255.0;
option routers 172.22.128.1;
next-server 172.23.129.101;
filename "pxelinux.0";
}
subnet 172.23.41.0 netmask 255.255.255.0 {
range 172.23.41.2 172.23.41.254;
option subnet-mask 255.255.255.0;
option routers 172.23.41.1;
next-server 172.23.41.101;
filename "pxelinx.0";
}
What am I doing wrong that the vm is picking up the gateway as the routers IP? Yes the request is coming from that router, but why isnt it sending back the correct gateway-ip ?
--
Jeff
Locked
