I was wondering how long does it take for the routing tables to update on the internet? I have setup a 44.108.2.12 as a test machine. My BGP has been approved.
I am able to surf the web with no issues, but here still seems to be no route to the ip address. It seems to stop at : sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50]
Tracing route to bbs.n5eqo.ampr.org [44.108.2.12] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.1] 2 2 ms 1 ms 1 ms 108-196-208-1.lightspeed.nworla.sbcglobal.net [108.196.208.1] 3 * * * Request timed out. 4 18 ms 15 ms 15 ms 12.123.239.110 5 15 ms 15 ms 15 ms 12.122.28.29 6 19 ms 15 ms 15 ms attga402igs.ip.att.net [12.122.117.121] 7 13 ms 14 ms 16 ms 4.68.62.225 8 * * * Request timed out. 9 53 ms 53 ms 53 ms CENIC.ear1.LosAngeles1.Level3.net [4.35.156.66] 10 55 ms 57 ms 54 ms dc-lax-agg8--lax-agg6-100ge-2.cenic.net [137.164.11.7] 11 55 ms 55 ms 54 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 12 56 ms 55 ms 55 ms dc-sdg-agg4--tus-agg8-300g.cenic.net [137.164.11.85] 13 63 ms 55 ms 55 ms dc-ucsd-100ge--sdg-agg4.cenic.net [137.164.23.177] 14 55 ms 54 ms 54 ms nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 15 55 ms 55 ms 55 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 16 * * * Request timed out. 17 * * * Request timed out.
Any help would be appreciated.
73 de Angelo
Usually quite quickly once your upstream advertises it. You can look at lg.he.net or any other number of looking glasses to see the state of the Internet table. If I look for your /24, there is no specific announcement for it. You might want to check with whomever you're peering with that they are allowing your AS announcement out.
Jason N8EI
-----Original Message----- From: 44Net 44net-bounces+jason=mfamily.org@mailman.ampr.org On Behalf Of Angelo via 44Net Sent: Saturday, January 30, 2021 12:20 PM To: lleachii--- via 44Net 44net@mailman.ampr.org Cc: Angelo n5uxt@hotmail.com; joshua johnson ibjosh1985@gmail.com Subject: [44net] BGP
I was wondering how long does it take for the routing tables to update on the internet? I have setup a 44.108.2.12 as a test machine. My BGP has been approved.
I am able to surf the web with no issues, but here still seems to be no route to the ip address. It seems to stop at : sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50]
Tracing route to bbs.n5eqo.ampr.org [44.108.2.12] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.1] 2 2 ms 1 ms 1 ms 108-196-208-1.lightspeed.nworla.sbcglobal.net [108.196.208.1] 3 * * * Request timed out. 4 18 ms 15 ms 15 ms 12.123.239.110 5 15 ms 15 ms 15 ms 12.122.28.29 6 19 ms 15 ms 15 ms attga402igs.ip.att.net [12.122.117.121] 7 13 ms 14 ms 16 ms 4.68.62.225 8 * * * Request timed out. 9 53 ms 53 ms 53 ms CENIC.ear1.LosAngeles1.Level3.net [4.35.156.66] 10 55 ms 57 ms 54 ms dc-lax-agg8--lax-agg6-100ge-2.cenic.net [137.164.11.7] 11 55 ms 55 ms 54 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 12 56 ms 55 ms 55 ms dc-sdg-agg4--tus-agg8-300g.cenic.net [137.164.11.85] 13 63 ms 55 ms 55 ms dc-ucsd-100ge--sdg-agg4.cenic.net [137.164.23.177] 14 55 ms 54 ms 54 ms nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 15 55 ms 55 ms 55 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 16 * * * Request timed out. 17 * * * Request timed out.
Any help would be appreciated.
73 de Angelo
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
It should be near instantaneous once your service provider sets everything up. Your traceroute is going to UCSD because there is no more specific route being advertised. Asking why that is, is a question for your service provider. They are the folks that actually make it work.
Try looking at a traceroute to 44.48.24.30, I think you will see the difference.
I found about 24 hours for routes to show. Mine seemed to update 00:00 UK time but it seemed to take some time.
2E0EMO
On Sat, 30 Jan 2021 at 19:13, Dave Gingrich via 44Net < 44net@mailman.ampr.org> wrote:
It should be near instantaneous once your service provider sets everything up. Your traceroute is going to UCSD because there is no more specific route being advertised. Asking why that is, is a question for your service provider. They are the folks that actually make it work.
Try looking at a traceroute to 44.48.24.30, I think you will see the difference.
-- Dave K9DC Indianapolis
On Jan 30, 2021, at 12:20, Angelo via 44Net 44net@mailman.ampr.org
wrote:
I was wondering how long does it take for the routing tables to update
on the internet? I have setup a 44.108.2.12 as a test machine. My BGP has been approved.
I am able to surf the web with no issues, but here still seems to be no
route to the ip address. It seems to stop at : sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50]
Tracing route to bbs.n5eqo.ampr.org [44.108.2.12] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.1] 2 2 ms 1 ms 1 ms
108-196-208-1.lightspeed.nworla.sbcglobal.net [108.196.208.1]
3 * * * Request timed out. 4 18 ms 15 ms 15 ms 12.123.239.110 5 15 ms 15 ms 15 ms 12.122.28.29 6 19 ms 15 ms 15 ms attga402igs.ip.att.net [12.122.117.121] 7 13 ms 14 ms 16 ms 4.68.62.225 8 * * * Request timed out. 9 53 ms 53 ms 53 ms CENIC.ear1.LosAngeles1.Level3.net
[4.35.156.66]
10 55 ms 57 ms 54 ms dc-lax-agg8--lax-agg6-100ge-2.cenic.net
[137.164.11.7]
11 55 ms 55 ms 54 ms dc-tus-agg8--lax-agg8-300g.cenic.net
[137.164.11.83]
12 56 ms 55 ms 55 ms dc-sdg-agg4--tus-agg8-300g.cenic.net
[137.164.11.85]
13 63 ms 55 ms 55 ms dc-ucsd-100ge--sdg-agg4.cenic.net
[137.164.23.177]
14 55 ms 54 ms 54 ms nodem-core-6807-vlan2767-gw.ucsd.edu
[132.239.254.61]
15 55 ms 55 ms 55 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu
[132.239.255.50]
16 * * * Request timed out. 17 * * * Request timed out.
Any help would be appreciated. 73 de Angelo
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Chris , Jason, Andrew and Dave,
Thanks so much for all your replies. It has helped a great deal.
Angelo
On 1/30/2021 1:12 PM, Dave Gingrich via 44Net wrote:
It should be near instantaneous once your service provider sets everything up. Your traceroute is going to UCSD because there is no more specific route being advertised. Asking why that is, is a question for your service provider. They are the folks that actually make it work.
Try looking at a traceroute to 44.48.24.30, I think you will see the difference.
Convergence time is about 3 - 4 minutes to most of the internet at the moment. I have noticed between most of the peers at one of the IX's in Australia and Cogent's table there's about 30 sec in table versions. If it takes 10 minutes somethings not working as it should.
Matt.
On 31/1/21 4:20 am, Angelo via 44Net wrote:
I was wondering how long does it take for the routing tables to update on the internet? I have setup a 44.108.2.12 as a test machine. My BGP has been approved.
I am able to surf the web with no issues, but here still seems to be no route to the ip address. It seems to stop at : sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50]
Tracing route to bbs.n5eqo.ampr.org [44.108.2.12] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dsldevice.attlocal.net [192.168.1.1] 2 2 ms 1 ms 1 ms 108-196-208-1.lightspeed.nworla.sbcglobal.net [108.196.208.1] 3 * * * Request timed out. 4 18 ms 15 ms 15 ms 12.123.239.110 5 15 ms 15 ms 15 ms 12.122.28.29 6 19 ms 15 ms 15 ms attga402igs.ip.att.net [12.122.117.121] 7 13 ms 14 ms 16 ms 4.68.62.225 8 * * * Request timed out. 9 53 ms 53 ms 53 ms CENIC.ear1.LosAngeles1.Level3.net [4.35.156.66] 10 55 ms 57 ms 54 ms dc-lax-agg8--lax-agg6-100ge-2.cenic.net [137.164.11.7] 11 55 ms 55 ms 54 ms dc-tus-agg8--lax-agg8-300g.cenic.net [137.164.11.83] 12 56 ms 55 ms 55 ms dc-sdg-agg4--tus-agg8-300g.cenic.net [137.164.11.85] 13 63 ms 55 ms 55 ms dc-ucsd-100ge--sdg-agg4.cenic.net [137.164.23.177] 14 55 ms 54 ms 54 ms nodem-core-6807-vlan2767-gw.ucsd.edu [132.239.254.61] 15 55 ms 55 ms 55 ms sdsc-7710-7--mcore-vl2995-p2p.ucsd.edu [132.239.255.50] 16 * * * Request timed out. 17 * * * Request timed out.
Any help would be appreciated.
73 de Angelo
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net