What's new

x3mRouting Empty ipset with dnsmasq, works fine with ASN Method

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Mikii

Regular Contributor
Hi. I just started using x3mRouting, so I am a Newbie here. I got it to work just fine with ASN Method, but if I try the dnsmasq= method I get an empty IPSET:

what am I missing? any help would be much appreciated.

for example:

Code:
sh /jffs/scripts/x3mRouting/x3mRouting.sh 1 0 BBC dnsmasq=bbc.co.uk,bbc.com,bbc.gscontxt.net ,bbci.co.uk,bbctvapps.co.uk,ssl-bbcsmarttv.2cnt.net

(x3mRouting.sh): 27259 Starting Script Execution 1 0 BBC dnsmasq=bbc.co.uk,bbc.com,bbc.gscontxt.net,bbci.co.uk,bbctvapps.co.uk,ssl-bbcsmarttv.2cnt.net
Done.

(x3mRouting.sh): 27259 IPSET created: BBC hash:net family inet hashsize 1024 maxelem 65536
(x3mRouting.sh): 27259 CRON schedule created: #BBC# '0 2 * * * ipset save BBC'
(x3mRouting.sh): 27259 Selective Routing Rule via WAN created for BBC fwmark 0x8000/0x8000
(x3mRouting.sh): 27259 iptables -t mangle -D PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x8000/0x8000 2>/dev/null added to /jffs/scripts/x3mRouting/vpnclient1-route-up
(x3mRouting.sh): 27259 iptables -t mangle -A PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x8000/0x8000 added to /jffs/scripts/x3mRouting/vpnclient1-route-up
(x3mRouting.sh): 27259 iptables -t mangle -D PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x8000/0x8000 2>/dev/null added to /jffs/scripts/x3mRouting/vpnclient1-route-pre-down
(x3mRouting.sh): 27259 sh /jffs/scripts/x3mRouting/x3mRouting.sh 1 0 BBC dnsmasq=bbc.co.uk,bbc.com,bbc.gscontxt.net,bbci.co.uk,bbctvapps.co.uk,ssl-bbcsmarttv.2cnt.net added to /jffs/scripts/nat-start
(x3mRouting.sh): 27259 Completed Script Execution

liststats would return:
BBC - 0.

here's the ipset:
Code:
Name: BBC
Type: hash:net
Revision: 6
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 316
References: 1
Number of entries: 0
Members:

Here's the /jffs/configs/dnsmasq.conf.add after running the bcc code:

