Buffalo WZR-1750DHP only one LAN port responding

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
Author Message
luiswu
DD-WRT Novice


Joined: 07 Apr 2015
Posts: 13

PostPosted: Tue Apr 07, 2015 23:18    Post subject: Buffalo WZR-1750DHP only one LAN port responding Reply with quote
Hi,

I've just flashed a Buffalo WRZ-1750 with the Brainslayer v24 preSP2 r25697 build, first from the stock firmware using the factory-to-dd-wrt.bin file then with the buffalo-wrz-1750dhp-webflash.bin file.

Each time I flashed the router with a DD_WRT firmware I did a 30/30/30 hard reset before and after the flash (leaving a good amount of time after the flash before doing the hard reset).

After the second flash I've noticed that the router has stopped responding to pings in LAN ports 2 through 4, though the router still responds to pings on LAN port 1. Other than that the router seems to behave normally. The ping on the LAN port 1 is responding with a TTL=64. All the ports were working properly after the first flash.

When I say that the router does not respond to pings I mean that either the pings result in a request timeout or in a no route to host. The computer I am pinging the router with is on the same network than the router (I just move the cable from LAN port 1 through LAN port 4).

The only peculiar thing is that before doing the second flash I was setting up vlans in the ports that are no longer responding, but the vlan.*ports and port.*vlans nvram variables were set back to normal configuration by the the hard reset. I know that the hard reset took place because I had to re-define the root password after each hard reset.

I flashed a third time the router with the Kong K3-AC-Arm build 25100M with exactly the same result.

Is it possible that the router has been partially bricked (if such thing is possible)? Any idea on how can I restore connectivity to the rest of the LAN ports?
Sponsor
djrobx
DD-WRT Novice


Joined: 12 Oct 2007
Posts: 18

PostPosted: Wed Apr 08, 2015 5:47    Post subject: Reply with quote
What do you get for

nvram get vlan1ports?

I believe this should be:
0 1 2 3 5*

If using a more recent DD-WRT you should also be able to see the link states for each port on the VLAN page. I see red for an unconnected port, yellow for a 10/100 connection, and green for a 1000 connection. Are your states showing properly?

Also what happens if you try to create another VLAN on another port?

I use port 4 for a second WAN link. You should be able to just tick the 4th port into a new VLAN in the VLAN page, and then bring it up:

ifconfig vlan2 192.168.1.200 netmask 255.255.255.0
ifconfig vlan2 up

I've moved through many firmwares on my WRZ-1750, but have never done a 30/30/30. Just did the factory reset once from DD-WRT when I switched to one of DD-WRT variants.
luiswu
DD-WRT Novice


Joined: 07 Apr 2015
Posts: 13

PostPosted: Wed Apr 08, 2015 7:31    Post subject: Reply with quote
Hi,

I get exactly what you say, the same that I got after the first flash: 0 1 2 3 5*. The GUI show the four ports on VLAN 1.

