yes I have 5 WAN Interfaces but I thought that is normal with Openwrt because I didn't make them, they are automatically configured after the first boot. I just need one but that is impossible (at least for me). I can delete all the extra Interfaces, apply the changes, all good. After I reboot the machine, they are all back (tried that several times). Everything gets saved and lives after the reboot except the WAN Interfaces, they all get back after the reboot.
Maybe you can remember a week or two ago I build a router PC with Openwrt, on that PC I have 6 WAN Interfaces and 3 TAPI Interfaces which I can delete but they are all back after the reboot. That is why I thought that this behavior is normal. That means on my router PC port forwarding also doesn’t work (haven’t tested it yet).
Do you have an Idea how I can permanently delete all the other Interfaces? I need just one WAN (on my router PC 2)…
Thank you for your answer. I understand what you mean but if I configure the WRT3200ACM as a dumb AP wouldn’t I lose his power? This is the main reason for the change to the bigger router. The CPU of the MR200 is to weak, it can’t handle the traffic. If I configure the WRT3200ACM as AP the MR200 would still have to handle all the traffic, or am I thinking wrong? I wanted the WRT3200ACM to handle the traffic and all the NAT because he has enough power to do so. The MR200 should just be a “dumb WAN Interface” but also handle the IOT stuff because the WRT3200ACM has problems with it…
Could you please explain what this line does? As far as I understand the line, it deletes the source port. Wouldn’t that mean that I am redirecting all the traffic form the WAN Interface to one port and one machine?
today I tried to compile an image for the WRT3200ACM with the latest sources and found out that this is not possible. Every Image that get created is incompatible with the router. There is absolutely no problem compiling the stable sources and the image is compatible with the router. I noticed one difference in “make menuconfig” between the stable and the latest branch. In the “Target Profile” of the stable branch I can select the WRT3200ACM “Rango”, nothing else. In the “Target Profile” of the latest branch there is the WRT3200ACM “Rango” and the WRT3200ACM (without “Rango”), when I select the “Rango” the other one gets selected automatically and I can’t unselect it. Can it be that this is the reason I get incompatible Images? I tried to force flash the Image which basically bricks the router, luckily it has two boot Images so I switched to the other one and reflashed the first one with a stable image…
Is there a way or a trick to unselect the second WRT3200ACM? Maybe that would produce a compatible Image?
I just finished building and flashing an image from current master with no issues. There was a name reconciliation pushed to master a while back, but that should not cause any issues. What do you mean when you say the images is incompatible; if you are moving between stable and master you will / should get a warning, do not keep config as master has changed to DSA and will yield an install with no link on the wan / lan nics.
I newer keep the settings, it’s better to configure everything from the scratch in my opinion. Yes, I get the DSA message, but the router is a brick after the flash. I don’t even get an IP address.
Device linksys,rango not supported by this image Supported devices: linksys,wrt3200acm armada-385-linksys-rango linksys,rango - Image version mismatch: image 1.1, device 1.0. Please wipe config during upgrade (force required) or reinstall. Reason: Config cannot be migrated from swconfig to DSA Image check failed.
The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.
Just the generic message, trying to stop people from messing up on an upgrade, once you flash (force, but without keeping config) the file /etc/config/system will have option compat_version '1.1' in an attempt to indicate where you are at in the config compatibility process. And on it will go...
@LordRayden
Had similar issue with IOT devices on the WRT3200ACM (not getting an IP for IOT devices, in my case those were indeed ESP8266-based devices).
Created a dedicated SSID for those devices with WMM disabled. Rock sold for 2 years now. Below screenshot of the settings: