You are not logged in.

Pages: 1

#1 2012-03-29 00:11:55

battlepanic
Member
Registered: 2009-08-22
Posts: 76

Trouble with DHCP via dhcpcd & wireless

I need some help interpreting my router's logs.  I am trying to diagnose an issue where my computer is periodically dropping it's network connection for a minute or two.  I only notice this occurring once or twice a day.

  • My computer is assigned an IP address via DHCP.

  • My computer is connected wirelessly to a Linksys WRT54G router running the Tomato custom firmware.

  • The WAN port on the WRT54G is connected to a 2wire modem/router combo provided by my ISP.  I am really just using the 2wire as a modem.  To do this I turned on its "DMZplus" mode which assigns it's own WAN IP to the WRT54G via DHCP and then forwards all traffic to this address.

The logs recorded by iptables and dnsmasq are as follows.

Mar 27 19:00:01 tomato syslog.info root: -- MARK --
Mar 27 19:02:56 tomato user.warn kernel: DROP IN=vlan1 OUT= MAC=00:13:10:e9:8f:eb:64:0f:28:65:ec:89:08:00:45:00:01:4d SRC=59.132.122.110 DST=59.132.122.109 LEN=333 TOS=0x00 PREC=0x00 TTL=255 ID=31365 DF PROTO=UDP SPT=67 DPT=68 LEN=313
Mar 27 19:07:56 tomato user.warn kernel: DROP IN=vlan1 OUT= MAC=00:13:10:e9:8f:eb:64:0f:28:65:ec:89:08:00:45:00:01:4d SRC=59.132.122.110 DST=59.132.122.109 LEN=333 TOS=0x00 PREC=0x00 TTL=255 ID=57253 DF PROTO=UDP SPT=67 DPT=68 LEN=313
Mar 27 19:12:56 tomato user.warn kernel: DROP IN=vlan1 OUT= MAC=00:13:10:e9:8f:eb:64:0f:28:65:ec:89:08:00:45:00:01:4d SRC=59.132.122.110 DST=59.132.122.109 LEN=333 TOS=0x00 PREC=0x00 TTL=255 ID=61505 DF PROTO=UDP SPT=67 DPT=68 LEN=313
Mar 27 19:17:56 tomato user.warn kernel: DROP IN=vlan1 OUT= MAC=00:13:10:e9:8f:eb:64:0f:28:65:ec:89:08:00:45:00:01:4d SRC=59.132.122.110 DST=59.132.122.109 LEN=333 TOS=0x00 PREC=0x00 TTL=255 ID=4421 DF PROTO=UDP SPT=67 DPT=68 LEN=313
Mar 27 19:22:57 tomato user.warn kernel: DROP IN=vlan1 OUT= MAC=00:13:10:e9:8f:eb:64:0f:28:65:ec:89:08:00:45:00:01:4d SRC=59.132.122.110 DST=59.132.122.109 LEN=333 TOS=0x00 PREC=0x00 TTL=255 ID=46865 DF PROTO=UDP SPT=67 DPT=68 LEN=313
Mar 27 19:27:57 tomato user.warn kernel: DROP IN=vlan1 OUT= MAC=00:13:10:e9:8f:eb:64:0f:28:65:ec:89:08:00:45:00:01:4d SRC=59.132.122.110 DST=59.132.122.109 LEN=333 TOS=0x00 PREC=0x00 TTL=255 ID=48709 DF PROTO=UDP SPT=67 DPT=68 LEN=313
Mar 27 19:31:39 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:31:39 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:31:44 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:31:44 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:31:51 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:31:51 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:31:54 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:31:54 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:31:57 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:31:57 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:00 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:00 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:03 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:03 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:07 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:07 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:10 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:10 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:16 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:16 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:19 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:19 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:25 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:25 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:29 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:29 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:32 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:32 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:39 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:39 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator
Mar 27 19:32:43 tomato daemon.info dnsmasq-dhcp[13719]: DHCPREQUEST(br0) 192.168.1.2 00:13:ce:0b:92:66
Mar 27 19:32:43 tomato daemon.info dnsmasq-dhcp[13719]: DHCPACK(br0) 192.168.1.2 00:13:ce:0b:92:66 ordinator

