[hawkeye]

Ok, so trying to make some logical sense of this...

Can someone shed some light on what the following variables refer to?
eth0
eth1
eth2
eth3

Also, when assigning ports to a vlan, I see variables like 0, 1, 2, 3, 4, 5, 8*, and 16. Is there a way to determine which of these applies to which port on the device, wireless, wan, etc? Also, what is the meaning of the asterisk (*)? On my WRT54GS, I see the asterisk after the 5*, but in the WRT600N, it seems the asterisk is after the 8*.

Trying to figure out what needs to go where. It appears that vlan2 is set as the WAN device when the wan and wireless works, but the LAN is separate, and ZeroPain's findings adds more ports onto vlan2 and then adds vlan2 onto the LAN interface list. Perhaps there is a way to do this to let them talk but yet keep them separate.

Also, does anyone know the difference between the two settings for vlans, i.e. vlan0ports= and port0vlans= ?

[CaScAdE]

[hawkeye]

Cascade,

I was aware that those were ethernet interfaces, I just did not know how to tell which corresponded with the switch, wireless radios, etc. I am not a big linux guy, but I know a bit here and there.

What did you do to pull up the info on the different interfaces? I still see an eth3 variable in both ZeroPain's settings and in my WRT54GSv2.1 that I am curious about.

One obvious issue is that lan_ifnames= does not include eth2 when initially flashed with DD-WRT. The other changes help to bridge the WAN port to the switch, but don't help us towards the goal of keeping it separate. I will play around with this some this afternoon if I have a chance.

[liquidice]

[hawkeye]

Ok, after playing around with it some this afternoon I have not gotten any further. Adding eth2 to the lan interfaces did not help. I also played around with the port numberings, wondering if perhaps 4 was for WAN on this unit rather than 0. When I flipped them around I did not get any change in results, LAN still not giving out a DHCP address. I'll keep looking to see if there is anything else that looks promising. Any other ideas anyone?

[liquidice]

[pauldmis]

I found this info in the reference design:

# Variables used by CFE and run-time OS image
# which may be modified by the run-time OS image
lan_ipaddr=192.168.1.1
lan_netmask=255.255.255.0

# Ethernet switch config (vlan1:LAN, vlan2:WAN)
vlan1ports=0 1 2 3 8*
vlan1hwname=et0
vlan2ports=4 8u

# bootloader/OS glue
landevs=vlan1 wl0 wl1
wandevs=et0
lan_ipaddr=192.168.1.1
lan_netmask=255.255.255.0

[ZeroPain]

Has anyone been able to find a seriel or jtag port on these machines and if so any help you could provide me in connecting one myself ex: images of where they are would be very helpful i have searched all around and i haven't found anyone who has done this i haven't even seen anyone try maybe i'm just not searching under the right terms but i could use some help if anyone has done this. Thank you in advance

[hawkeye]

pauldmis, interesting on the reference design specs. I see you have them posted here:
http://svn.dd-wrt.com:8000/dd-wrt/ticket/554

This mentions the 4705L reference design. Is this relevant for the chips in the WRT600N? If so, as you note, there are differences in the vlan settings both in the port numbers used, and the fact that it seems in the WRT600Nv1.1, vlan1 does not appear to be used (at least in my default install of DD-WRT. Instead it uses vlan0 and vlan2. If relevant, have you tried those vlan settings yet?

[sharo]

There are some bugfixes in the original linksys source. They are marked with "GEMTEK" - these guys make also a lot of D-link hardware
I'm trying to compile the dd-wrt sources, but still no success

[CaScAdE]

Just a quick sitenote:

BrainSlayer somehow did it :-)

Proof of it stands on my tv-rack *G*

So be patient...
I guess BS will release an image soon.
This propably will help out the devices that have the "new" switch-chip as long as he gets a cfe backup...

german thread: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=181021#181021

[BrainSlayer]

it will also be webflashable


here a snipped of the mini version without any trick from linksys webinterface (but this is untested)

[jrose78]

K this is just a quick review. I went through the web interface for the firmware upgrade and around ( I think ) 60% it gave me a page can not be displayed and the router still worked with old ip. I could not access the GUI of the router. I waited about 3 minutes and still could not access the router. I then unplugged the router and plugged it back in. It now has DD-WRT on it and the switch works !!!! I am going to try wireless now and other options. A big thank you to BrainSlayer .. You rock!! .

Update: Wireless is ok I can connect on the 5gz at 130 so the 20mhz is ok the 40mz is not there yet but thats a know issue already. No need to check anything else as really the only problem was the new switch hardware in version 1.1 and that is ok. Again Big thanks BrainSlayer!

[hawkeye]

Awesome!

I will have to try that tonight. I wonder what it was?!?!?! Will have to compare nvram settings to see if they have changed in BrainSlayer's working version.

I will eagerly wait for the standard, mega versions. Maybe before long the 40MHz will be up too. How exciting!

[CaScAdE]