pixelserv-tls not interception about pixelserv-tls HOT 9 CLOSED

Please let me know if you need any other data, have spet two days on figuring out what could be the issue but couldn't , i followed your guide to use pihole with pixelserv-tls and some guide to use pihole with pivpn

Thank you for the excellent program.

from pixelserv-tls.

pixelserv must not listen on IP 0.0.0.0
This is not an IP Adresse because it's a network address.

from pixelserv-tls.

i have used other ip address also with same result like 10.128.0.6 in my case and simultaneously changinf the ip in pihole ipv4

from pixelserv-tls.

or can you please tell which ip i should based on following result

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1460
        inet 10.128.0.6  netmask 255.255.255.255  broadcast 10.128.0.6
        inet6 fe80::4001:aff:fe80:6  prefixlen 64  scopeid 0x20<link>
        ether 42:01:0a:80:00:06  txqueuelen 1000  (Ethernet)
        RX packets 3319  bytes 883009 (862.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2513  bytes 623072 (608.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 48  bytes 4659 (4.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 48  bytes 4659 (4.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.9.0.1  netmask 255.255.255.0  destination 10.9.0.1
        inet6 fe80::1ab:3b0c:547e:d869  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10  bytes 480 (480.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun1: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.8.0.1  netmask 255.255.255.0  destination 10.8.0.1
        inet6 fe80::111a:a7a7:5dd1:2df5  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 11  bytes 528 (528.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

from pixelserv-tls.

The problem seems to be the VPN interface. As soon as you switch to a different interface the routing will not longer work.
You have on each interface a /24 network. Without setting static routes on your router you are not able to access the other networks. In addition you are using the VPN which make it almost impossible to access this.

Because of this fact I have invented the keweon project and this is working with public IP addresses. Because of this you can always access the "pixelserver". :-)

from pixelserv-tls.

I am on a debian stretch 9 with static public address. so what should i do fix this ? thank you very much in advance

from pixelserv-tls.

Just use my DNS Servers. If you want to know more then ask Google or XDA.

1. 213.239.207.143 and 107.191.55.215

2. Get the Root Cerificate from:
   https://pki.keweon.center

3. DNS over HTTPS and DNS over TLS Server
   DoT address: dot.asecdns.com
   DoH address: https://doh.asecdns.com/nebulo

4. The public "pixelserver" is adblock.keweon.center with IP address 5.189.169.177

Almost the entire systems are located within Germany.

Current blacklist Database contains 56 Million entries

Have fun 😉

from pixelserv-tls.

i am interested in solution specific to my setup.

from pixelserv-tls.

That's too much routing efforts and on the other hand I have seriously no clue about your VPN and required settings. To do this via a chat is almost not possible. Sorry...

from pixelserv-tls.