The logs start by reporting that a packet is being dropped every five minutes.  The port numbers of 67, and 68 suggest that this is DHCP traffic.  I know that the 2wire in DMWplus mode assigns a 10 minute DHCP lease to the WRT54G.  After 5 minutes the WRT54G seems to be requesting a new lease.  These logs suggest that a response from the 2wire DHCP server is being blocked by the WRT54G firewall.  However, as far as I can tell, the lease on the router still seems to be getting renewed.  How could this be?

This section is followed by log entries made by dnsmasq.  It looks like my computer is repeatedly making some sort of request.  This lasts for about two minutes and corresponds with the period during which I have no network connection.  The problem eventually resolves itself on its own.

Are there any clues in here which might help explain why computer is periodically losing it's network connection?

Last edited by battlepanic (2012-04-06 16:21:04)

Offline

#2 2012-03-29 05:37:05

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: Trouble with DHCP via dhcpcd & wireless

The "DHCPREQUEST/DHCPACK" basically indicates that your client is constantly doing a dhcp request to the router during those 2 minutes. So the question here is, why is it doing that? Ideally, a packet capture (on the client side) when the actual issue occurs would help (see if the dhcp ack packet actually makes it to the client), but as the issue only occurs every so often; that's difficult to obtain obviously.

What's your setup like on the client side? Which wlan adapter are you using, dhcpcd or dhclient,...? Perhaps for testing purposes try setting a static ip (on the client) for a few days and see if the issue still occurs.

Burninate!

Offline

#3 2012-03-29 14:06:30

battlepanic
Member
Registered: 2009-08-22
Posts: 76

Re: Trouble with DHCP via dhcpcd & wireless

My wireless adapter is an Intel Pro Wireless 2200BG (ipw2200) and I'm using dhcpcd as my DHCP client software.

I used Wireshark to run a packet capture for a few hours, looking specifically at traffic on ports 67 and 68.  Sure enough, the problem eventually reoccurred and the capture indicates that the DHCPACK messages are indeed making it to my computer.  It's very strange that my computer is continuing to send DHCPREQUEST messages if it is receiving the DHCPACK messages from the server.  I can't seem to figure it out.

Come to think of it, I'm not even sure why my computer is sending DHCPREQUEST messages in the first place.  I've read that DHCP clients generally try to renew their lease at the midpoint of the current lease but it is not clear if this is the case here.  My router is currently configured to assign a 24 hour lease to clients.  This should mean that I would see a request for renewal every 12 hours or so.  Looking briefly at the logs in my router, I'm seeing DHCPREQUEST messages being sent more often than that.  I haven't rebooted my computer lately, so what else could be prompting my machine to send out these requests?

I'm including a sampling of the Wireshark capture data summary which shows what I'm seeing.

No.     Time            Source                Destination           Protocol Length Info
     10 22:41:41.975888 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x19f3efae
     11 22:41:41.987722 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x19f3efae
     12 22:41:45.095874 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0xbf40088a
     13 22:41:48.709296 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0xbf40088a
     14 22:41:48.720169 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0xbf40088a
     15 22:41:50.039260 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x9c113818
     16 22:41:50.050540 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x9c113818
     17 22:42:09.992583 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x18261f1e
     18 22:42:10.003921 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x18261f1e
     19 22:42:12.032582 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0xee8bc297
     20 22:42:12.046683 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0xee8bc297
     21 22:42:39.919221 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x4b52e0ea
     22 22:42:39.928820 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x4b52e0ea
     23 22:42:43.232599 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x717b56c4
     24 22:42:47.485947 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x717b56c4
     25 22:42:47.496625 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x717b56c4
     26 22:42:48.419245 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x6588ba3a
     27 22:42:48.429634 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x6588ba3a
     28 22:42:55.049215 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0xdc5a1da8
     29 22:42:55.059860 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0xdc5a1da8
     30 22:45:42.995854 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x8cfd947e
     31 22:45:46.680214 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x8cfd947e
     32 22:45:46.691023 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x8cfd947e
     33 22:49:05.742542 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x515dd491
     34 22:49:05.753346 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x515dd491
     35 22:49:34.662505 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x76a063ff
     36 22:49:39.164332 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0x76a063ff
     37 22:49:39.174583 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0x76a063ff
     38 22:50:07.892536 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0xd54379ca
     39 22:50:07.902135 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0xd54379ca
     40 22:50:13.169174 0.0.0.0               255.255.255.255       DHCP     376    DHCP Request  - Transaction ID 0xc61f1dbb
     41 22:50:13.206804 192.168.1.1           192.168.1.2           DHCP     349    DHCP ACK      - Transaction ID 0xc61f1dbb

