Firewalla Purple not assigning IP addresses to ethernet ports?
Using Firewalla Purple 1.49 (159) in Router Mode
I've recently had major issues with my Orbi wifi (set up as an access point) dying after about 30 mins. But for some reason I lost connectivity on my wired connections as well. So I started digging around, and it appears that I'm not getting an IP address at all on my hard wired connections.
So that leads me to believe that the little switch in the Orbi is also dying when the wireless goes down. Simple solution, right? Plug the LAN output of the Firewalla Purple right into my Netgear unmanaged switch. Nope. Set up that way, I am still unable to get an IP address on my hardwired connections.
Is there some setting I'm missing here? I have hardwire-only devices that work fine (when the Orbi is up and running, like AppleTV's etc), but when I have wireless connection, my ipconfig in Windows shows the self-assigned address from Windows for the ethernet port. Same happens on my Mac computers.
It seems as though I'm only getting wireless functionality from the DHCP server. If I turn off WiFi (when the Orbi is working), I have no connectivity. This is happening on both dynamic and reserved IP addresses.
Suggestions? Thanks in advance...
Greg
-
Follow-up. Firewalla Purple app shows an IP address assigned, for example, to the ethernet port on my MBP. I've reserved that IP address in the app, then gave the connection in the MBP that same IP address. It popped up as "green", saying it's connected. However, no internet connectivity if I turn off WiFi. I have no rules defined for that device at all.
I manually added the Firewalla DNS server address to that connection as well, thinking that might have been the answer. No luck.
Greg
-
Thanks for responding! It was actually the opposite (ethernet devices not getting IP address from Firewalla) and the wifi only devices working (when the Orbi wasn't failing).
I think I have traced it back to a bad switch in my office, which I'm guessing may have gone bad a while back but I only really noticed it when my Orbi started to flake out and I realized I wasn't getting an ethernet connection.
New TP Link Deco AX3000 mesh system arriving tomorrow (so much for my 2 year old Orbi...good riddance...). Fingers crossed my network issues are behind me.
Please sign in to leave a comment.
Comments
3 comments