>> [root@netops-adm-1 ~]# ip addr show
>> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 scope host lo
>> inet6 ::1/128 scope host
>> valid_lft forever preferred_lft forever
>> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
>> 1000
>> link/ether 00:21:9b:a6:6e:24 brd ff:ff:ff:ff:ff:ff
>> inet 172.20.1.116/29 brd 172.20.1.119 scope global eth0
>> inet 172.20.1.117/29 brd 172.20.1.119 scope global secondary eth0:1
>> inet6 fe80::221:9bff:fea6:6e24/64 scope link
>> valid_lft forever preferred_lft forever
>> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>> link/ether 00:21:9b:a6:6e:26 brd ff:ff:ff:ff:ff:ff
>> 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>> link/ether 00:21:9b:a6:6e:28 brd ff:ff:ff:ff:ff:ff
>> 5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>> link/ether 00:21:9b:a6:6e:2a brd ff:ff:ff:ff:ff:ff
>> 6: sit0: <NOARP> mtu 1480 qdisc noop
>> link/sit 0.0.0.0 brd 0.0.0.0
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> This looks suspicious: I'm not sure if the lack of the /<netmask-bits>
> part of the address means that the netmask is all-ones or all-zeros, but
> if it's all zeros that could really mess things up.
>
> Are you using the sit0 interface, and is its current state deliberate?
>
> The existence of an interface with address 0.0.0.0 and netmask 0.0.0.0
> is pretty unusual and may well give exactly the symptoms you're seeing.
> Not that if you can remove that interface, you'll need to restart
> dnsmasq to end its confusion.
>
OK, sit0 the ipv4 -> ipv6 tunnel interface, which I am not using (sorry ARIN).
You can remove it by:
[root@netops-adm-1 ~]# grep IPV6 /etc/sysconfig/network
NETWORKING_IPV6=no
# touch /etc/modprobe.d/disable-ipv6.conf
# echo "options ipv6 disable=1" >> /etc/modprobe.d/disable-ipv6.conf
... and rebooting (in a pinch for the lazy).
So, post reboot, the interfaces look like:
[root@netops-adm-1 ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:21:9b:a6:6e:24 brd ff:ff:ff:ff:ff:ff
inet 172.20.1.116/29 brd 172.20.1.119 scope global eth0
inet 172.20.1.117/29 brd 172.20.1.119 scope global secondary eth0:1
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:21:9b:a6:6e:26 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:21:9b:a6:6e:28 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:21:9b:a6:6e:2a brd ff:ff:ff:ff:ff:ff
Unfortunately, we are still offering nulls for the server identifier:
dnsmasq-dhcp: 764422230 available DHCP range: 10.32.206.144 -- 10.32.206.190
dnsmasq-dhcp: 764422230 DHCPREQUEST(eth0) 10.32.206.153 f0:4d:a2:02:5a:ca
dnsmasq-dhcp: 764422230 DHCPACK(eth0) 10.32.206.153 f0:4d:a2:02:5a:ca
netboot-GCHVKN1
dnsmasq-dhcp: 764422230 requested options: 1:netmask, 28:broadcast,
2:time-offset, 3:router,
dnsmasq-dhcp: 764422230 requested options: 15:domain-name, 6:dns-server,
12:hostname,
dnsmasq-dhcp: 764422230 requested options: 40:nis-domain, 41:nis-server,
42:ntp-server
dnsmasq-dhcp: 764422230 tags: 10.32.206.128-nettag, GCHVKN1-eth0, known, eth0
dnsmasq-dhcp: 764422230 bootfile name: discovery/pxelinux.0
dnsmasq-dhcp: 764422230 server name: ks.sec.zynga.com
dnsmasq-dhcp: 764422230 next server: 172.20.1.116
dnsmasq-dhcp: 764422230 sent size: 1 option: 53:message-type 05
dnsmasq-dhcp: 764422230 sent size: 4 option: 54:server-identifier 0.0.0.0
dnsmasq-dhcp: 764422230 sent size: 4 option: 51:lease-time 00:03:f4:80
dnsmasq-dhcp: 764422230 sent size: 4 option: 58:T1 00:01:d0:28
dnsmasq-dhcp: 764422230 sent size: 4 option: 59:T2 00:03:4b:d8
dnsmasq-dhcp: 764422230 sent size: 4 option: 1:netmask 255.255.255.128
dnsmasq-dhcp: 764422230 sent size: 15 option: 12:hostname netboot-GCHVKN1
dnsmasq-dhcp: 764422230 sent size: 4 option: 3:router 10.32.206.129
dnsmasq-dhcp: 764422230 sent size: 8 option: 42:ntp-server 172.20.1.116,
172.20.1.124
dnsmasq-dhcp: 764422230 sent size: 8 option: 6:dns-server 172.20.1.117,
172.20.1.125
dnsmasq-dhcp: 764422230 sent size: 13 option: 15:domain-name sec.zynga.com
- I tried a quick update to 2.57, which had no effect.
- I tried dropping the eth0:1 interface, which also had no effect.
Any possibility this is an effect of the goofy network I am in? Or some
corruption from the relay?
Here is the dhcpdump of a sample request (not the same as the above):
---------------------------------------------------------------------------
TIME: 16:53:48.651085
IP: > (00:01:e8:76:31:4a) > (00:21:9b:a6:6e:24)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 907bce3f
SECS: 65535
FLAGS: 0
CIADDR: 10.32.165.147
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: f0:4d:a2:01:62:9f:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST)
OPTION: 55 ( 10) Parameter Request List 1 (Subnet mask)
28 (Broadcast address)
2 (Time offset)
3 (Routers)
15 (Domainname)
6 (DNS server)
12 (Host name)
40 (NIS domain)
41 (NIS servers)
42 (NTP servers)
---------------------------------------------------------------------------
TIME: 16:53:48.686584
IP: > (00:21:9b:a6:6e:24) > (00:00:5e:00:01:29)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 907bce3f
SECS: 65535
FLAGS: 0
CIADDR: 10.32.165.147
YIADDR: 10.32.165.147
SIADDR: 172.20.1.116
GIADDR: 0.0.0.0
CHADDR: f0:4d:a2:01:62:9f:00:00:00:00:00:00:00:00:00:00
SNAME: ks.sec.zynga.com.
FNAME: discovery/pxelinux.0.
OPTION: 53 ( 1) DHCP message type 5 (DHCPACK)
OPTION: 54 ( 4) Server identifier 0.0.0.0
OPTION: 51 ( 4) IP address leasetime 259200 (3d)
OPTION: 58 ( 4) T1 129466 (1d11h57m46s)
OPTION: 59 ( 4) T2 226666 (2d14h57m46s)
OPTION: 1 ( 4) Subnet mask 255.255.255.128
OPTION: 12 ( 15) Host name netboot-GDNVKN1
OPTION: 3 ( 4) Routers 10.32.165.129
OPTION: 42 ( 8) NTP servers 172.20.1.116,172.20.1.124
OPTION: 6 ( 8) DNS server 172.20.1.117,172.20.1.125
OPTION: 15 ( 13) Domainname sec.zynga.com
---------------------------------------------------------------------------
TIME: 16:53:48.712433
IP: > (00:21:9b:a6:6e:24) > (00:00:5e:00:01:29)
OP: 2 (BOOTPREPLY)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 1
XID: 907bce3f
SECS: 65535
FLAGS: 0
CIADDR: 10.32.165.147
YIADDR: 10.32.165.147
SIADDR: 172.20.1.116
GIADDR: 0.0.0.0
CHADDR: f0:4d:a2:01:62:9f:00:00:00:00:00:00:00:00:00:00
SNAME: ks.sec.zynga.com.
FNAME: discovery/pxelinux.0.
OPTION: 53 ( 1) DHCP message type 5 (DHCPACK)
OPTION: 54 ( 4) Server identifier 0.0.0.0
OPTION: 51 ( 4) IP address leasetime 259200 (3d)
OPTION: 58 ( 4) T1 118365 (1d8h52m45s)
OPTION: 59 ( 4) T2 215565 (2d11h52m45s)
OPTION: 1 ( 4) Subnet mask 255.255.255.128
OPTION: 12 ( 15) Host name netboot-GDNVKN1
OPTION: 3 ( 4) Routers 10.32.165.129
OPTION: 42 ( 8) NTP servers 172.20.1.116,172.20.1.124
OPTION: 6 ( 8) DNS server 172.20.1.117,172.20.1.125
OPTION: 15 ( 13) Domainname sec.zynga.com
---------------------------------------------------------------------------
-Mike
>>
>> I should mention at this point that the configuration has grown rather large:
>>
>> [root@netops-adm-1 ~]# egrep -v '^#|^$' /etc/dnsmasq.conf | wc
>> 12515 12530 1013088
>> [root@netops-adm-1 ~]# grep dhcp-host /etc/dnsmasq.conf | wc
>> 5735 5951 514853
>>
> Nice to see that it keeps going at those sizes: there shouldn't be any
> problems just because of the size of the config.
>
>
> Simon.
>
>
>> -Mike
>
