Kamoj Kamoj Addon 5.5 Beta for Netgear R7800/R8900/R9000 with Voxel FW

jrbmw

Regular Contributor
Running my R7800 with Voxel V1.0.2.98SF and Kamoj V5.5b27 and I have a problem with the Vpn bypass. If I put my google chromecast on bypass the vpn to watch netflix I get the you are using an unblocker or proxy.The ip rule shows the chromecast as bypassed and its in the bypass devices box.Netflix works fine with the vpn off.
 

jay2020

Occasional Visitor
Running my R7800 with Voxel V1.0.2.98SF and Kamoj V5.5b27 and I have a problem with the Vpn bypass. If I put my google chromecast on bypass the vpn to watch netflix I get the you are using an unblocker or proxy.The ip rule shows the chromecast as bypassed and its in the bypass devices box.Netflix works fine with the vpn off.
go back to Voxel V1.0.2.97SF and see if the issue is still there. dont forget to report back with your status/results
 

R. Gerrits

Senior Member
Running my R7800 with Voxel V1.0.2.98SF and Kamoj V5.5b27 and I have a problem with the Vpn bypass. If I put my google chromecast on bypass the vpn to watch netflix I get the you are using an unblocker or proxy.The ip rule shows the chromecast as bypassed and its in the bypass devices box.Netflix works fine with the vpn off.
so "ip rule show" has an entry like this: "from <chromecast_IP> lookup novpn" ???

and you are really sure that the chromecast still has that IP-address?

If so then the only explanation I can think of, is that somethings wrong with the routing table.
Can you check the output of "ip route show table novpn" ?
 

jrbmw

Regular Contributor
so "ip rule show" has an entry like this: "from <chromecast_IP> lookup novpn" ???

and you are really sure that the chromecast still has that IP-address?

If so then the only explanation I can think of, is that somethings wrong with the routing table.
Can you check the output of "ip route show table novpn" ?
vpn set to new york

32763: from 192.168.1.2 lookup novpn same as chromecast with google tv ip

[email protected]:/$ ip route show table novpn
default via 172.16.10.217 dev ppp0
172.16.10.217 dev ppp0 proto kernel scope link src 195.213.37.142
173.239.207.84 via 172.16.10.217 dev ppp0
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1
239.0.0.0/8 dev br0 scope link
 

R. Gerrits

Senior Member
vpn set to new york

32763: from 192.168.1.2 lookup novpn same as chromecast with google tv ip

[email protected]:/$ ip route show table novpn
default via 172.16.10.217 dev ppp0
172.16.10.217 dev ppp0 proto kernel scope link src 195.213.37.142
173.239.207.84 via 172.16.10.217 dev ppp0
192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1
239.0.0.0/8 dev br0 scope link
Looks fine to me.
Then the next guess:
You haven't enabled "Router it-self bypass VPN" -> DNS requests that chromecast makes are routed through the VPN. And your VPN provider intercepts those DNS requests and redirects it to his own DNS servers.
(chromecast asks your router; your router sends the queries towards the internet via its default route)
 

jrbmw

Regular Contributor
Looks fine to me.
Then the next guess:
You haven't enabled "Router it-self bypass VPN" -> DNS requests that chromecast makes are routed through the VPN. And your VPN provider intercepts those DNS requests and redirects it to his own DNS servers.
(chromecast asks your router; your router sends the queries towards the internet via its default route)
Enabling router it-self bypass made no difference
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top