@rprengel said in ping works fine in both directions but http / ssh from remote to intern fails:
@viragomann said in ping works fine in both directions but http / ssh from remote to intern fails:
@rprengel said in ping works fine in both directions but http / ssh from remote to intern fails:
No obvious blocker / filter /firewlls are active.
I was expecting this view. That's why I suggested to sniff the traffic to see, what's going on in fact.
I found a youtube video with some hints that a NAT may be necessary on the pfsene because of the fritzbox allthough ping is working.
Yes, NAT is a hack to circumvent firewall restrictions. But it's rather recommended to configure the firewalls properly instead of doing hacks.
It's a workaround to enable access to devices from outside, which have no default gateway setting.Hallo,
found the problem but not solved.
I can reach system from „outside“ using ssh on port 22 and http using non default ports.
I tested the last days only trying to reach a default webserver.
It looks like ports 80 and 443 are the problem. Maybe the anti-lockout rule?
Ralf
Now solved:
After I realized that ssh from outside worked too I tried another webserver. This one worked immediately.
The first web-target was the interface of a printer that obviously didn t deliver its contect in external lans.
Ralf