16 Jan
2021
16 Jan
'21
6:12 a.m.
Clients connect to the Vultr non-44 address on ens3. The target of the tunnel cannot be
an address inside the tunnel range.
While establishing BGP for Net-44 is a topic for this list (IMO). Configuring OpenVPN
probably is not. But OpenVPN is popular and widely used. There are tons of public places
to get support for OpenVPN. One place I would suggest (it is what we are using for IRLP
repeaters) is pivpn.io. It was intended for the Raspberry Pi, but can run on any Debian.
But beyond that suggestion, I going back to listen only.
Good luck, you beat the hard part!
-Dave, K9DC
On Jan 15, 2021, at 16:44, pete M via 44Net
<44net(a)mailman.ampr.org> wrote:
Now the problem is about openvpn.
I wont connect to it, either by the adress on 44 or the vultr provided IP.
So
systemctl status openvpn
● openvpn.service - OpenVPN service
Loaded: loaded (/lib/systemd/system/openvpn.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Jan 15 21:21:33 hamrad.ca systemd[1]: openvpn.service: Succeeded.
Jan 15 21:21:33 hamrad.ca systemd[1]: Stopped OpenVPN service.
Now I need to follow the bread crumb that is causing this...
So not being a 44net problem should I not go to the vpn44 list?
I think this will only climb the noise level way too high for many people on the list
that have no interest at all about vpn stuff.
Now prove me wrong and I will stay here ;-)
________________________________________
De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de
Ruben ON3RVH via 44Net <44net(a)mailman.ampr.org>
Envoyé : 15 janvier 2021 16:29
À : AMPRNet working group
Cc : Ruben ON3RVH
Objet : Re: [44net] BGP/openvpn finally all ok.
I don’t see why you should move. It is 44net related, even if you are announcing through
vultr.
Ruben - ON3RVH
> On 15 Jan 2021, at 22:17, pete M via 44Net <44net(a)mailman.ampr.org> wrote:
>
> Yes probably. Better on group.io for such project.
> Going there for the rest of the discussion..
>
> The BGP route not working was a problem at vultr, they fixed it pretty fast. But as
always I got stock with something else for the job ;-)
>
> Thanks to every one that helped!
>
>
> ________________________________________
> De : 44Net <44net-bounces+petem001=hotmail.com(a)mailman.ampr.org> de la part de
David McAnally via 44Net <44net(a)mailman.ampr.org>
> Envoyé : 15 janvier 2021 14:31
> À : AMPRNet working group
> Cc : David McAnally; Rob PE1CHL
> Objet : Re: [44net] BGP/openvpn finally all ok.
>
> Perhaps better discussed here?
> <https://groups.io/g/net-44-vpn>
>
> David M.
> WD5M
>
>> On Fri, Jan 15, 2021 at 1:18 PM Rob PE1CHL via 44Net
<44net(a)mailman.ampr.org>
>> wrote:
>>
>> Maybe it is an idea to take this off-list?
>>
>>> On 1/15/21 8:01 PM, pete M via 44Net wrote:
>>> yup it is there
>>> BGP
>>> Prefix Date Added RPKI Status Valid
>>> 44.135.59.0/24 2020-10-26 18:22:57 No RPKI ROA found
>> Yes
>>>
>>>