On Sun, Jul 13, 2014 at 10:11 AM, Björn Ketelaars <
bjorn.ketela...@hydroxide.nl> wrote:

> It sounds like that your default inet route is overwritten after dhclient
> on vlan1 is issued.


That's not something I'd expect, given that the dhclient instances should
be in separate routing domains.



> Did you have a look at the route table before and after each call of
> dhclient?
>

That was my initial suspicion and one of my reasons for trying to separate
things into rdomain 1.

I logged routing tables every second or so while manually running dhclient
for vlan1 (instead of via hostname.if).

Before:

# netstat -T0 -nrfinet
Internet:
Destination        Gateway            Flags   Refs      Use   Mtu  Prio
Iface
default            84.245.29.1        UGS        7  1871091     -     8
vlan0
84.245.29/24       link#5             UC         1        0     -     4
vlan0
84.245.29.1        00:30:88:16:ac:fd  UHLc       1        0     -     4
vlan0
127/8              127.0.0.1          UGRS       0        0 33144     8
lo0
127.0.0.1          127.0.0.1          UH         2    29313 33144     4
lo0
192.168.1.2        00:25:90:33:12:65  UHLc       0       16     -     4
lo0
224/4              127.0.0.1          URS        0        0 33144     8
lo0

# netstat -T1 -nrfinet
Internet:
Destination        Gateway            Flags   Refs      Use   Mtu  Prio
Iface
10.0.52/24         link#15            UC         0        0     -     4
vlan52


# route -T1 exec /sbin/dhclient vlan1

Gives me an IP on vlan1 and routes in rdomain 1, but kills connectivity on
vlan0 after the first DHCPREQUEST goes out on vlan1.


# ps ax | grep dhclient | grep -v grep
23596 ??  Is      0:00.02 dhclient: vlan0 [priv] (dhclient)
27697 ??  Is      0:00.48 dhclient: vlan0 (dhclient)
12813 ??  Ss      0:00.00 dhclient: vlan1 [priv] (dhclient)
10342 p7  Z+      0:00.00 (dhclient)
 7017 p7  S+      0:00.01 dhclient: vlan1 (dhclient)

Note the zombie dhclient in between. I don't know why it's there. A few
seconds later, vlan1 appears to have its address and - I assume - the
zombie is reaped.

# ps ax | grep dhclient | grep -v grep
23596 ??  Is      0:00.02 dhclient: vlan0 [priv] (dhclient)
27697 ??  Is      0:00.48 dhclient: vlan0 (dhclient)
12813 ??  Ss      0:00.01 dhclient: vlan1 [priv] (dhclient)
19415 ??  Ss      0:00.00 dhclient: vlan1 (dhclient)

# netstat -T0 -nrfinet
Internet:
Destination        Gateway            Flags   Refs      Use   Mtu  Prio
Iface
default            84.245.29.1        UGS        7  1871093     -     8
vlan0
84.245.29/24       link#5             UC         1        0     -     4
vlan0
84.245.29.1        00:30:88:16:ac:fd  UHLc       1        0     -     4
vlan0
127/8              127.0.0.1          UGRS       0        0 33144     8
lo0
127.0.0.1          127.0.0.1          UH         2    29313 33144     4
lo0
192.168.1/24       link#2             UC         1        0     -     4
em1
192.168.1.2        00:25:90:33:12:65  UHLc       0       16     -     4
lo0
224/4              127.0.0.1          URS        0        0 33144     8
lo0

# netstat -T1 -nrfinet
Internet:
Destination        Gateway            Flags   Refs      Use   Mtu  Prio
Iface
default            10.10.12.1         UGS        0        0     -     8
vlan1
10.0.52/24         link#15            UC         0        0     -     4
vlan52
10.10.12/22        link#16            UC         1        0     -     4
vlan1
10.10.12.1         link#16            UHLc       1        0     -     4
vlan1


Forgive me for removing the "Routing tables" line from the netstat output.

Only after killing all dhclients and re-running dhclient vlan0, I get my
internet connectivity back.

Regards,

Rogier

Reply via email to