Modify

Opened 8 years ago

Closed 7 years ago

#7118 closed defect (no_response)

backfire 10.03 fail-safe mode is broken - eth0 Interface is down

Reported by: Chris Martin <chris@…> Owned by: developers
Priority: response-needed Milestone: Backfire 10.03.1
Component: packages Version: Trunk
Keywords: Cc:

Description

When entering fail-safe the router doesn't have an IP address.
In-fact the network interface eth0 device has not been initialised.

I have a serial console so I can see the log

The last line from the log is

- failsafe -
b44: eth0: powering down PHY

If I issue

ifconfig eth0 up 192.168.1.1/24 

The interface then comes up OK.

Attachments (0)

Change History (11)

comment:1 Changed 8 years ago by jow

Which architecture? brcm-2.4, brcm47xx, brcm63xx ?

comment:2 Changed 8 years ago by Chris Martin <chris@…>

I was just looking at pre-init realised that there was an architecture component.
I was testing brcm47xx and brcm-2.4 - The problem occurs on both

comment:3 Changed 8 years ago by Chris Martin <chris@…>

I also noticed that if I enter failsafe via the console. That I am no longer able to mount the filesystems using the "mount_root" command.

The command completes without error, but nothing happens

comment:4 Changed 8 years ago by nico

Can you confirm you're still experiencing this issue after [20838] ?

comment:5 Changed 8 years ago by Chris Martin <chris@…>

I have just tested with 20872 with a brcm47xx image.
If I try and enter failsafe via the console [ f enter ], the interface is not configured.
If I use the reset button, it is ignored and will not go to failsafe - this is different to my ealier experience, where it would recognise the button, but the interface is not configured.
HOWEVER: I did use a different router. Originally, I was using a Linksys WRT54GS. This time I am using an ASUS WL500Pv2.

BUT... the mount_root issue is resolved .. That is working

So I think that there are 2 outstanding issues
(1) The interface is not configured in failsafe.
(2) The reset button on the WL500Pv2 is not recognised to enter failsafe

comment:6 Changed 8 years ago by cshore@…

1.1) Is eth0 your lan or your wan. The lan is the one for failsafe for security reasons (you don't *really* want world telnet access to your router do you?)
1.2) Does this arch define the interface to use for failsafe, or do you need to specify it under Image Options|Preinit Options in the buildroot?

comment:7 Changed 8 years ago by Chris Martin <chris@…>

eth0 is the primary interface. The others are Vlans
But the switch was not configured either so I had to use the eth0 device not eth0.1
So the CPU was an untagged interface (access port) on the switch. (the default config of the broadcom switch).

Mmmm I havn't looked in the Image configuration for a while.... I didn't set anything.
I will have a look and do a couple of builds and report back

comment:8 Changed 8 years ago by romain.riviere@…

I'd like to confirm this on stock 10.03 and (up to) r21408. The modules are loaded, but eth0 is not configured. Tested on a WRT54GL v1.1

comment:9 follow-up: Changed 8 years ago by Romain Riviere <romain.riviere@…>

Just a heads-up, I believe this issue should be fixed by cshore's commit in trunk r21417 :-)

comment:10 in reply to: ↑ 9 Changed 7 years ago by nico

  • Priority changed from normal to response-needed

Replying to Romain Riviere <romain.riviere@…>:

Just a heads-up, I believe this issue should be fixed by cshore's commit in trunk r21417 :-)

Can someone confirm this issue is fixed in 10.03.1-rc1 ?

comment:11 Changed 7 years ago by nbd

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

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.