Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#1084 - All ethernet ports assigned to WAN on EnGenius ENS202EXT #6603

Closed
openwrt-bot opened this issue Oct 19, 2017 · 4 comments
Closed
Labels

Comments

@openwrt-bot
Copy link

nixcamic:

On the EnGenius ENS202EXT after flashing the image to install LEDE I had all ethernet ports by default assigned to WAN, making me unable to connect to the router, I had to go in through serial and enable WiFi/move ports over to the LAN bridge. Using Snapshot r5108-48dcd26.

@openwrt-bot
Copy link
Author

nixcamic:

To be clear, eth0 seemed to be nothing, and eth1 was both ports, no ports had the mac address printed on the back of the router.

@openwrt-bot
Copy link
Author

hanetzer:

Huh. Unusual, I don't recall running into this myself. I need to learn how one can preconfig this device. Ideally both eth0 and eth1 need to end up on br-lan, right? Considering this is not a router in the traditional sense?

@openwrt-bot
Copy link
Author

nixcamic:

I wonder if it could have to do with having easyWRT installed previously, I wiped all settings in between but maybe it screwed up something more permanently?

@openwrt-bot
Copy link
Author

whitslack:

1.) A big thank you to everyone who has worked on producing a public build of OpenWrt that runs on the ENS202EXT. You have really opened up this otherwise limited device.

2.) Bad news, though. Installing "ens202ext-squashfs-factory.bin" through the OEM firmware's web interface works, but then the device becomes inaccessible via any network interfaces upon rebooting into OpenWrt. Indeed, as described in this bug report, eth0 (which seems not to be connected to any external ports) is brought up and attached to br-lan, which is assigned IP address 192.168.1.1, but eth1 (which seems to be connected to an internal hardware bridge that also connects the two external Ethernet ports on the device) remains down.

I was forced to open up the device, solder a pin header to the serial port pads, and connect the serial port to a Raspberry Pi's 3.3-volt UART pins by wire-wrapping. The serial console was then very usable and reliable, but that was a lot of time that I didn't intend to spend on this project.

Anyway, once I had a serial console, I was able to fix the fault in the device by booting into OpenWrt's failsafe mode (not the ENS202EXT's failsafe partition!) and executing "firstboot" to blank the jffs2 file system. Then rebooting the device back into normal mode made everything work as it should.

In hindsight, maybe I could have erased the jffs2 by using the reset button while booted normally. I was assuming at the time that flashing OpenWrt over the OEM firmware would have erased all user settings. (I did perform a factory reset in the OEM firmware just before flashing OpenWrt, but that was not enough.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant