Comment 4 for bug 1521618

Revision history for this message
Zoltan Arnold Nagy (zoltan) wrote : Re: wrong subnet in DHCP answer when multiple networks are present

I will be able to do the tcpdumps a bit later; in the meantime, here are the requested outputs:

root@maas:~# ip addr list; ip route list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:bf:29:c4 brd ff:ff:ff:ff:ff:ff
    inet 9.4.113.251/24 brd 9.4.113.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:febf:29c4/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:bf:a4:48 brd ff:ff:ff:ff:ff:ff
    inet 10.6.250.250/16 brd 10.6.255.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:febf:a448/64 scope link
       valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:50:56:bf:f1:71 brd ff:ff:ff:ff:ff:ff
    inet 10.7.250.250/16 brd 10.7.255.255 scope global eth2
       valid_lft forever preferred_lft forever
    inet6 fe80::250:56ff:febf:f171/64 scope link
       valid_lft forever preferred_lft forever
default via 9.4.113.254 dev eth0
9.4.113.0/24 dev eth0 proto kernel scope link src 9.4.113.251
10.6.0.0/16 dev eth1 proto kernel scope link src 10.6.250.250
10.7.0.0/16 dev eth2 proto kernel scope link src 10.7.250.250
root@maas:~#