Last edited by battlepanic (2012-04-06 16:19:48)

Offline

#4 2012-03-29 16:31:34

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: Trouble with DHCP via dhcpcd & wireless

Interesting. I was honestly expecting that the DHCPACK wasn't making it back to the client. There's 2 routes to investigate here as I see it:

1) Issue is related to signal loss/instability (driver, signal quality,...)
2) Issue is actually related to dhcp.

Would it be an option for you to test for a while without using dhcp (setting a static ip in other words). If the issue still occurs, we can at least rule out that dhcp has something to do with it.

Burninate!

Offline

#5 2012-03-29 17:25:49

battlepanic
Member
Registered: 2009-08-22
Posts: 76

Re: Trouble with DHCP via dhcpcd & wireless

During the outage, running the following command,

$ ip addr list

shows that no IP address is bound to the network adapter.

I have also wondered if this is due to signal loss on my wireless connection.  While this could explain the intial disconnection, but I doesn't easily explain the repeated DHCPREQUEST packets.  If the signal has dropped outl, then these packets can't be sent.  If the signal is restored and a new lease is requested, it really should only happen once.  Maybe if the signal is really flaking out and dropping in and out continuously, it might explain the repeated requests.  It's worth checking out, but I'm skeptical since the wireless signal only has to travel about 10 feet within the same room.  I want to set up some way to monitor wireless network connectivity and log any outages.  I might need some help in this area.  Do you have any experience setting up this kind of logging?

In the meantime, before switching to a static IP address, I'm going to stick with DHCP but I will now use the wired network adapater on my computer to see if the problem persists.  If so, I think we can safely assume it's not a problem with my wireless adapter.

Offline

#6 2012-03-29 17:56:53

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: Trouble with DHCP via dhcpcd & wireless

battlepanic wrote:

I want to set up some way to monitor wireless network connectivity and log any outages.  I might need some help in this area.  Do you have any experience setting up this kind of logging?

A fairly simple and straightforward tool for this would be Wavemon.

battlepanic wrote:

In the meantime, before switching to a static IP address, I'm going to stick with DHCP but I will now use the wired network adapater on my computer to see if the problem persists.  If so, I think we can safely assume it's not a problem with my wireless adapter.

Sounds like something worth trying.

Burninate!

Offline

#7 2012-04-06 16:17:58

battlepanic
Member
Registered: 2009-08-22
Posts: 76

Re: Trouble with DHCP via dhcpcd & wireless

So, I did some more testing and here is what I've found.

  • Running the wired network adapter with DHCP via dhcpcd works.

  • Running Arch on a different computer with a different wireless adapter and dhcpcd works.

  • Running a fresh Arch installation on the problem computer with wireless and dhcpcd does not work.

  • Switching the DHCP client from dhcpcd to dhclient works.

This is leading me to believe that the problem is perhaps the combination of dhcpcd and my wireless adapater (ipw2200).  The next step is to revert to my original configuration and figure out how to get dhcpcd to log it's activity.  Hopefully this will provide some clues as to why I'm losing my IP address.

Offline

#8 2012-04-07 03:35:10

battlepanic
Member
Registered: 2009-08-22
Posts: 76

Re: Trouble with DHCP via dhcpcd & wireless

I've invoked dhcpcd with the --debug option and I am posting what I'm seeing in the logs during the outage.

This is with the Intel Pro/Wireless 2200BG (ipw2200) network adapter and I'm only noticing connection issues when using dhcpcd.  Can anyone make sense of this?

