0Port 8080
Does anyone know if there are there any rules blocking a port forward to port 8080? Or is port 8080 in use on the eero system?
I have an eero network setup where I have a WLAN client running as a bridge to a non wireless device. I can access the end device fine and access the wired device's web manager, but when I try to port forward to the WLAN bridge using port 8080, it does not work.
I then move the exact WLAN bridge, end device setup to another vendor access point, and the port forward works fine.
eero AP - 192.168.4.1
End device - 192.168.4.200
Port forward attempt - 192.168.4.200:8080
-
Hello shadejr,
eero does not prevent people from using port 8080 for port forwarding. There may be something not test correctly. Did you setup the IP Reservation first? I have shared an article below that will go over these steps. Let me know if you still need assistance after this.
https://support.eero.com/hc/en-us/articles/207908443-How-do-I-configure-port-forwarding-
Thank you,
James
eero Support
-
Hi, I am still not able to have the port forward work. I created a drawing of my use case. See attached image. All my devices are inside the eero network. The WLAN bridge is transparent to the eero network (passes along the IP and MAC of the end device). I can navigate from my laptop, to the end device web manager at 192.168.4.200, but when I try to port forward to the web manager of the wlan brdige (with port 8080), it does not work. If I move the WLAN bridge and end device to a different, non-eero access point, it works fine.
I have tried this both with no port forward rules set up in the eero app as well with rules set.
Any comments would be helpful. Thanks!
-
Some more detail, when I do a port scan on the eero network, I see port 8080 is filtered (see filtered attachment).
When I move my setup to another access point (non-eero) port 8080 shows open (see open attachment)
-
Any feedback on this topic?
-
shadejr I took a look into your issue here, and wanted to follow up with you. You're able to access the web manager by navigating to 192.168.4.200 while on WLAN, yes? Since this is a LAN issue, there shouldn't be a need to open any ports. Hairpin NAT is automatically enabled on eero networks, which is why you're capable of accessing the web manager using the IP address.
Is your secondary non-eero access point on a different subnet than eero? If so, that would be the reason you're able to access the manager through 192.168.4.200:8080.
Kora | eero Community Team
-
-
Hi Kora,
Correct, when my laptop is connected to the eero AP, I can navigate to 192.168.4.200 over the wireless connection and access the end device.
The non-eero access point is completely isolated (completely different setup) from the eero network. There is no networked/physical connection between the two. I just powered on another vendor AP, connected my laptop WLAN card and my WLAN bridge/end device to the access point and then I can navigate to the end device at 192.168.4.200 and the port forward works at 192.168.4.200:8080.
-
Hi, just following up on this item. I still cannot access anything using port 8080
-
shadejr Thanks for following up. I think there is some confusion on our end as to what exactly you are attempting to accomplish. Is there a specific reason that accessing the device via its IP address is not adequate when you are on the LAN? Port forwarding is designed to be used for external access, meaning you are accessing a device on the eero network when you are not on the same network. This is accomplished by inputting the external public IP and the port that you configured. When you are on the same network, there is no need for any port forwarding to access those devices. If there is something specific you are trying to accomplish here that standard local access does not permit, let me know and I can look into what other solutions we can offer.
-
Evan (eero support) Hi Evan, I am testing compatibility with a 3rd party device on an eero network. The wireless bridge I am using has a function that makes the wireless bridge (MAC and IP) transparent to the eero network. The wireless bridge passes through the IP and MAC of the end device. The wireless bridge uses a port forward as a way of accessing the web manager of the bridge. This way the user can access the end device as well as the bridge but the eero network will only see a single IP and single MAC, that of the end device.
-
shadejr Thank you for the clarification! If the bridge is not registering as connecting to the eero network, as it does not get its own IP, rather just passing the information along to your end device, the eero effectively doesn't know it even exists, making access to it not possible.
-
Evan (eero support) Thanks Evan. Would this still be the case when all the communication is destine for the end device? When I request data from the end device, I send it to IP 192.168.4.200. The ARP table in the eero knows this is at MAC/IP of the end device. The end device responds to the request with its own MAC and IP. When I send a request to the port forward destination, 192.168.4.200:8080, the request will still have a destination mac and IP of the end device. When the WLAN bridge sees the packet on port 8080, it then responds to the request with the MAC and IP of the end device, not its own. So, the eero should know are all times where to send the packet as the destination address is always the MAC/IP of the end devices and all responding communication would be with a source MAC and IP of the end device
-
Evan (eero support) Just wanted to check if there were any other comments/thoughts on this topic.
-
So I just tested again and looks like it is working now. The only thing that has changed is an eero update the other night to 6.3.0. At this point everything is working as expected, although not sure why it wasn't working before with the same setup.
-
