Modify

Opened 6 years ago

Closed 6 years ago

Last modified 4 years ago

#10479 closed defect (no_response)

Wired network is not accessible after a few hours

Reported by: Barosl LEE <yuki@…> Owned by: developers
Priority: response-needed Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: wired Cc:

Description

I installed trunk 2 days ago. And the wired network of my router, DIR-615, is disabled a few hours after booting. On the first day, it stopped after 4-5 hours. I found it today and rebooted the router. 14 hours later, the same problem occurred.

While disabled, I can still access the Internet using the wireless network. I can also see the router from the WAN.

Here is the log:

Nov 22 21:46:07 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:07 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:08 miki kern.info kernel: eth0: link down
Nov 22 21:46:08 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:08 miki kern.info kernel: eth0: link up (1000Mbps/Full duplex)
Nov 22 21:46:08 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:08 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:09 miki kern.info kernel: eth0: link down
Nov 22 21:46:09 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:09 miki kern.info kernel: eth0: link up (1000Mbps/Full duplex)
Nov 22 21:46:09 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:09 miki kern.info kernel: br-lan: port 1(eth0) entering forwarding state
Nov 22 21:46:09 miki kern.info kernel: eth0: link down
Nov 22 21:46:10 miki kern.info kernel: eth0: link up (1000Mbps/Full duplex)
Nov 22 21:46:10 miki kern.info kernel: eth0: link down
Nov 22 21:46:10 miki kern.info kernel: eth0: link up (1000Mbps/Full duplex)
Nov 22 21:46:10 miki kern.info kernel: eth0: link down
Nov 22 21:46:11 miki kern.info kernel: eth0: link up (1000Mbps/Full duplex)
Nov 22 21:46:11 miki kern.info kernel: eth0: link down
Nov 22 21:46:12 miki kern.info kernel: eth0: link up (1000Mbps/Full duplex)

And the same messages continue.

Attachments (0)

Change History (8)

comment:1 Changed 6 years ago by Barosl LEE <yuki@…>

I found that typing "ifconfig eth0 down && ifconfig eth0 up" on the router makes the wired interface usable again. I don't see something special in the syslog, just a dhcp request message and a dhcp ack message are there.

comment:2 follow-up: Changed 6 years ago by matt@…

I'm seeing something similar, though I don't have a wired network so I can't confirm that I'm seeing the exact same issue.

However, one of my two wireless networks shows this issue. After a period of time (seeingly random), one of the two networks (always the 802.11g, never the 802.11n network) disconnects. This doesn't seem to be a client issue, as I'm seeing it on two of my 802.11g devices. Again, the 802.11n device is fine.

I don't see anything odd in the log, though I can confirm that bringing down the interface, then bringing it back up solves this issue.

Note that the wireless clients connect, but nothing passes through the interface. So, the handshake is performed fine, but DHCP (and stateless IPv6) do not work.

comment:3 in reply to: ↑ 2 Changed 6 years ago by anonymous

Replying to matt@…:

I'm seeing something similar, though I don't have a wired network so I can't confirm that I'm seeing the exact same issue.

However, one of my two wireless networks shows this issue. After a period of time (seeingly random), one of the two networks (always the 802.11g, never the 802.11n network) disconnects. This doesn't seem to be a client issue, as I'm seeing it on two of my 802.11g devices. Again, the 802.11n device is fine.

I don't see anything odd in the log, though I can confirm that bringing down the interface, then bringing it back up solves this issue.

Note that the wireless clients connect, but nothing passes through the interface. So, the handshake is performed fine, but DHCP (and stateless IPv6) do not work.

Also, seeing this on Blackfire RC6, not trunk.

comment:4 Changed 6 years ago by jogo

Which DIR-615 revision is this, C (with ar9130) or E (with ar7240)?

comment:5 Changed 6 years ago by Barosl LEE <yuki@…>

I'm using DIR-615 revision E4, with the firmware for DIR-600 revision A1. And the current revision is r29274.

comment:6 Changed 6 years ago by nbd

  • Priority changed from high to response-needed

does this issue still show up on current trunk?

comment:7 Changed 6 years ago by nbd

  • Resolution set to no_response
  • Status changed from new to closed

comment:8 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.