This seems the same issue I was having with Mikrotik tunnels. It may be the same "fix" needs applied to EOIP tunnels as well. Try disabling the EOIP tunnel on the opposite side and see if it still crashes/boot loops your mx4300. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
As of r58124 the note is gone, so someone managed to do a serial boot dump. Guess ill try to brick mine this weekend. So whats the deal with the two partitions? dd-wrt sits on first, and if it boot loops 5 times it loads the second partition?
As of r58124 the note is gone, so someone managed to do a serial boot dump. Guess ill try to brick mine this weekend. So whats the deal with the two partitions? dd-wrt sits on first, and if it boot loops 5 times it loads the second partition?
Someone on the OpenWRT forum supplied him with a serial log. It's pretty stable now. Still some radio issues perhaps Power levels seem to fluctuate.
Two partitions is basically a bootable backup. My method is to put a known working version onto both partitions when first flashing (three total flashes), then alternate back and forth as builds are released. This way, if you would happen to install a bad build that cannot boot (or no longer update), you can switch partitions and be good again.
If one partition fails to boot three times (not 5), it will switch boot partitions automatically. If it fails to boot five times, it erases NVRAM. This is adjustable in Administration tab.
You can also manually switch boot partitions in a few ways. From a telnet or ssh session using a combination of the fw_printenv and fw_setenv commands. Or just toggle the power switch 3 times, counting to 4 or 5 between power cycles. The forth boot will be the opposite partition. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
No guarantee it will be available in the next release, but work is being done to fix restoring the Factory OEM images on this router and others.
What will be available in the next release is the ability to change the CPU clock on this device up to 2208mhz. Note this is still in ondemand mode so you may not notice it immediately, and it's highly recommended you do not change this.
NOTE: While the SoC does support these higher CPU clock speeds, the heat sinks may not.
----USE WITH CAUTION!----DO NOT RUN AT THESE SPEEDS IN PERFORMANCE MODE or you will likely fry your CPU in a short amount of time. You have been warned! _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
Seems to be working well with the exception of eoip tunnels still. It goes in to a boot loop once I connect internet to the wan port or if I enabled static ip addressing on the wan.
I have attached the dmesg and mtd strings
@lexridge: Is there a tutorial on the mikortik tunnels setup? Will it work from dd-wrt router to another or does it require a mikrotik router?
Posted: Tue Sep 03, 2024 3:12 Post subject: Re: Enabling eoip tunnels still goes to boot looping
dun4cheap wrote:
@lexridge: Is there a tutorial on the mikortik tunnels setup? Will it work from dd-wrt router to another or does it require a mikrotik router?
There are no tutorials that I have found and it should work from ddwrt<>ddwrt.
I spent a lot of time on Mikrotik and VXLan tunnels with very limited progress. When I started out testing them, neither worked. This testing was done on a MR7350 but should be identical on the mx4300. Initially I could not get the vxlan1 interface to come up. This has been fixed. Regarding Mikrotik: even without a Mikrotik tunnel configured on the mr7350, any other router with a Mikrotik tunnel pointed at the mr7350 would cause it to kernel dump. This too has been fixed.
What I tried with Mikrotik with some limited success (they both actually sent and received some data). I was never able to ping the remote sides.
Here are some things I discovered while doing this, and this could be completely wrong. Just what I observed:
1. The remote and local IP addresses cannot be the same as your router's subnet.
2. You have to unbridge the tunnel.
3. You have to add a manual route under Advanced Routing on each side.
4. I am still unclear on what the MTU value should be, but I suspect the default is not correct.
5. There is no place to add a tunnelID. According to the Mikrotik, this is a requirement, but could be that BS has done this automatically behind the scenes. No idea at this point.
Sorry I could not be of more help. FYI, I also messed with EoIP and never experienced any crashes with it, but also never made it work either. I didn't spend a lot of time on it (yet), and I didn't have my WAN port connected. My goal is to use one of these tunnels to move vlans over a wireless connection. Once I get it figured out I will write a howto guide for it which will hopefully include all three of these tunnels, if possible. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
I have eoip working on my asus routers and Buffalo. But when I enable it on the mx4300 and the static ip address is set on the Wan or I set it up for dynamic and plug a cable in the Wan port it goes in to a boot loop. Not reset though. _________________ 5 Linksys MX4300 LN1301 DD-WRT v3.0-r58376 std (09/11/24)
I have eoip working on my asus routers and Buffalo. But when I enable it on the mx4300 and the static ip address is set on the Wan or I set it up for dynamic and plug a cable in the Wan port it goes in to a boot loop. Not reset though.
This sounds much different than the issue with the Mikrotik tunnel causing kernel oops on the mr7350 (fixed). Perhaps @kernel-panic69 can point BS to your kernel dump upload you posted earlier. I don't know how to link a specific post, or I would do it.
If that doesn't get any attention from BS, I will try to re-create your circumstances in a test environment and send him my logs, assuming I can re-create it. I have other projects going on ATM, so I may not get to that for a while. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
Okay folks, we can finally flash back to stock FW, if you really want too. This only works from the console. YOU CANNOT DO THIS FROM THE WEBUI!
First, scp, sftp or ftp the factory firmware file to the router's /tmp folder (figure this out on your own).
Next either SSH or Telnet into the router's console and cd to /tmp.
Do #ls -lart to make sure the file you just uploaded is present. Using the -lart flags will sort your newly uploaded factory firmware file to the bottom of the output list.
Also type
Code:
#fw_printenv -n boot_part
to verify which partition you are booted from, assuming you want to put the factory firmware back onto only one partition while retaining DD-WRT on the currently booted partition. NOTE: If the file is not present when you run the following command, you will get a segmentation fault. NOTE2: Should will be fixed in the next public release..and has been as of release r58362.
Note, linux|linux2 are the two individual partitions. DO NOT USE BOTH HERE, chose one or the other. If the output of fw_printenv is 1, then you would writing to linux2 in this command. If the output of fw_printenv is 2, you would use linux. This ensures you keep your presently booted dd-wrt partition intact. Also, be careful. Both the linux or linux2 MUST match in both places of the command line. This is because the -e erases it first, then the -f writes to it. THEY MUST MATCH or else the router will refuse to boot from whichever partition you flashed to.
If you see this error, you can ignore it:
Code:
Writing from FW_MX4300_1.0.4.215382_prod.img to linux ... [w]
Warning unaligned data, we use manual padding to avoid errors. size was 131072!!!
Once completed you need to change your boot partition to where you just flashed the factory firmware.
Code:
fw_setenv boot_part 1|2
This is either 1 OR 2. You should know which to use by now.
If you choose to return to Factory Firmware on both partitions, just run the above command on BOTH partitions, one at a time. You will not need to change the boot partition once completed. Just reboot afterwards.
Code:
mtd -e linux -f write factoryfilename.img linux
mtd -e linux2 -f write factoryfilename.img linux2
Using two command lines instead of one:
If combining the erase and flash commands makes you nervous, you can split them up.
This should work on all newly supported Linksys AX routers and maybe others, but has only been tested on the MX4300 and the MR7350.
Hopefully this provides a guide to all those who wish to return to stock OEM Firmware. Good luck! _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
Last edited by lexridge on Mon Sep 09, 2024 5:33; edited 3 times in total
Just for clarification, because I know how people are, I'd venture to say that you'd want to flash to one partition via CLI then switch to that boot partition, reboot, then flash from stock webUI to complete the transaction to return completely to stock because otherwise, you best hope that mtd is still resident in RAM.
Good call @kernel-panic69! Having Factory on one partition and ddwrt on the other can create a bunch of caveats that most people would not be able to wrap their head around. Such as, you can not upgrade DD-WRT from the WebUI ever again in this situation. You will trash the Factory partition if you attempt this and it will be completely unbootable. All updates would have to be done manually using the methods described above and written to the correct partition which ddwrt is booting from.
IT IS RECOMMENDED YOU FLASH BOTH PARTITIONS TO FACTORY to avoid this situation unless you really know what you are doing. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: VLANs, Samba, WG, Entware - r60xxx
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r60xxx
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r60xxx
- Linksys MX4300: (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r60xxx
- Linksys MR7350: WDS Station for extended Ethernet r60xxx
- Linksys MR7500, MX8500: None in production. Just testing. r60xxx
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
- Forum member #248
