Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
I'm not having issues with Vultr at the moment. I did have some issues about a month ago when they had a crash in their datacenter and a VM was corrupt. Luckily it was not my router and did not have anything important on it.
(yes, I do have backups of everything important and the router ;) )
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of Toussaint OTTAVI via 44Net Sent: Friday, January 24, 2020 15:24 To: 44net@mailman.ampr.org Cc: Toussaint OTTAVI t.ottavi@bc-109.com Subject: [44net] Vultr BGP routing KO in Paris ?
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Thank you Ruben. It seems the problem is located in Paris.
I'll add the redundant BGP announcement from different operator / different location on my TODO list, HI :-)
73 de TK1BI
Le 24/01/2020 à 15:40, Ruben ON3RVH a écrit :
I'm not having issues with Vultr at the moment. I did have some issues about a month ago when they had a crash in their datacenter and a VM was corrupt. Luckily it was not my router and did not have anything important on it.
(yes, I do have backups of everything important and the router ;) )
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of Toussaint OTTAVI via 44Net Sent: Friday, January 24, 2020 15:24 To: 44net@mailman.ampr.org Cc: Toussaint OTTAVI t.ottavi@bc-109.com Subject: [44net] Vultr BGP routing KO in Paris ?
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Atlanta is ok.
Are you still able to reach your bgp peer? Or is session up but your announcement is filtered?
On Fri, Jan 24, 2020, 9:26 AM Toussaint OTTAVI via 44Net < 44net@mailman.ampr.org> wrote:
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I had similar issue in past with their ams and tokyo nodes, one time it was unrecoverable. For diagnostics, are you able to ssh to the gateway? If you are using bird then you can check with `birdc show proto all`.
On 1/24/20 10:23 PM, Toussaint OTTAVI via 44Net wrote:
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
- My gateway is up and running. I can SSH to it via its WAN address and through my tunnel.
- bird shows the iBGP session is established (see output below)
- a traceroute to my gateway 44.190.11.1 from the outside goes to San Diego
- on the gateway, a ping with a 44.190 adress (ping -I 44.190.11.253 8.8.8.8) goes nowhere
-------
birdc show proto all BIRD 1.6.3 ready. name proto table state since info vultr BGP master up 14:45:50 Established Preference: 100 Input filter: REJECT Output filter: ACCEPT Routes: 0 imported, 1 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 1 0 0 --- 1 Export withdraws: 0 --- --- --- 0 BGP state: Established Neighbor address: 169.254.169.254 Neighbor AS: 64515 Neighbor ID: 45.63.113.24 Neighbor caps: refresh restart-aware AS4 add-path-rx Session: external multihop AS4 Source address: 199.247.9.191 Hold timer: 131/180 Keepalive timer: 17/60
static1 Static master up 14:45:46 Preference: 200 Input filter: ACCEPT Output filter: REJECT Routes: 1 imported, 0 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 0 0 1 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
device1 Device master up 14:45:46 Preference: 240 Input filter: ACCEPT Output filter: REJECT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
Le 24/01/2020 à 15:44, Quan Zhou via 44Net a écrit :
I had similar issue in past with their ams and tokyo nodes, one time it was unrecoverable. For diagnostics, are you able to ssh to the gateway? If you are using bird then you can check with `birdc show proto all`.
On 1/24/20 10:23 PM, Toussaint OTTAVI via 44Net wrote:
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Looks like everything is fine on your end, but didn't propagate beyond 169.254.169.254. Should be their issue.
On 1/24/20 10:56 PM, Toussaint OTTAVI wrote:
- My gateway is up and running. I can SSH to it via its WAN address
and through my tunnel.
bird shows the iBGP session is established (see output below)
a traceroute to my gateway 44.190.11.1 from the outside goes to San
Diego
- on the gateway, a ping with a 44.190 adress (ping -I 44.190.11.253
8.8.8.8) goes nowhere
birdc show proto all BIRD 1.6.3 ready. name proto table state since info vultr BGP master up 14:45:50 Established Preference: 100 Input filter: REJECT Output filter: ACCEPT Routes: 0 imported, 1 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 1 0 0 --- 1 Export withdraws: 0 --- --- --- 0 BGP state: Established Neighbor address: 169.254.169.254 Neighbor AS: 64515 Neighbor ID: 45.63.113.24 Neighbor caps: refresh restart-aware AS4 add-path-rx Session: external multihop AS4 Source address: 199.247.9.191 Hold timer: 131/180 Keepalive timer: 17/60
static1 Static master up 14:45:46 Preference: 200 Input filter: ACCEPT Output filter: REJECT Routes: 1 imported, 0 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 0 0 1 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
device1 Device master up 14:45:46 Preference: 240 Input filter: ACCEPT Output filter: REJECT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
Le 24/01/2020 à 15:44, Quan Zhou via 44Net a écrit :
I had similar issue in past with their ams and tokyo nodes, one time it was unrecoverable. For diagnostics, are you able to ssh to the gateway? If you are using bird then you can check with `birdc show proto all`.
On 1/24/20 10:23 PM, Toussaint OTTAVI via 44Net wrote:
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Le 24/01/2020 à 16:22, Quan Zhou a écrit :
Looks like everything is fine on your end, but didn't propagate beyond 169.254.169.254. Should be their issue.
15:03 Ticket submitted to Vultr support 15:11 Acknowledgement, ticket is forwarded to the right team 15:42 Mail from the tech, he's investigating the problem 16:15 Ping is UP
The problem was a side effect of their network upgrade in Paris.
I am always impressed by Vultr support responsiveness and efficiency for a $5/month product. With the same ratio, my business providers should solve my problems in less than one second, HI :-D
73 de TK1BI
here's a traceroute from me and it seems there is no tunnel to you my network is 44.56.53.1/28
I have a PBX in the NJ vultr node and its ok
73 leon wa4zlw
C:>tracert 44.190.11.1
Tracing route to 44.190.11.1 over a maximum of 30 hops
1 1 ms 1 ms <1 ms t30.wa4zlw.org [10.195.10.3] 2 1 ms 1 ms 1 ms core100.wa4zlw.ampr.org [44.56.53.1] 3 * * * Request timed out. 4 10 ms 10 ms 10 ms gateway-t0-0-0-11-flt3blocal1.flt.ptd.net [207.44.126.57] 5 23 ms 24 ms 23 ms gateway-be3-dc112eph2.dc11.ptd.net [207.44.127.133] 6 22 ms 22 ms 23 ms lag-122.bear2.washington111.level3.net [4.14.99.89] 7 * 100 ms 100 ms ae-2-3201.ear1.paris1.level3.net [4.69.140.26] 8 221 ms 97 ms 98 ms choopa-llc.ear1.paris1.level3.net [212.73.205.86] 9 * * * Request timed out. 10 * * * Request timed out. 11 101 ms 100 ms 103 ms bgp-paris-1.radioamateur.tk [199.247.9.191] 12 113 ms 113 ms 113 ms 44.190.11.1
Trace complete.
C:>
On 1/24/2020 9:56 AM, Toussaint OTTAVI via 44Net wrote:
- My gateway is up and running. I can SSH to it via its WAN address
and through my tunnel.
bird shows the iBGP session is established (see output below)
a traceroute to my gateway 44.190.11.1 from the outside goes to San
Diego
- on the gateway, a ping with a 44.190 adress (ping -I 44.190.11.253
8.8.8.8) goes nowhere
birdc show proto all BIRD 1.6.3 ready. name proto table state since info vultr BGP master up 14:45:50 Established Preference: 100 Input filter: REJECT Output filter: ACCEPT Routes: 0 imported, 1 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 1 0 0 --- 1 Export withdraws: 0 --- --- --- 0 BGP state: Established Neighbor address: 169.254.169.254 Neighbor AS: 64515 Neighbor ID: 45.63.113.24 Neighbor caps: refresh restart-aware AS4 add-path-rx Session: external multihop AS4 Source address: 199.247.9.191 Hold timer: 131/180 Keepalive timer: 17/60
static1 Static master up 14:45:46 Preference: 200 Input filter: ACCEPT Output filter: REJECT Routes: 1 imported, 0 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 0 0 1 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
device1 Device master up 14:45:46 Preference: 240 Input filter: ACCEPT Output filter: REJECT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
Le 24/01/2020 à 15:44, Quan Zhou via 44Net a écrit :
I had similar issue in past with their ams and tokyo nodes, one time it was unrecoverable. For diagnostics, are you able to ssh to the gateway? If you are using bird then you can check with `birdc show proto all`.
On 1/24/20 10:23 PM, Toussaint OTTAVI via 44Net wrote:
Hi all,
Our subnet 44.190.11.0/24 does not seem to be reachable anymore from Internet. It's announced in BGP via a Vultr VPS located in Paris. I had notices from Vultr in the last few days about network upgrades. Currently, the route to our gateway 44.190.11.1 seems to be the default route via UCSD.
I opened a support ticket. I know some of us are using Vultr. Do you encounter similar problems ?
Thank you in advance, 73 de TK1BI
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
Hi there...Glad they resolved it. Both Vultr and Digital Ocean have good support in my experiences.
73 Leon WA4ZLW
On 1/24/2020 3:17 PM, Toussaint OTTAVI via 44Net wrote:
Le 24/01/2020 à 16:39, Leon Zetekoff a écrit :
here's a traceroute from me and it seems there is no tunnel to you my network is 44.56.53.1/28
Hi Leon,
Thank you for your report. Your traceroute is good. It came just after Vultr support solved the issue.
73 de TK1BI
-
Leon Zetekoff -
Quan Zhou -
Ruben ON3RVH -
Scott Nicholas -
Toussaint OTTAVI