yes, because i disabled ipv6 connection in router as long eset firewall does not protect this.
this is not a adress, that is the configured "eset trusted zone" that i manually have added recently for hopefully allowing local traffic. i removed this. i have no vpc connection.
Teredo is ok, but i have disabled now. now my eset adapter view looks same as yours.. with the problem persist. instead my isp gives me ipv6 only. ipv4 is pseudo because dslite tunnel. that is why i need working ipv6 firewall.
i have added both rules for testing. see eset ignorance:
as i have used eset firewall rules before, i understand that both should work as same if selected direction BOTH. only one rule must be needed. But this didnt solve anything. since the problem is localhost connection is being blocked. and firewall rules are ignored. eset does not apply it set firewall rule. Only if in interactive mode i set allow temporaly for processID.
i would say. teredo or any other tunnel mechanism is fine if you have a WORKING firewall with ipv6 support as eset is supposed to as advertised. it is only insecure if you believe your NAT makes you secure, tunnel passes forwarding through.
eset does block any local connection i cannot even reach my local webserver Environment, it's blocked. cannot browse to from chrome. see screenshot.
eset does interpret ::1 as unknown device. see "firewallproblem window" right bottom corner. it reads "unblocked" in the same time it says in detail, that no rule was applied. if i remove exclusion rule, the "unblock button" is back enabled ... eset 10 is very buggy. will this be patched or i have to only solution downgrade back to eset 9?
please note, i did a mistake in error report translation, i said training mode instead interactive mode. interactive mode gives the dialog box to allow remember connections.