I'm having a problem accessing a private network across interfaces of the FWG.
So my modem (in bridged mode) assigns the FWG interface a public IP but it also has it's own private IP for configuration. I used to be able to access the modem though the phone app from another private network hosted by the FWG but it seems to not know hot to get there anymore.
Modem connected to eth2 assigning public IP to interface but running a 192.x.x.x/24 network for config
Wireless router in AP mode connected to eth3 NOT running DHCP just VLAN tagging wireless networks. Private IP for modem does not over lap
Virtual network created in FWG with VLAN tagging to assign a different 192.x.x.x/24
I have no over lapping private 192 networks
I can ping the private IP of the modem from the FWG SSH console
There was a host route for the modem auto populated in the routing table, I remove this and created a new route for /24 sending it to eth2, I can still ping the modem from SSH (so that didn't break) but not able to ping from my workstation. (workstation and phone are on same VLAN)
VLAN has no rules created in FWG
I did a packet capture, from the workstation I can see the packet leaving eth2 but no reply is found but when I ping from FWG I can see the ping come back. I can also, from the FWG, wget the webpage hosted on port 80 as a confirmation that I'm talking to the right device. So the modem is online and responding to that IP.
Is there something in the FWG app that may be blocking this traffic?
Please sign in to leave a comment.