In my case my service provider did all the BGP work on
his end, using
his ASN. I just did the legwork of applying for a /24 and obtaining and
forwarding the LOA, as well as organising geolocation updates, DNS, and
doing my own renumbering.
While I didn't learn anything about BGP itself, I did get a feel for
some of the related administrative processes.
If the network starts using BGP internally, I'd be open to learning
about it.
On 29/7/21 5:29 am, PH5X via 44Net wrote:
I've never done anything more than home
networking and I have managed
to set this up remotely on a VM for €5/month. My network is connected
directly to two internet exchanges and exchanging routing information
with hundreds of other autonomous systems.
An ASN can be had for free from some sponsoring LIRs.
The address space is available from 44Net.
Plenty of people are willing to peer with you, even some larger ISPs,
NSPs and organizations are happy to peer with small networks. Some
even provide free transit.
A € 5 VPS and free & open source software is all you need. You could
even get started with a tunnel to a virtual internet exchange and a
transit provider from a local machine.
Some experience with home networking and Linux command line is all I had.
These peering requirements are not always so strict or are not
mentioned at all. Some large networks may have those requirements for
direct peering, plenty of others that don't.
Some technical skills are expected, but we already have that as
amateur radio operators, or are willing to learn.
It's not such a large hurdle to overcome as it might seem. 44net can
be a great opportunity to learn about BGP and the workings of the
global internet with publicly routable address space. People should be
encouraged to learn.
Regards,
PH5X
On 28-07-2021 20:42, Tim Požar via 44Net wrote:
BGP on the public Internet requires that you:
* Have an ASN
* Have address space that is a /24 or larger that you can announce
* Typically, have two peers or more you can announce to.
* Have the gear/software that announce the space
* Have some previous experience so you are not just experimenting
with your deployment
* Meet your peer's requirements (eg 24 hour NOC, show up at a peering
location, etc.)
* Have the skill set to execute all of the above
This will be a large hurdle for most folks.
Tim
On 7/28/21 11:16 AM, Colin Bodor via 44Net wrote:
> BGP is what is used at a high level for the internet, it can be
> ultra-reliable but of course only as reliable as the number of peers
> and the admin who runs that ASN 😉 and in some cases, the politics
> of the country you reside in.
>
> I have no comment on the proposal, other than that if I need to
> renumber any of my BGP prefixes, sooner is probably better than
> later, and VPN makes more sense (I think that’s whats being
> proposed?) than the current method (but BGP is best) IMHO. Amazon
> AWS for example can do BGP through a VPN, those of us who can do BGP
> will prefer it as its easiest for our network design, and if you
> "just want to connect" IPSEC is supported by almost everything and
> would be easy to configure and setup, specially with a portal to
> create credentials and provide some config examples. Then just
> default route through it. Or even OpenSSL... The renumbering is what
> it is.
>
> I am also willing to provide some no charge VPS's up here in Canada
> if that is of any use for VPN end points or whatever purpose. We are
> actively seeking volunteer opportunities that "mesh" with our IT
> offerings (data center, BGP, VPS etc) and happy to donate some
> resources to a good cause. I also focus on keeping local traffic
> local (IE internet exchange points) so if the opportunity is there
> to help route local 44net traffic within Canada that’s great,
> andbetter for a number of reasons.
>
> Just my .02
> -Colin/VA6CCB
>
> -----Original Message-----
> From: 44Net <44net-bounces+colin.bodor=imperium.ca(a)mailman.ampr.org>
> On Behalf Of Pedro Converso via 44Net
> Sent: Wednesday, July 28, 2021 12:06
> To: 44Net general discussion <44net(a)mailman.ampr.org>
> Cc: Pedro Converso <pconver(a)gmail.com>
> Subject: Re: [44net] A new era of IPv4 Allocations
>
> Thanks Antonis,
>
> Looks things could be then allright for us in case this proposal is
> accepted.
>
> Althoug BGP doesn't look reliable as on
>
https://www.cloudflare.com/learning/security/glossary/what-is-bgp/ I
> try to not favore BGP usage for ampr users.
>
73,
lu7abf, Pedro
On 7/28/21, Antonios Chariton (daknob) via 44Net
<44net(a)mailman.ampr.org> wrote:
> Hello Pedro,
>
> The 44.153/16 allocation will only be affected if you do not want to
> join a network like HAMNET but instead you want to use this IP space
> on the Internet using BGP.
>
> Depending on your current use case and what you plan to do, we can
> provide more information about any steps you may have to take, and if
> you do, we’ll be happy to work with you to determine what these may
> be.
>
> Thanks,
> Antonis
>
>> On 28 Jul 2021, at 15:59, Pedro Converso via 44Net
>> <44net(a)mailman.ampr.org> wrote:
>>
>> Will proposed change affect 44.153.x.x allocations?
>>
>> Thanks
>>
>> 73, lu7abf, Pedro
>> 44.153 Argentina Coordination
>> _________________________________________
>> 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
>
_________________________________________
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
_________________________________________
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