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(a)mailman.ampr.org> On Behalf Of Toussaint OTTAVI via 44Net Sent: Friday, January 24, 2020 15:24 To: 44net(a)mailman.ampr.org Cc: Toussaint OTTAVI <t.ottavi(a)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(a)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(a)mailman.ampr.org >> https://mailman.ampr.org/mailman/listinfo/44net > _________________________________________ > 44Net mailing list > 44Net(a)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 : _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

Le 24/01/2020 à 16:39, Leon Zetekoff a écrit : Hi Leon, Thank you for your report. Your traceroute is good. It came just after Vultr support solved the issue. 73 de TK1BI