Yes we did that earlier. Neil
Sent from my iPhone On 9 Jan 2018, at 19:06, Alan Ramsay <[email protected]<mailto:[email protected]>> wrote: I did suspect it was a Virgin issue, hence the original title. It does look like someone has put some sort of filter in place now though: root@nat:~# traceroute -I 195.2.224.253 traceroute to 195.2.224.253 (195.2.224.253), 30 hops max, 38 byte packets 1 410.xe-2-2-0.central10.pcn-bng02.plus.net<http://410.xe-2-2-0.central10.pcn-bng02.plus.net> (84.93.253.72) 12.171 ms 11.206 ms 11.483 ms 2 411.be6.pcn-ir01.plus.net<http://411.be6.pcn-ir01.plus.net> (84.93.253.75) 12.766 ms 411.be6.pcn-ir02.plus.net<http://411.be6.pcn-ir02.plus.net> (84.93.253.79) 12.085 ms 411.be6.pcn-ir01.plus.net<http://411.be6.pcn-ir01.plus.net> (84.93.253.75) 11.963 ms 3 195.99.125.136 (195.99.125.136) 11.971 ms 195.99.125.140 (195.99.125.140) 12.166 ms 195.99.125.136 (195.99.125.136) 11.925 ms 4 peer5-hu0-1-0-1.telehouse.ukcore.bt.net<http://peer5-hu0-1-0-1.telehouse.ukcore.bt.net> (195.99.127.21) 12.207 ms peer1-et-10-3-0.telehouse.ukcore.bt.net<http://peer1-et-10-3-0.telehouse.ukcore.bt.net> (62.172.103.17) 12.792 ms peer5-hu0-1-0-1.telehouse.ukcore.bt.net<http://peer5-hu0-1-0-1.telehouse.ukcore.bt.net> (195.99.127.21) 12.017 ms 5 * * * 6 te0-1-0-0.telehouse-east4.core.enta.net<http://te0-1-0-0.telehouse-east4.core.enta.net> (188.39.127.149) 12.930 ms 12.886 ms 12.602 ms 7 te0-0-0-3.man.core.enta.net<http://te0-0-0-3.man.core.enta.net> (188.39.127.183) 19.668 ms 19.745 ms 19.570 ms 8 te0-0-2-0.man-te.core.enta.net<http://te0-0-2-0.man-te.core.enta.net> (188.39.127.31) 19.564 ms 19.644 ms 19.694 ms 9 te0-0-0-0.wolv-te.core.enta.net<http://te0-0-0-0.wolv-te.core.enta.net> (188.39.127.225) 21.520 ms 21.191 ms 21.092 ms 10 ip195-2-224-253.presscomputers.net<http://ip195-2-224-253.presscomputers.net> (195.2.224.253) 19.209 ms 18.864 ms 19.504 ms root@nat:~# Many thanks to all that offered advice, and especially Neil for getting things moving in the right direction. Kind regards Alan On Tue, 9 Jan 2018 at 18:45, Neil J. McRae <[email protected]<mailto:[email protected]>> wrote: Looks like Virgin are leaking prefixes, if they see this can they take a look! But it’s not affecting connectivity but needs fixing. Cheers Neil. Sent from my iPhone On 9 Jan 2018, at 14:50, Neil J. McRae <[email protected]<mailto:[email protected]>> wrote: defiant:~ neil$ ping 188.39.202.154 PING 188.39.202.154 (188.39.202.154): 56 data bytes 64 bytes from 188.39.202.154<http://188.39.202.154>: icmp_seq=0 ttl=51 time=22.811 ms The outbound route is via our Telehouse-North Node. So works ok from BT. I’ve asked one of the team to look into it though incase there is something strange going on perhaps with our virgin border router. Can you tell me what IP address you are tracerouting from (traceroute is the worst tool for debugging IMO). Cheers, Neil. On 09/01/2018, 13:50, "uknof on behalf of Alan Ramsay" <[email protected]<mailto:[email protected]> on behalf of [email protected]<mailto:[email protected]>> wrote: Hi Simon, I really appreciate you taking the time to respond. Based on your email, I've checked from one of our customers firewalls, who's on AS2856, and see the same issue from there too, so obviously not just restricted to PlusNet as I had initially though. From the BT LG link that you've sent, it shows that from AS4500 there are only two paths - NTT-> IXReach -> here or Vodafone-> Enta -> Here. So I follow it down the chain - Vodafone's LG shows Enta -> here - and obviously further still down the chain Enta shows us as being connected to them. I've also tested from a connection on AS2529 which goes Vodafone -> Enta -> Here, and do NOT see the issue, so to me, this now looks like it's an issue at BT Thanks for pointing me in the right direction; now to see if anyone from BT notices this, or if I'll have to repost changing the subject...... On 9 January 2018 at 13:12, Beevers, Simon <[email protected]<mailto:[email protected]>> wrote: Hi Alan, I don’t believe anyone from PN is still subscribed to UKNOF, as all of the people who were (like me) have left. What I can say is that PN no longer has any public connectivity, other than BT AS2856, so you’ll need use BT’s looking glass - http://www.bt.net/looking-glass.html Kind Regards Simon From: Alan Ramsay <[email protected]<mailto:adramsay%[email protected]>> Date: Tuesday, 9 January 2018 at 13:07 To: <[email protected]<mailto:[email protected]>> Subject: [uknof] PlusNet / Virgin routing weirdness I'm seeing some routing weirdness from PlusNet xDSL connections to one of our subnets, and wondered if there was any members from PlusNet and Virgin on list who could take a look. We have a subnet 195.2.224.0/24<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F195.2.224.0%2F24&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=nABYXbyjqF1fT%2BULCDVWYJtAlKET4FCuVhplYixb%2Bko%3D&reserved=0> on AS44052 which is dual homed to EntaNet and IXReach. From a PlusNet xDSL connection, the routing to our router looks quite sensible when hitting the carrier side IP addresses that are assigned to it: EntaNet assigned address: alan-mbp:~ alanramsay$ traceroute -I 188.39.202.154 traceroute to 188.39.202.154 (188.39.202.154), 64 hops max, 72 byte packets 1 nat (172.16.10.1) 5.767 ms 3.174 ms 1.931 ms 2 410.xe-2-2-0.central10.pcn-bng02.plus.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F410.xe-2-2-0.central10.pcn-bng02.plus.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=526Buggm2MTYMa5SSg7Z87TzKQ2L8EwgcyuzZXoI%2B10%3D&reserved=0> (84.93.253.72) 17.874 ms 17.056 ms 14.640 ms 3 411.be6.pcn-ir02.plus.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F411.be6.pcn-ir02.plus.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=R6GWZA%2FD5thFaUZlvEhpVr11eaLx8sDPgN8BFJL9TWg%3D&reserved=0> (84.93.253.79) 17.152 ms 14.379 ms 17.687 ms 4 195.99.125.144 (195.99.125.144) 14.960 ms 17.165 ms 14.512 ms 5 peer1-et-10-3-0.telehouse.ukcore.bt.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpeer1-et-10-3-0.telehouse.ukcore.bt.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=RUGCbHHnnbqWPU9FFQlGrglzLKP%2FmBu5dw20Dc%2BNqWA%3D&reserved=0> (62.172.103.17) 18.485 ms 16.459 ms 14.942 ms 6 * * * 7 te0-2-0-3.interxion3.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-2-0-3.interxion3.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=EwGm9YgyLLQtAJR0fL5aYVp6fTnX3evlhs1WZqnbjt4%3D&reserved=0> (188.39.127.172) 18.420 ms 18.229 ms 17.572 ms 8 te0-0-2-0.miltonkeynes.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-0-2-0.miltonkeynes.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=GpqAah7wru%2FguwYh8VDdHxuG2PDF9%2BZ4nEiZ08KpD4M%3D&reserved=0> (188.39.127.209) 19.556 ms 18.382 ms 20.486 ms 9 te0-0-0-1.birmingham-te.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-0-0-1.birmingham-te.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=WNShxDMZvziUl6nQHm2Gz6Rd4nDdkurwwD%2FcHtaYAfU%3D&reserved=0> (188.39.127.212) 22.215 ms 30.097 ms 21.483 ms 10 te0-0-0-2.wolv-te.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-0-0-2.wolv-te.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=m9Uums%2BapqjThVi5HeMxoVMCahxm2HDxwtfvj8BFJMw%3D&reserved=0> (188.39.127.217) 22.330 ms 25.702 ms 21.107 ms 11 188-39-202-154.static.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F188-39-202-154.static.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154625372&sdata=RuDjILNUnE857uXPjCLYR%2FJyA0zSSBFGOW8N6k%2BU5fI%3D&reserved=0> (188.39.202.154) 20.173 ms 21.385 ms 20.329 ms alan-mbp:~ alanramsay$ IXReach assigned address: alan-mbp:~ alanramsay$ traceroute -I 31.217.134.34 traceroute to 31.217.134.34 (31.217.134.34), 64 hops max, 72 byte packets 1 nat (172.16.10.1) 5.455 ms 2.448 ms 2.362 ms 2 410.xe-2-2-0.central10.pcn-bng02.plus.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F410.xe-2-2-0.central10.pcn-bng02.plus.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=BkcoX1QaO6%2Faszf1DBkWnxRl02CN1yNHhxag%2FHr3ng4%3D&reserved=0> (84.93.253.72) 16.839 ms 14.814 ms 14.290 ms 3 411.be6.pcn-ir01.plus.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F411.be6.pcn-ir01.plus.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=9I9bS5PXQm6NjkutHxjgRdw1V8TisTtjtLnSWmTsb7Q%3D&reserved=0> (84.93.253.75) 15.082 ms 15.229 ms 15.825 ms 4 195.99.125.136 (195.99.125.136) 15.509 ms 15.857 ms 16.325 ms 5 62.172.103.49 (62.172.103.49) 41.430 ms 17.144 ms 15.461 ms 6 * * * 7 31.217.134.34 (31.217.134.34) 24.338 ms 21.765 ms 21.651 ms alan-mbp:~ alanramsay$ Now if we try to do a traceroute to the router directly within the advertised subnet, PlusNet seems to favour the EntaNet connection, but sends traffic to it via Virgin Media. alan-mbp:~ alanramsay$ traceroute -I 195.2.224.253 traceroute to 195.2.224.253 (195.2.224.253), 64 hops max, 72 byte packets 1 nat (172.16.10.1) 4.343 ms 2.126 ms 5.047 ms 2 410.xe-2-2-0.central10.pcn-bng02.plus.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F410.xe-2-2-0.central10.pcn-bng02.plus.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=BkcoX1QaO6%2Faszf1DBkWnxRl02CN1yNHhxag%2FHr3ng4%3D&reserved=0> (84.93.253.72) 17.572 ms 16.744 ms 13.716 ms 3 411.be6.pcn-ir02.plus.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2F411.be6.pcn-ir02.plus.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=yKq3rMIsbhTEJqBhL57xLAPHjtKjEieSGC0QtDUkqSk%3D&reserved=0> (84.93.253.79) 19.078 ms 18.111 ms 15.559 ms 4 195.99.125.140 (195.99.125.140) 15.161 ms 15.049 ms 15.472 ms 5 peer2-et-1-1-0.redbus.ukcore.bt.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpeer2-et-1-1-0.redbus.ukcore.bt.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=RdlF5lxP74GRLDReGNyG5IxKiW5tniq5Ih3XwcacvAQ%3D&reserved=0> (62.172.103.45) 15.296 ms 15.722 ms 17.498 ms 6 194.74.65.22 (194.74.65.22) 22.802 ms 27.988 ms 23.007 ms 7 * * * 8 * * * 9 * * * 10 tcl5-ic-5-ae0-0.network.virginmedia.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftcl5-ic-5-ae0-0.network.virginmedia.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=bR%2BHXhzrlDOTvsIVr9v%2BoHZPmt9GplWikEop0Dt%2FwfI%3D&reserved=0> (62.254.84.66) 28.122 ms 23.156 ms 24.506 ms 11 * * * 12 te0-2-0-3.interxion3.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-2-0-3.interxion3.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=3Hmw%2Fq6mZsapnBAuyp4m66KtCK4i4h2j5cAsupBpo5w%3D&reserved=0> (188.39.127.172) 23.327 ms 20.859 ms 21.733 ms 13 te0-0-2-0.miltonkeynes.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-0-2-0.miltonkeynes.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=RU%2FZruRP89snuNx4Y1UbCK3EXMW%2Bzhg2EVG3lKC6LHo%3D&reserved=0> (188.39.127.209) 22.365 ms 23.298 ms 25.178 ms 14 te0-0-0-1.birmingham-te.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-0-0-1.birmingham-te.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=Z%2B4WPI%2FRn3qMpn6lYhDK2YFMa9KyMOdyIufjqWKRhw0%3D&reserved=0> (188.39.127.212) 26.434 ms 27.137 ms 29.711 ms 15 te0-0-0-2.wolv-te.core.enta.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fte0-0-0-2.wolv-te.core.enta.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154635380&sdata=srMALOUSbtI2nLvHseQDHoDz7tsE8KDXvcBaS89x1ac%3D&reserved=0> (188.39.127.217) 31.469 ms 31.309 ms 28.197 ms 16 ip195-2-224-253.presscomputers.net<https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fip195-2-224-253.presscomputers.net&data=02%7C01%7C%7Cae6e8bb0371345677c3008d55761d87a%7C5f7cd26c94dd4a75aaaf9324631d31a9%7C0%7C1%7C636511000154645388&sdata=0CbrWgLeXG%2BYqdGmE5NFrLmzDf1Cs7bwsQuYzb2wIvU%3D&reserved=0> (195.2.224.253) 28.177 ms 25.894 ms 27.156 ms alan-mbp:~ alanramsay$ What would cause the traffic to go via Virgin, rather than direct - we can see when they hit the external PlusNet IP of the router it routes without going via Virgin. Any advice on how to resolve this is much appreciated. Thanks Alan Privileged/Confidential information may be contained in this Communication (which includes any attachment). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by Registered office: PCCW Global Networks (UK) plc. Suite 1, 3rd Floor, 11-12, St. James’s Square, London, SW1Y 4LB<https://maps.google.com/?q=Suite+1,+3rd+Floor,+11-12,+St.+James%E2%80%99s+Square,+London,+SW1Y+4LB&entry=gmail&source=g> reply email. Thank you.