Apr  6 20:43:51 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:43:51 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:43:51 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:43:51 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:43:51 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x3482967e), next in 4.89 seconds
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:43:52 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.48 seconds
Apr  6 20:43:53 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.66 seconds
Apr  6 20:43:55 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:43:57 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:43:59 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:44:03 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x5323bd70), next in 3.95 seconds
Apr  6 20:44:07 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x5323bd70), next in 7.98 seconds
Apr  6 20:44:07 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:44:07 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:44:07 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.98 seconds
Apr  6 20:44:09 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.38 seconds
Apr  6 20:44:11 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:44:13 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:44:15 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x654ed834), next in 4.47 seconds
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:45:07 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.76 seconds
Apr  6 20:45:09 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.16 seconds
Apr  6 20:45:10 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:45:12 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:45:14 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:45:26 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:45:26 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:45:26 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:45:26 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:45:26 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0xe6bf9905), next in 3.72 seconds
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:45:27 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.61 seconds
Apr  6 20:45:28 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.87 seconds
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x47ecf543), next in 3.77 seconds
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:45:30 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.24 seconds
Apr  6 20:45:31 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.89 seconds
Apr  6 20:45:33 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:45:35 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:45:37 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:45:42 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:45:42 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:45:42 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:45:42 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:45:42 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x3ee9a938), next in 4.25 seconds
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:45:43 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.94 seconds
Apr  6 20:45:45 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.71 seconds
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0xb3e147f1), next in 3.24 seconds
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:45:46 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.88 seconds
Apr  6 20:45:48 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:45:48 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x1c76ce5e), next in 4.61 seconds
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:45:49 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.65 seconds
Apr  6 20:45:51 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.55 seconds
Apr  6 20:45:52 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:45:54 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:45:54 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:45:54 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:45:54 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:45:54 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:45:54 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:45:55 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:45:57 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x72a5967), next in 4.19 seconds
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:46:03 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.58 seconds
Apr  6 20:46:05 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.97 seconds
Apr  6 20:46:06 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:46:06 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x2350bd03), next in 3.28 seconds
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:46:07 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.41 seconds
Apr  6 20:46:08 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.02 seconds
Apr  6 20:46:09 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:46:11 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:12 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:46:12 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x8352a9c8), next in 3.33 seconds
Apr  6 20:46:12 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:46:12 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:46:12 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.07 seconds
Apr  6 20:46:13 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.21 seconds
Apr  6 20:46:14 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:46:16 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:46:18 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x72ad4c51), next in 4.43 seconds
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:46:39 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.23 seconds
Apr  6 20:46:40 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.68 seconds
Apr  6 20:46:42 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:46:44 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:46:46 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: carrier lost
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: deleting default route via 192.168.1.1
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: deleting route to 192.168.1.0/24
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: deleting IP address 192.168.1.2/24
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason NOCARRIER
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: carrier acquired
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: using hwaddr 00:13:ce:0b:92:66
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: not configured to accept IPv6 RAs
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: rebinding lease of 192.168.1.2
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: sending REQUEST (xid 0x10c80508), next in 4.58 seconds
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: acknowledged 192.168.1.2 from 192.168.1.1
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: checking for 192.168.1.2
Apr  6 20:47:38 localhost dhcpcd[5818]: eth1: sending ARP probe (1 of 3), next in 1.29 seconds
Apr  6 20:47:40 localhost dhcpcd[5818]: eth1: sending ARP probe (2 of 3), next in 1.70 seconds
Apr  6 20:47:41 localhost dhcpcd[5818]: eth1: sending ARP probe (3 of 3), next in 2.00 seconds
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: leased 192.168.1.2 for 86400 seconds
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: adding IP address 192.168.1.2/24
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: adding route to 192.168.1.0/24
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: adding default route via 192.168.1.1
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: writing lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason BOUND
Apr  6 20:47:43 localhost dhcpcd[5818]: eth1: sending ARP announce (1 of 2), next in 2.00 seconds
Apr  6 20:47:45 localhost dhcpcd[5818]: eth1: sending ARP announce (2 of 2)

Offline

#9 2012-04-07 06:46:43

Gcool
Member
Registered: 2011-08-16
Posts: 1,456

Re: Trouble with DHCP via dhcpcd & wireless

It seems to be dropping the carrier all the time there. While I don't really have a direct explanation of why it's doing that; perhaps try using a netcfg profile in which you can set/increase the "CARRIER_TIMEOUT" value and see what that gives as a result.

Burninate!

Offline

Pages: 1

Board footer

Powered by FluxBB