[lordcy]

I have been trying everything I can think of to get the 4th Ethernet port on my R7000 to work. I have tried working cables and connections that were verified but the port will not come up. I did have r26138 installed and tried updating to r30471 to see if that would solve my issue but it did not. Are there any commands in ssh that I could use to check the interface or is there a new Kong firmware that I could download that could fix this issue? I have posted my ifconfig below. Thanks.

LordCy

root@R7000:/etc/config# ifconfig -a
br0 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:45
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1227953 errors:0 dropped:34860 overruns:0 frame:0
TX packets:4736093 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:166722194 (158.9 MiB) TX bytes:6829187386 (6.3 GiB)

br0:0 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:45
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth0 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:46
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8173015 errors:0 dropped:0 overruns:0 frame:0
TX packets:1976237 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2806925957 (2.6 GiB) TX bytes:347682163 (331.5 MiB)
Interrupt:179 Base address:0x4000

eth1 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:48
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1662954 errors:0 dropped:0 overruns:0 frame:1698919
TX packets:4600736 errors:94 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:238469478 (227.4 MiB) TX bytes:2354083198 (2.1 GiB)
Interrupt:163

eth2 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:45
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:187367 errors:0 dropped:0 overruns:0 frame:21203
TX packets:294787 errors:132 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:36115054 (34.4 MiB) TX bytes:203372909 (193.9 MiB)
Interrupt:169

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MULTICAST MTU:65536 Metric:1
RX packets:3890 errors:0 dropped:0 overruns:0 frame:0
TX packets:3890 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:275446 (268.9 KiB) TX bytes:275446 (268.9 KiB)

teql0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:172.18.13.1 P-t-P:172.18.13.1 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

vlan1 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:46
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:169156 errors:0 dropped:0 overruns:0 frame:0
TX packets:950605 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:24079739 (22.9 MiB) TX bytes:185091085 (176.5 MiB)

vlan2 Link encap:Ethernet HWaddr E4:F4:C6:0E:B8:47
inet addr:70.180.64.247 Bcast:70.180.71.255 Mask:255.255.248.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8003794 errors:0 dropped:12510 overruns:0 frame:0
TX packets:1025632 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6898004450 (6.4 GiB) TX bytes:154686130 (147.5 MiB)

[Malachi]

Probably a bad port.

[lordcy]

Thanks. It was working on the original netgear firmware before I put dd-wrt on it and never used the port until the other day. Any commands I could run for sure that would tell me it is a hardware issue?

[Malachi]

Hmm. That is strange. Since it's easy to do, I would try to flash stock to it, not the latest, in case they made it so you can't flash third party firmware it.
See if it works then. If it does, try using kongs firmware followed by an nvram erase.

[Per Yngve Berg]

Probably some wrong nvram variables for the vlan set-up.

What is the output of "nvram show | grep vlan.*ports"?

PS. You are in the wrong forum. As this is a Broadcom based router, use the Broadcom forum.

[lordcy]

I'll try to flash the firmware when I get more time to do so. I thought about that too, but I'm sure someone would have noticed if the DD-WRT firmware didn't allow all Ethernet ports on the router. Makes me think that it is broken. How exactly do you do an nvram erase? I'm not that experienced or comfortable with deleting the nvram...

Here is the output from the nvram command, vlan1 is my data vlan.

nvram show | grep vlan.*ports
size: 49585 bytes (15951 left)
vlan2ports=0 5u
vlan1ports=1 2 3 4 5*

Sorry if I posted in the wrong forum, I thought the R7000 had an arm processor. If a moderator wants to move my issue to the Broadcom forum, I would appreciate it. Thanks.

LordCy

[<Kong>]

The port status is directly queried from the switch. Vlan setting do nothing with the port status.

You could only deactivate the port by running special robo commands, dd-wrt firmware does not do that.


Thus either the port is defective, or your cable, or you client network card is defective.

[mac913]

Switch the connecting cables between port 3 & 4 to see if the problem follows the client.

I've blown a port or two from static electricity...