Suddenly external access to B3 not possible
Posted: 08 May 2014, 07:19
Hi,
my B3 serves as router + firewall + server. Software version is 2.6.0.2. The WAN port is connected to a cable modem, and there are several devices connected via LAN cable and wlan. I'm using easyfind to make external access comfortable.
Since a few days, I can't reach the B3 from outside, while the internal access still works fine. But it's not possible to get access through port 80 or port 22 (connection time out), although the ports are enabled. This is my firewall configuration:
It's definitely not easyfind that is causing the trouble because sending a ping using the easyfind name points correctly to my external IP.
All this seems rather strange to me. External access used to work fine for more than one year and I didn't change my configuration at all. Therefore, I have no idea how to fix this problem. Maybe someone has any suggestions?
Thanks,
Nils
my B3 serves as router + firewall + server. Software version is 2.6.0.2. The WAN port is connected to a cable modem, and there are several devices connected via LAN cable and wlan. I'm using easyfind to make external access comfortable.
Since a few days, I can't reach the B3 from outside, while the internal access still works fine. But it's not possible to get access through port 80 or port 22 (connection time out), although the ports are enabled. This is my firewall configuration:
Code: Select all
iptables -L
Chain INPUT (policy DROP)
target prot opt source destination
REJECT tcp -- anywhere anywhere tcp flags:SYN,ACK/SYN,ACK state NEW reject-with tcp-reset
DROP tcp -- anywhere anywhere tcp flags:!FIN,SYN,RST,ACK/SYN state NEW
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere
ACCEPT icmp -- anywhere anywhere icmp time-exceeded
ACCEPT icmp -- anywhere anywhere icmp echo-request
ACCEPT icmp -- anywhere anywhere icmp fragmentation-needed
ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
ACCEPT tcp -- anywhere anywhere tcp dpt:www
ACCEPT tcp -- anywhere anywhere tcp dpt:https
Chain FORWARD (policy DROP)
target prot opt source destination
ACCEPT all -- anywhere anywhere
ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED
ACCEPT icmp -- anywhere anywhere icmp fragmentation-needed
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
All this seems rather strange to me. External access used to work fine for more than one year and I didn't change my configuration at all. Therefore, I have no idea how to fix this problem. Maybe someone has any suggestions?
Thanks,
Nils