Modify

Opened 7 years ago

Closed 7 years ago

Last modified 2 years ago

#7980 closed defect (fixed)

Netgear WNDR3700 WAN port synchronization issue

Reported by: nettie@… Owned by: developers
Priority: high Milestone: Backfire 10.03.1
Component: base system Version: Backfire 10.03.1 RC2
Keywords: Cc:

Description

I'm running Backfire (10.03.1-rc3, r22796), I need to turn off autonegotiation and set the interface speed to 100Mbit full-duplex.

ethtool -s eth1 autoneg off speed 100 duplex full prints the following message to the kernel log:

ar71xx: pll_reg 0xb8050014: 0x1099
eth1: link up (100Mbps/full-duplex)

but after a second the interface syncs back to 1000Mbps/Full duplex:

ar71xx: pll_reg 0xb8050014: 0x11110000
eth1: link up (1000Mbps/full-duplex)

--

The ISP device is configured 100Mbps/full-duplex and need a port forced 100/full as all well.

--

When autonegotiation is enable the interface is automatically configured to 100Mbps/half-duplex.

If ou need more debug information just write.

Thanx a lot in advance.

Attachments (0)

Change History (6)

comment:1 Changed 7 years ago by KanjiMonster

At a first glance it looks like the PHY doesn't respect the autonegotiation bit, or perhaps doesn't even recieve it.

Assuming the PHY driver of the Realtek driver is responsible for the WAN port, I guess trunk/target/linux/generic/files/drivers/net/phy/rtl8366s.c#L1091 needs special handling for it.

I'll create up a patch for it.

comment:2 follow-up: Changed 7 years ago by Mark Mentovai <mark@…>

Fixed in r23127?

comment:3 in reply to: ↑ 2 Changed 7 years ago by KanjiMonster

Replying to Mark Mentovai <mark@…>:

Fixed in r23127?

Only for trunk, backfire still needs back porting.

comment:4 Changed 7 years ago by jow

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

Merged to backfire in r23659

comment:5 Changed 4 years ago by anonymous

That's weird cause I'm having the same issue on 12.09 and trunk.

I have one WNDR3700 on which it works perfectly and another one which looks exactly the same, version 1 for sure but WAN has to be configured to 100Mbps on the switch to work.

comment:6 Changed 2 years ago by anonymous

REFERENCES

WNDR3400v1 Wan/switch port configuration wrong
/ticket/13000.html

WNDR3800 WAN port up status not updated to /var/state
/ticket/11952.html

Netgear WNDR3700v2 no WAN connection
/ticket/11800.html

TL-WR1043ND Ver 1.8 Board Rev 1.1 WAN PORT Issue->
/ticket/11898.html

WNDR3700v2 no internet on WAN port in specific enviroment.
/ticket/11041.html

  • Problems with wan port autoconfig on netgear WNDR3700V2

/ticket/10517.html

Config error in /e/c/wireless (wrong HTmode on ch161) makes LAN dead to the world (WNDR3700v2)
/ticket/10181.html

WNDR3700 (v1) switch issues.
/ticket/7980.html

WNDR4300: Adding a VLAN in the Web UI causes a loss of connectivity
/ticket/19391.html

WAN port on WNDR3700v2 does not work
/ticket/15006.html

WNDR3800 WAN port can't work on some situation
/ticket/19630.html

WNDR4300 - number of errors
/ticket/19377.html

broadcom
http://wiki.openwrt.org/toh/netgear/wndr3400

atheros
http://wiki.openwrt.org/toh/netgear/wndr3700
http://wiki.openwrt.org/toh/netgear/wndr3800
http://wiki.openwrt.org/toh/netgear/wndr4300

https://www.dd-wrt.com/site/support/router-database

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.