[Freedombox-discuss] connection/firewall problem with privoxy

Aaron Ferrucci aaron.ferrucci at gmail.com
Mon Feb 27 14:51:40 UTC 2017

> Did you check if your local network connection on the freedombox is also
> in the correct firewall zone (internal)?
> --
> James

This sounds promising. I had a look. Here are my connections:

  [freedombox]$ nmcli connection
  NAME                   UUID                                  TYPE
  FreedomBox WAN         599a2458-cd6d-463a-929a-8f15cadd4260
802-3-ethernet  enp1s0
  tun0                   704fd1e0-d860-47d0-b834-0fb28cc7c4b9  tun
  FreedomBox LAN enp2s0  ede86fda-5b2b-4538-bd09-efbc89e73576
802-3-ethernet  --
  FreedomBox LAN enp3s0  d765a2a2-77e2-4a16-a894-8f6d7ce3acb0
802-3-ethernet  --

What connection is "tun0" in?

  [freedombox]$ nmcli connection show tun0 | grep zone
  connection.zone:                        --

That doesn't seem right (I assume "--" means "not assigned"). I
modified tun0's zone to "internal:

  [freedombox]$ nmcli con modify tun0 connection.zone internal
  [freedombox]$ nmcli connection show tun0 | grep zone
  connection.zone:                        internal

And the zone assignment persisted after a reboot. However! This change makes no
difference to the actual issue:

  [client computer]$ nc -v 8118
  nc: connect to port 8118 (tcp) failed: No route to host

Any other ideas?

More information about the Freedombox-discuss mailing list