"
oh, just find I can visit it from my public IPv4 address, seems like something wrong on the configuration...
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
22.7 Legacy Series / Can't Acess to Web GUI
May 16, 2023, 06:07:50 AM
Hi,
I recently replaced my AT&T gateway, it assigned a LAN IP (192.168.1.64) to my OPNSense router's WAN interface by default. After I enabled the IP passthrough (similar to bright mode), I rebooted both the gateway and router. Then I found I could not access Web GUI anymore. It has the response of ERR_CONNECTION_TIMED_OUT.
When I setup the LAN interface, I set the address to 192.168.50.1 (since the gateway is using 192.168.1.x); subnet bit count to 24; enable DHCP on LAN; set IP range from 192.168.50.2 to 192.168.50.250
Currently, my devices can get LAN IP automatically by DHCP, they have Internet connections, and I can access to gateway Web GUI on 192.168.1.254.
On OPNSense CLI it shows:
Can anyone figure out what's the problem to the Web GUI?
I recently replaced my AT&T gateway, it assigned a LAN IP (192.168.1.64) to my OPNSense router's WAN interface by default. After I enabled the IP passthrough (similar to bright mode), I rebooted both the gateway and router. Then I found I could not access Web GUI anymore. It has the response of ERR_CONNECTION_TIMED_OUT.
When I setup the LAN interface, I set the address to 192.168.50.1 (since the gateway is using 192.168.1.x); subnet bit count to 24; enable DHCP on LAN; set IP range from 192.168.50.2 to 192.168.50.250
Currently, my devices can get LAN IP automatically by DHCP, they have Internet connections, and I can access to gateway Web GUI on 192.168.1.254.
On OPNSense CLI it shows:
Quote
LAN (re1) -> v4: 192.168.50.1/24
OPT1 (re2) -> # Plan to make LAN bridge, not using right now
WAN (re0) -> v4/DHCP4: 45.28.xx.xx/22 #My public IPv4 address
v6/DHCP6: 2600:xxxxx/64 # My IPv6
Can anyone figure out what's the problem to the Web GUI?
#3
General Discussion / LAN Connections are Reconigzed as WAN's
January 16, 2022, 11:29:40 AM
Hi,
I recently set my opnsense router at home, but I noticed that LAN connections are only recognized as WAN connections. For example, the internal Linux server shows the last login was my WAN IP, instead of my LAN IP address. My internal Adguard Home DNS server also only has one client which is my WAN IP.
When I check the firewall log, the rule was the default LAN rule. The traceroute also shows the actual route never went to WAN. I have attached my LAN firewall rules below.
Can anyone help me figure out what causes this problem? Thanks!
UPDATE: I find this problem only occurs when the connection is going through the LAN bridge. If two devices are under the same interface, the connection shows LAN IP address.
I recently set my opnsense router at home, but I noticed that LAN connections are only recognized as WAN connections. For example, the internal Linux server shows the last login was my WAN IP, instead of my LAN IP address. My internal Adguard Home DNS server also only has one client which is my WAN IP.
When I check the firewall log, the rule was the default LAN rule. The traceroute also shows the actual route never went to WAN. I have attached my LAN firewall rules below.
Can anyone help me figure out what causes this problem? Thanks!
UPDATE: I find this problem only occurs when the connection is going through the LAN bridge. If two devices are under the same interface, the connection shows LAN IP address.
Pages1