Right now I have only one computer at hand (I'm configuring it before moving it to production env), therefore I can only see a green light on port 1 on that page. The leds on the back of the router are blinking green however when I plug the cable into the LAN ports.

At this point I am trying to get connectivity back to the LAN ports before creating VLANs again. Some of the ports will be tagged therefore it would be very difficult to debug if there is any problem unless I am certain that the ports work.

I thought that the GUI only had effects on the port.*vlans variables, not the vlan.*ports, I thought that you had to manually define the vlan.*ports variables as well. In any case I also brought up the interfaces via ifconfig when everything was working.

I followed the advise on the peacock thread for doing a 30/30/30 reset. On second thoughts I believe that flashing the router a second time after flashing the factory-to-ddwrt may have been unnecessary, but then again I don't see how can that may have damaged the router, if done properly.

I'll try to get another computer to check the status of the ports in the VLAN page, any other suggestion meanwhile?
djrobx
DD-WRT Novice


Joined: 12 Oct 2007
Posts: 18

PostPosted: Wed Apr 08, 2015 16:19    Post subject: Reply with quote
You might try flashing the official Buffalo WZR-1750DHPD DD-WRT firmware, and doing the factory reset with that in place.

http://www.buffalotech.com/support-and-downloads/download/wzr1750dhpd-v24sp2-23709c.zip

The one time I did do a reset, it was with that firmware, and I have to think Buffalo would have verified that the defaults contained in their own firmware build are correct.

If you wanted to check the link states with only functional wired network, you could move your one working PC to the non-functional port, then log into the DD-WRT UI through wifi on your mobile phone.
luiswu
DD-WRT Novice


Joined: 07 Apr 2015
Posts: 13

PostPosted: Thu Apr 09, 2015 23:36    Post subject: Reply with quote
It turns out that I was wrong and vlan1ports contained the settings prior to the hard reset, making it impossible to connect: vlan1ports=0 1t 2t 5*. I still can't understand how that variable survived a hard reset of the router...

Now everything is working except for the fact that I have declared a vlan3 on the fourth port of the router but I can't connect to it. Here is the configuration that I am using:

nvram show | grep vlan.*ports
vlan1ports=0 1 2 5*
vlan2ports=4 5u
vlan3ports=3 5
vlan5ports=1t 2t 5
vlan6ports=1t 2t 5
vlan7ports=1t 2t 5

nvram show | grep port.*vlans
port0vlans=2 18 19
port1vlans=3 18 19
port2vlans=1 5 6 7 16 18 19
port3vlans=1 5 6 7 16 18 19
port4vlans=1 18 19
port5vlans=1 2 3 5 6 7 16

nvram show | grep vlan.*hwname
vlan1hwname=et0
vlan2hwname=et0
vlan3hwname=et0
vlan5hwname=et0
vlan6hwname=et0
vlan7hwname=et0

On top of that I've declared the following interfaces:
ifconfig vlan3 192.168.3.1 netmask 255.255.255.0
ifconfig vlan5 192.168.5.1 netmask 255.255.255.0
ifconfig vlan6 192.168.6.1 netmask 255.255.255.0
ifconfig vlan7 192.168.7.1 netmask 255.255.255.0
ifconfig vlan3 up
ifconfig vlan5 up
ifconfig vlan6 up
ifconfig vlan7 up

Now when I configure a computer with 192.168.3.100/255.255.255.0 gw 192.168.3.1 and plug the cable into the port #4 of the router (port1vlan, the numbering is reversed) I can't even ping the gateway, as if the interface was not defined. If I do however ifconfig in the router I can see the interface is up and running:

vlan3 Link encap:Ethernet HWaddr CC:E1:D5:6D:6B:BA
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

The computer that I am connecting to the vlan3 is not using a tag vlan. Any idea what may be going wrong?
djrobx
DD-WRT Novice


Joined: 12 Oct 2007
Posts: 18

PostPosted: Sat Apr 11, 2015 2:58    Post subject: Reply with quote
Glad to hear you got that sorted out.

My working config is:

root@DD-WRT:~# nvram show | grep port.*vlans
port5vlans=1 2 3 16
port3vlans=1 18 19 21
port1vlans=1 18 19 21
port4vlans=3 18 19 21
port2vlans=1 18 19 21
port0vlans=2 18 19 21

root@DD-WRT:~# nvram show | grep vlan.*ports
size: 39640 bytes (25896 left)
vlan2ports=4 5u
vlan3ports=3 5*
vlan1ports=0 1 2 5*

root@DD-WRT:~# nvram show | grep vlan.*hwname
vlan3hwname=et0
vlan2hwname=et0
vlan1hwname=et0


I'm not using tag VLANs either. Now, reviewing the above, it looks like my portxVlan's doesn't seem to match the vlanxports (vlan3 is really on port 1, which is 4 on the back of the router, UGH!). It still works anyway, the vlanxports seems to be the important one.

I noticed I have '5*" where you have "5" also. Not sure what that difference means.

You might drop vlans 5-7 until you get 3 working.

Here's all the variables I have set for vlan3:

root@DD-WRT:~# nvram show | grep vlan3
vlan3_netmask=255.255.255.0
vlan3hwname=et0
vlan3_txq=0
vlan3_dns_ipaddr=0.0.0.0
vlan3_ipaddr=192.168.2.1
wan2_ifname=vlan3
bat_vlan3_bridge=br0
vlan3_mtu=1500
vlan3_dns_redirect=0
vlan3ports=3 5*
vlan3_multicast=0
bat_vlan3_enable=0
vlan3_isolation=0
vlan3_nat=0
vlan3_bridged=1
luiswu
DD-WRT Novice


Joined: 07 Apr 2015
Posts: 13

PostPosted: Sun Apr 12, 2015 15:15    Post subject: [Solved] Buffalo WZR-1750DHP only one LAN port responding Reply with quote
Your last post did it!

Somehow I was missing the following information for my vlan3:
vlan3_netmask=255.255.255.0
vlan3_ipaddr=192.168.3.1

One I set those variables and rebooted everything was up and running. Thanks for the info!

On the "5*" vs "5": I seem to recall that in the swiched port (http://www.dd-wrt.com/wiki/index.php/Switched_Ports) part of the wiki they mentioned that the 5* was necessary only for vlan1ports definition, the exact reason why totally escapes my understanding.
djrobx
DD-WRT Novice


Joined: 12 Oct 2007
Posts: 18

PostPosted: Mon Apr 13, 2015 4:43    Post subject: Reply with quote
Excellent! Glad I could help.
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum