TrueNas Core network configuration issue (“Communication prohibited by filter”)

[flofloflo]

Hi,

I've updated my FreeNAS system to TrueNAS Core 12.0 two days ago.
Unfortunately since then I cannot connect to the internet any more. As I couldn't find the issue I tried a completely fresh install, didn't help either.

If I try to ping e.g. github.com I get the error msg:

Code:

ping: cannot resolve github.com: Host name lookup failure

The default gateway setting is the same as on my windows PC in the same network where everything works just fine.
The IP is set out of the DHCP range from my router.

When using the IP address the ping on my PC shows me for github.com, I get the following error msg:

Code:

PING 140.82.121.4 (140.82.121.4): 56 data bytes
36 bytes from 192.0.0.2: Communication prohibited by filter
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 0054 e182   0 0000  3f  01 215e 192.168.178.201  140.82.121.4

Here are my general network settings:

And here are my interface settings:

Can anyone help me with this issue?

Best, Florian

 

[Patrick M. Hausen]

You are missing a nameserver entry in the general settings.

Not sure about that filter though, but first things first ...

 

[flofloflo]

I added two nameserver entries from this list: https://de.ccm.net/faq/1431-dns-server-deutscher-internetanbieter.
Didn't change anything.
Edit: meaning the same result on the same tests as above.

 

[Patrick M. Hausen]

Put in your default gateway or whatever your Windows system uses. And better pick a static IP address from the same network but outside your DHCP range.

Prohibited by filter is an ICMP message that says exactly that. The gateway at 192.0.0.2 is prohibiting that Traffic. Can one ping github in general at all? Some people block ICMP ...

Anyway, with the correct nameserver at least name resolution should work.

 

[flofloflo]

My windows PC uses the default gateway. I've put that into the NAS, too. Now I also get the filter issue with the url.
I already have a static IP outside of the DHCP range, my wording was a little misleading there.

I can ping github.com from my PC. I also get the same error for other destinations, like google.com or truenas.com, on my NAS, also both pingable from my PC.

I also wonder what 192.0.0.2 is ... might be in the local network as the ping (I can ping it) is only 0.5–1.2 ms from my PC. On the other hand it has to be past the router as traceroute shows the following:

Code:

root@NAS[~]# traceroute github.com
traceroute to github.com (140.82.121.4), 64 hops max, 40 byte packets
1  fritz.box (192.168.178.1)  0.403 ms  0.336 ms  0.306 ms
2  192.0.0.2 (192.0.0.2)  0.395 ms !X  0.417 ms !X  0.399 ms !X