Code:
log-async
log-queries
log-facility.....  [(can't post the rest of the code, cloud fare blocks it!)]
ipset=/bbc.co.uk/bbc.com/bbc.gscontxt.net/bbci.co.uk/bbctvapps.co.uk/ssl-bbcsmarttv.2cnt.net/BBC
 
Last edited:
AFAIK, that software is no longer under developed and has known issues w/ more recent Merlin firmware. Use at your own risk.
 
I wouldn't call it app-based as much as domain-based. To my knowledge, that software was unique in its ability to route at the domain level. Although the basic concept is a rather simple one involving the use of DNSMasq, ipset (hash tables), and some firewall rules. What x3mRouting did is bring it to a much higher level, w/ utilities and other features beyond those basic elements.

I wrote a very similar but much more basic script for Merlin some time ago, with the sole purpose of routing traffic that would normally be routed over the OpenVPN client, back to the WAN. It's primarily for users who need to route their streaming content for Netflix, Amazon Prime, etc., over the WAN to avoid blocking by the content provider.


Again, it's targeted for that specific purpose, but could be the basis for a more generalized solution w/ additional work.
 
So I tested the DNSMASQ method and it seems to be working for me. I had to have Accept DNS Configuration set to Disabled for it to work under my OpenVPN Client Settings.
 
I wouldn't call it app-based as much as domain-based. To my knowledge, that software was unique in its ability to route at the domain level. Although the basic concept is a rather simple one involving the use of DNSMasq, ipset (hash tables), and some firewall rules. What x3mRouting did is bring it to a much higher level, w/ utilities and other features beyond those basic elements.

I wrote a very similar but much more basic script for Merlin some time ago, with the sole purpose of routing traffic that would normally be routed over the OpenVPN client, back to the WAN. It's primarily for users who need to route their streaming content for Netflix, Amazon Prime, etc., over the WAN to avoid blocking by the content provider.


Again, it's targeted for that specific purpose, but could be the basis for a more generalized solution w/ additional work.

Right, domain-based routing. Thanks you eibgrad for point out your script, I can see you put a lot of work into it. Right now x3mRouting seems to be working for me with ASN, but it is good to know there are alternatives out there.

I just wish that when an app or script becomes obsolete, the moderator would add a tag or seething on top of the forum to avoid new user installing it thinking it is still up-to-date....
 
So I tested the DNSMASQ method and it seems to be working for me. I had to have Accept DNS Configuration set to Disabled for it to work under my OpenVPN Client Settings.

thanks for the suggestion, I tried disabling Accept DNS Configuration but that did not help in my case.
 
Right, domain-based routing. Thanks you eibgrad for point out your script, I can see you put a lot of work into it. Right now x3mRouting seems to be working for me with ASN, but it is good to know there are alternatives out there.

I just wish that when an app or script becomes obsolete, the moderator would add a tag or seething on top of the forum to avoid new user installing it thinking it is still up-to-date....
To be honest idk what I’m gonna do when that script stops working. It’s one of the best scripts. I hope someone takes it over. So far x3mrouting is still working on the latest Merlin.
 
I just wish that when an app or script becomes obsolete, the moderator would add a tag or seething on top of the forum to avoid new user installing it thinking it is still up-to-date....

I'm trying to be as super delicate as possible here.

Fact is, no one knows what's up w/ the author since they have NOT been heard from in quite some time, perhaps as much as a year ago. They are NOT even listed as a member on this forum anymore. So I think it's a case of everyone hoping for the best, but fearing the worst. And as you might imagine, you're dealing w/ a sensitive topic when it comes to messing w/ someone else's intellectual property.

This is always the risk w/ any of this stuff, from the firmware to the AddOns. Sometimes developers just lose interest and move on, sometimes w/ much fanfair, other times w/ no further commentary. And then sometimes …
 
thanks for the suggestion, I tried disabling Accept DNS Configuration but that did not help in my case.
The reason to disable accept DNS configuration is to stop VPN client from using your VPN provider DNS, thus bypassing your router DNS. Ideally, you want your VPN client devices DNS request to use router dnsmasq. That is where ipset will be able to add the entries. Can you try tail -f dnsmasq.log in /opt/var/log directory and then run your bbc program and check the logs?

Here is a sample of the output:
Code:
Apr 28 16:40:02 dnsmasq[8170]: 49 192.168.1.24/58612 query[A] nrdp.prod.ftl.netflix.com from 192.168.1.24
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 reply nrdp51-appboot.netflix.com is <CNAME>
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 reply appboot.netflix.com is <CNAME>
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 reply appboot.dradis.netflix.com is <CNAME>
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 ipset add Netflix 52.89.18.61 appboot.us-west-2.origin.prodaa.netflix.com
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 reply appboot.us-west-2.origin.prodaa.netflix.com is 52.89.18.61
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 ipset add Netflix 34.218.179.120 appboot.us-west-2.origin.prodaa.netflix.com
Apr 28 16:40:02 dnsmasq[8170]: 27 192.168.1.24/55463 reply appboot.us-west-2.origin.prodaa.netflix.com is 34.218.179.120
 
Thank you for putting me on the right direction chongnt !
After actually running the BBC app, the IPset got populated!
No-one said that you need to run the BBC app after issuing the x3mRouting.sh with dnsmasq command!!!
 
Hi again. I still cannot get BBC to be routed thought client vpn 5.

how should I set the client option "Redirect Internet traffic through tunnel" ?

here's some logs in case someone can help:

Code:
/tmp/mnt/MicUSB/entware/var/log# x3mRouting ALL 5 BBC asnum=AS2818,AS31459
(x3mRouting): 17147 Starting Script Execution ALL 5 BBC asnum=AS2818,AS31459
(x3mRouting): 17147 Created fwmark 0x3000/0x3000
(x3mRouting): 17147 IPSET created: BBC hash:net family inet hashsize 1024 maxelem 65536
(x3mRouting): 17147 Selective Routing Rule via VPN Client 5 created for BBC fwmark 0x3000/0x3000
(x3mRouting): 17147 iptables -t mangle -D PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x3000/0x3000 2>/dev/null added to /jffs/scripts/x3mRouting/vpnclient5-route-up
(x3mRouting): 17147 iptables -t mangle -A PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x3000/0x3000 added to /jffs/scripts/x3mRouting/vpnclient5-route-up
(x3mRouting): 17147 iptables -t mangle -D PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x3000/0x3000 2>/dev/null added to /jffs/scripts/x3mRouting/vpnclient5-route-pre-down
(x3mRouting): 17147 sh /jffs/scripts/x3mRouting/x3mRouting.sh ALL 5 BBC asnum=AS2818,AS31459 added to /jffs/scripts/nat-start
(x3mRouting): 17147 Completed Script Execution


Code:
Jul 23 21:03:10 dnsmasq[14313]: reply r.bbci.co.uk is <CNAME>
Jul 23 21:03:10 dnsmasq[14313]: reply r.bbci.co.uk.pri.bbci.co.uk is <CNAME>
Jul 23 21:03:10 dnsmasq[14313]: reply uk.r.bbci.co.uk.pri.bbci.co.uk is 212.58.244.39
Jul 23 21:03:10 dnsmasq[14313]: reply uk.r.bbci.co.uk.pri.bbci.co.uk is 212.58.249.201
Jul 23 21:03:11 dnsmasq[14313]: query[A] vod-dash-uk.live.cf.md.bbci.co.uk from 192.168.1.150
Jul 23 21:03:11 dnsmasq[14313]: forwarded vod-dash-uk.live.cf.md.bbci.co.uk to 85.38.28.3
Jul 23 21:03:11 dnsmasq[14313]: reply vod-dash-uk.live.cf.md.bbci.co.uk is 108.139.239.231
Jul 23 21:03:11 dnsmasq[14313]: query[A] kinesis.eu-west-1.amazonaws.com from 192.168.1.42
Jul 23 21:03:11 dnsmasq[14313]: forwarded kinesis.eu-west-1.amazonaws.com to 85.38.28.3
Jul 23 21:03:11 dnsmasq[14313]: reply kinesis.eu-west-1.amazonaws.com is 99.80.34.164
Jul 23 21:03:14 dnsmasq[14313]: query[A] mm.bidi.bbc.co.uk from 192.168.1.150
Jul 23 21:03:14 dnsmasq[14313]: forwarded mm.bidi.bbc.co.uk to 85.38.28.3
Jul 23 21:03:14 dnsmasq[14313]: reply mm.bidi.bbc.co.uk is <CNAME>
Jul 23 21:03:14 dnsmasq[14313]: reply matchmaker.live.md.bbc.co.uk is <CNAME>
Jul 23 21:03:14 dnsmasq[14313]: reply matchmaker.live.a612ae212abeaf97.xhst.bbci.co.uk is <CNAME>
Jul 23 21:03:14 dnsmasq[14313]: reply live-compo-qkdrft3n54j1-1326475104.eu-west-1.elb.amazonaws.com is 54.73.104.248
Jul 23 21:03:14 dnsmasq[14313]: reply live-compo-qkdrft3n54j1-1326475104.eu-west-1.elb.amazonaws.com is 63.32.67.222
Jul 23 21:03:14 dnsmasq[14313]: reply live-compo-qkdrft3n54j1-1326475104.eu-west-1.elb.amazonaws.com is 52.31.238.161
Jul 23 21:03:15 dnsmasq[14313]: query[A] b2-rbsov-bbc.live.bidi.net.uk from 192.168.1.150
Jul 23 21:03:15 dnsmasq[14313]: forwarded b2-rbsov-bbc.live.bidi.net.uk to 85.38.28.3
Jul 23 21:03:15 dnsmasq[14313]: reply b2-rbsov-bbc.live.bidi.net.uk is 212.58.227.226
Jul 23 21:03:15 dnsmasq[14313]: query[A] vod-sub-uk-live.akamaized.net from 192.168.1.150
Jul 23 21:03:15 dnsmasq[14313]: forwarded vod-sub-uk-live.akamaized.net to 85.38.28.3
Jul 23 21:03:16 dnsmasq[14313]: reply vod-sub-uk-live.akamaized.net is <CNAME>
Jul 23 21:03:16 dnsmasq[14313]: reply a1670.w10.akamai.net is 173.222.107.89
Jul 23 21:03:16 dnsmasq[14313]: reply a1670.w10.akamai.net is 173.222.107.81
Jul 23 21:03:19 dnsmasq[14313]: query[A] vod-dash-uk-live.akamaized.net from 192.168.1.150
Jul 23 21:03:19 dnsmasq[14313]: forwarded vod-dash-uk-live.akamaized.net to 85.38.28.3
Jul 23 21:03:19 dnsmasq[14313]: reply vod-dash-uk-live.akamaized.net is <CNAME>
Jul 23 21:03:19 dnsmasq[14313]: reply a2.w10.akamai.net is 173.222.107.84
Jul 23 21:03:19 dnsmasq[14313]: reply a2.w10.akamai.net is 173.222.107.79

and:

Code:
ip route show
85.38.28.2 via 192.168.100.1 dev ppp0  metric 1
85.38.28.3 via 192.168.100.1 dev ppp0  metric 1
192.168.100.1 dev ppp0  proto kernel  scope link
10.24.0.114 dev tun11  proto kernel  scope link  src 10.24.0.113
192.168.1.0/24 dev br0  proto kernel  scope link  src 192.168.1.1
10.121.230.0/23 dev tun15  proto kernel  scope link  src 10.121.230.66
169.254.0.0/16 dev eth0  proto kernel  scope link  src 169.254.201.171
127.0.0.0/8 dev lo  scope link
default via 192.168.100.1 dev ppp0

BBC ipset is:
Code:
Name: BBC
Type: hash:net
Revision: 6
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 652
References: 1
Number of entries: 6
Members:
212.58.224.0/19
132.185.0.0/16
132.185.224.0/20
132.185.112.0/20
212.58.230.0/24
132.185.128.0/20
 
Last edited:
Hi again. I still cannot get BBC to be routed thought client vpn 5.

how should I set the client option "Redirect Internet traffic through tunnel" ?

here's some logs in case someone can help:

Code:
/tmp/mnt/MicUSB/entware/var/log# x3mRouting ALL 5 BBC asnum=AS2818,AS31459
(x3mRouting): 17147 Starting Script Execution ALL 5 BBC asnum=AS2818,AS31459
(x3mRouting): 17147 Created fwmark 0x3000/0x3000
(x3mRouting): 17147 IPSET created: BBC hash:net family inet hashsize 1024 maxelem 65536
(x3mRouting): 17147 Selective Routing Rule via VPN Client 5 created for BBC fwmark 0x3000/0x3000
(x3mRouting): 17147 iptables -t mangle -D PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x3000/0x3000 2>/dev/null added to /jffs/scripts/x3mRouting/vpnclient5-route-up
(x3mRouting): 17147 iptables -t mangle -A PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x3000/0x3000 added to /jffs/scripts/x3mRouting/vpnclient5-route-up
(x3mRouting): 17147 iptables -t mangle -D PREROUTING -i br0 -m set --match-set BBC dst -j MARK --set-mark 0x3000/0x3000 2>/dev/null added to /jffs/scripts/x3mRouting/vpnclient5-route-pre-down
(x3mRouting): 17147 sh /jffs/scripts/x3mRouting/x3mRouting.sh ALL 5 BBC asnum=AS2818,AS31459 added to /jffs/scripts/nat-start
(x3mRouting): 17147 Completed Script Execution


Code:
Jul 23 21:03:10 dnsmasq[14313]: reply r.bbci.co.uk is <CNAME>
Jul 23 21:03:10 dnsmasq[14313]: reply r.bbci.co.uk.pri.bbci.co.uk is <CNAME>
Jul 23 21:03:10 dnsmasq[14313]: reply uk.r.bbci.co.uk.pri.bbci.co.uk is 212.58.244.39
Jul 23 21:03:10 dnsmasq[14313]: reply uk.r.bbci.co.uk.pri.bbci.co.uk is 212.58.249.201
Jul 23 21:03:11 dnsmasq[14313]: query[A] vod-dash-uk.live.cf.md.bbci.co.uk from 192.168.1.150
Jul 23 21:03:11 dnsmasq[14313]: forwarded vod-dash-uk.live.cf.md.bbci.co.uk to 85.38.28.3
Jul 23 21:03:11 dnsmasq[14313]: reply vod-dash-uk.live.cf.md.bbci.co.uk is 108.139.239.231
Jul 23 21:03:11 dnsmasq[14313]: query[A] kinesis.eu-west-1.amazonaws.com from 192.168.1.42
Jul 23 21:03:11 dnsmasq[14313]: forwarded kinesis.eu-west-1.amazonaws.com to 85.38.28.3
Jul 23 21:03:11 dnsmasq[14313]: reply kinesis.eu-west-1.amazonaws.com is 99.80.34.164
Jul 23 21:03:14 dnsmasq[14313]: query[A] mm.bidi.bbc.co.uk from 192.168.1.150
Jul 23 21:03:14 dnsmasq[14313]: forwarded mm.bidi.bbc.co.uk to 85.38.28.3
Jul 23 21:03:14 dnsmasq[14313]: reply mm.bidi.bbc.co.uk is <CNAME>
Jul 23 21:03:14 dnsmasq[14313]: reply matchmaker.live.md.bbc.co.uk is <CNAME>
Jul 23 21:03:14 dnsmasq[14313]: reply matchmaker.live.a612ae212abeaf97.xhst.bbci.co.uk is <CNAME>
Jul 23 21:03:14 dnsmasq[14313]: reply live-compo-qkdrft3n54j1-1326475104.eu-west-1.elb.amazonaws.com is 54.73.104.248
Jul 23 21:03:14 dnsmasq[14313]: reply live-compo-qkdrft3n54j1-1326475104.eu-west-1.elb.amazonaws.com is 63.32.67.222
Jul 23 21:03:14 dnsmasq[14313]: reply live-compo-qkdrft3n54j1-1326475104.eu-west-1.elb.amazonaws.com is 52.31.238.161
Jul 23 21:03:15 dnsmasq[14313]: query[A] b2-rbsov-bbc.live.bidi.net.uk from 192.168.1.150
Jul 23 21:03:15 dnsmasq[14313]: forwarded b2-rbsov-bbc.live.bidi.net.uk to 85.38.28.3
Jul 23 21:03:15 dnsmasq[14313]: reply b2-rbsov-bbc.live.bidi.net.uk is 212.58.227.226
Jul 23 21:03:15 dnsmasq[14313]: query[A] vod-sub-uk-live.akamaized.net from 192.168.1.150
Jul 23 21:03:15 dnsmasq[14313]: forwarded vod-sub-uk-live.akamaized.net to 85.38.28.3
Jul 23 21:03:16 dnsmasq[14313]: reply vod-sub-uk-live.akamaized.net is <CNAME>
Jul 23 21:03:16 dnsmasq[14313]: reply a1670.w10.akamai.net is 173.222.107.89
Jul 23 21:03:16 dnsmasq[14313]: reply a1670.w10.akamai.net is 173.222.107.81
Jul 23 21:03:19 dnsmasq[14313]: query[A] vod-dash-uk-live.akamaized.net from 192.168.1.150
Jul 23 21:03:19 dnsmasq[14313]: forwarded vod-dash-uk-live.akamaized.net to 85.38.28.3
Jul 23 21:03:19 dnsmasq[14313]: reply vod-dash-uk-live.akamaized.net is <CNAME>
Jul 23 21:03:19 dnsmasq[14313]: reply a2.w10.akamai.net is 173.222.107.84
Jul 23 21:03:19 dnsmasq[14313]: reply a2.w10.akamai.net is 173.222.107.79

and:

Code:
ip route show
85.38.28.2 via 192.168.100.1 dev ppp0  metric 1
85.38.28.3 via 192.168.100.1 dev ppp0  metric 1
192.168.100.1 dev ppp0  proto kernel  scope link
10.24.0.114 dev tun11  proto kernel  scope link  src 10.24.0.113
192.168.1.0/24 dev br0  proto kernel  scope link  src 192.168.1.1
10.121.230.0/23 dev tun15  proto kernel  scope link  src 10.121.230.66
169.254.0.0/16 dev eth0  proto kernel  scope link  src 169.254.201.171
127.0.0.0/8 dev lo  scope link
default via 192.168.100.1 dev ppp0

BBC ipset is:
Code:
Name: BBC
Type: hash:net
Revision: 6
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 652
References: 1
Number of entries: 6
Members:
212.58.224.0/19
132.185.0.0/16
132.185.224.0/20
132.185.112.0/20
212.58.230.0/24
132.185.128.0/20

What is your current "Redirect Internet traffic through tunnel" setting?
Note that if you are using latest Merlin version with VPN Director, do not use x3mRouting option 2. Use x3mRouting option 3 instead.

Can you run these commands to verify the rules are created properly and any packets hitting the rules?
Code:
ip rule
iptables -nvL PREROUTING -t mangle --line
 
after several reboots and trials, I I got it to work yesterday .... but now it is not working anymore. Will try reboot etc.

"Redirect Internet traffic through tunnel" was my question too.
I now have two VPNs active, "Redirect Internet traffic through tunnel" is set to VPN director, but VPN director has no rules at all.

"Accept DNS Configuration" is set to disabled.

I installed with option 3, and here's the current results:

Code:
ASUSWRT-Merlin RT-AC88U 386.7_0 Wed Jun 22 18:47:22 UTC 2022

Michele@RT-AC88U-72D8:/tmp/home/root# ip rule
0:    from all lookup local
9990:    from all fwmark 0x8000/0x8000 lookup main
9991:    from all fwmark 0x3000/0x3000 lookup ovpnc5
32766:    from all lookup main
32767:    from all lookup default

Code:
Michele@RT-AC88U-72D8:/tmp/home/root# iptables -nvL PREROUTING -t mangle --line

Chain PREROUTING (policy ACCEPT 204K packets, 72M bytes)
num   pkts bytes target     prot opt in     out     source               destination      
1      152  8627 MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set RAIPLAY dst MARK or 0x8000
2     8181  777K MARK       all  --  br0    *       0.0.0.0/0            0.0.0.0/0            match-set BBC dst MARK or 0x3000

this sends Raiplay through the direct connection (which works just fine) and BBC through the vpn5

(edit):
after restarting vpn5, it seems to be working again. Gotta do more tests in the following days and adding more rules.
Question: can VPN director rules and x3mRouting rules co-exists?
I was thinking of setting a set of x3mRouting rules for VPN1 and 2, and then set a final VPN director rule for VPN5. Would this work?

thank you!
 
Last edited:
mmm.... I seem to be getting inconsistent results. Sometimes some show play fine on BBC player, but if I change show I get the "we cannot play this show at this moment. Try quitting the app and restart" message.
I do not know if this is due to the VPN or to the BBC ip table being incomplete?

Code:
sh /jffs/scripts/x3mRouting/x3mRouting.sh ALL 5 BBC dnsmasq=bbc.co.uk,bbc.com,bbc.gscontxt.net,bbci.co.uk,bbctvapps.co.uk,ssl-bbcsmarttv.2cnt.net
 
mmm.... I seem to be getting inconsistent results. Sometimes some show play fine on BBC player, but if I change show I get the "we cannot play this show at this moment. Try quitting the app and restart" message.
I do not know if this is due to the VPN or to the BBC ip table being incomplete?

Code:
sh /jffs/scripts/x3mRouting/x3mRouting.sh ALL 5 BBC dnsmasq=bbc.co.uk,bbc.com,bbc.gscontxt.net,bbci.co.uk,bbctvapps.co.uk,ssl-bbcsmarttv.2cnt.net
x3mRouting option 3 and VPN Director can co-exists. Your iptables output earlier seems ok. However, some program may detect certain VPN provider IP range as they tends to have some sort of geo-blocking.
 
Thank for confirming I am on the right path, I'll keep testing with other UK channels and different VPNs providers for a while.
 

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