[native_tx]

Initially I had used R54914 then R55009 both ended up with some weird vlan3 being added to bridging table removing eth1 leaving eth2 vlan3 on br0.

You don't see this until after swconfig is configured separating port 1 -> cpuport is selected and saved, then selecting the Networking tab -> eventually adding a different ip range to further separate both networks.

The symptom is no 5ghz, no br1, no separate ip address, doesn't seem that swconfig is the problem.

In the Networking tab you will then notice the problem -> on the Bridging table section, after resetting the router using the reset button at least 3x's in a futile effort to figure out why vlan3 kept placing itself on br0 and so I had left it alone till today and by the way this is no cache problem or browser issue.

I do have the d-link dir-860l a1 on R54914 currently and it is working with the same config as it should but why not the EA6500v1 since I do have R54914 on the d-link and working?

Turns out no matter what even after clearing nvram vlan3_hwaddr is created what looks like on the get go, swconfig does not see this of course only in the Networking tab you see the problem but you don't know that vlan3 was already created and to correct it there are two variables that need to be created at least for me:

Start by adding these two variables, this will set the bridging table properly:
nvram set bat_eth1_bridge="eth1"
nvram commit

Next:
nvram set lan_ifnames="vlan1 vlan2 eth1 eth2"
nvram commit

These set where interfaces are.

I don't know what or why these are not created to complete this configuration as I had done on the d-link where it worked through the gui as for the EA6500v1 5ghz sits on eth1, 2.4ghz is on eth2 but I can't say if that is the reason or not for this odd behavior?

Long story short the EA6500v1 is configured and working using R55009 Linux 4.4.302-st48 mips as it should like the d-link was/is configured using R54914.

Regards.

[ho1Aetoo]

I have no idea what you're saying.

All new interfaces are bridged with br0 by default settings.
No hwaddr are deleted on resets and your commands are all wrong.

you bridge eth1 with eth1 lol
and VLAN2 is also not a LAN interface

You don't need to manipulate anything in the nvram because you can configure the bridge assignments in the "networking" tab.

See my signature for help

[native_tx]

In a normal circumstance as mentioned with my d-link setup was done, yes it should had went without issue with the EA6500v1.

I do not expect you to understand my workaround cause that is what it is a workaround to temporally correct a problem that presented itself at the time of configuring the router for my network needs.

The router is working fine no need to criticize users for a workarounds by using lol?

I am well aware of your link and it is very useful that is one of the reasons why I mentioned switch config was not the problem.

Currently the router is running okay showing both br0, br1 w/separate ip ranges.

Regards

[ho1Aetoo]

Once again your workaround is wrong.

You are bridging eth1 with eth1 - correct would be with br0
By the way, the nvram variable is for BATMANADV - so completely useless

https://svn.dd-wrt.com/browser/src/router/httpd/visuals/portsetup.c#L250

VLAN2 is not a LAN interface

And what your "workaround" does can all be easily set in the GUI.

If eth1 is not bridged, simply create an entry under bridge assignment (assign to bridge br0 + eth1)

And I criticize that you post wrong instructions and probably don't even know what these commands do at all

[native_tx]

Using the GUI 3x's didn't produce what should had work the first time even after clearing nvram.

If you want to keep repeating your workaround is wrong, sure that is fine.

Regards

[ho1Aetoo]

It is, because you obviously don't understand what you're doing.

[native_tx]

That screen shot is not in my gui as it was on the d-link.

Would it had been better to not had posted in the first place?

Do you want to delete my post to preserve your ego of being right and for me being wrong and not knowing what I am doing?

Have good day.

[ho1Aetoo]

You have to look at the normal "unbridged interfaces"

Then the layer 2 mesh setting appears. (see screenshot)

As I said, the nvram variable is not what you thought it was and it doesn't do anything because you can't bridge interfaces with themselves and even if you did, the variable wouldn't do anything because layer 2 mesh has to be activated first.

And it has little to do with my ego, we are just trying to fix bugs correctly and permanently for everyone.