On 23 July 2019 at 09:32 R P via 44Net
<44net(a)mailman.ampr.org mailto:44net@mailman.ampr.org > wrote:
"Name me one brand of standard of the shelf routers that supports IPIP"
I know that MikroTik and Ubiquiti Router support IPIP and they are standart of the
shelf routers
I myself use Mikrotik Router and all our DMR Repeaters that get their Internet with
Cellular use MikroTik routers they are very reliable heve good GUI we can use them for
that purpuse akso any OPEN WRT based routers support IPIP and OPENWRT support lot of on
the shelf routers
Ronen - 4Z4ZQ
________________________________
From: 44Net <44net-bounces+ronenp=hotmail.com(a)mailman.ampr.org
mailto:44net-bounces+ronenp=hotmail.com@mailman.ampr.org > on behalf of Ruben ON3RVH
via 44Net <44net(a)mailman.ampr.org mailto:44net@mailman.ampr.org >
Sent: Monday, July 22, 2019 11:12 PM
To: 'AMPRNet working group' <44net(a)mailman.ampr.org
mailto:44net@mailman.ampr.org >
Cc: Ruben ON3RVH <on3rvh(a)on3rvh.be mailto:on3rvh@on3rvh.be >
Subject: Re: [44net] 44 net connectivity
There is nothing wrong with using private ASN's within a network. It's done
by many (if not all) telecom and network operators and used for their internal network or
connecting an internal customer with redundancy.
If we were to use a separate public ASN for each and every customer router that needs
redundancy we would quickly run out of ASN's and it'd be a mess.
When connecting to the internet, then indeed you need a public ASN which identifies
who you are and what networks you route (using radb and the likes), but within a private
network there is no need to use public ASN's. Even Vultr uses a private ASN to connect
with your VPS if you want to route some public space via them.
rPi is not a problem btw, it is a solution to many problems. Standard of the shelf
routers and modems will never support any kind of real openvpn tunneling or even ipsec
tunneling, nor will they run any kind of standard routing protocols like BGP or OSPF, or
even IPIP.
Name me one brand of standard of the shelf routers that supports IPIP (or even any
kind of dynamic routing protocol) out of the box without having to install an additional
daemon
So why would a rPi be a complication or problem? Please explain that to me. If you
want, you can even explain it of list.
73,
Ruben - ON3RVH
-----Original Message-----
From: 44Net <44net-bounces+on3rvh=on3rvh.be(a)mailman.ampr.org
mailto:44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org > On Behalf Of Pedja YT9TP via
44Net
Sent: dinsdag 23 juli 2019 7:53
To: 44net(a)mailman.ampr.org mailto:44net@mailman.ampr.org
Cc: Pedja YT9TP <yt9tp(a)uzice.net mailto:yt9tp@uzice.net >
Subject: Re: [44net] 44 net connectivity
On 23.07.2019 00:00, Brian via 44Net wrote:
Well, the
best step would be to make connecting easier, meaning,
anything but IPIP.
That
seems to be the vocal preference no?
> Nope. It is a fact.
Until
there is simple option to connect using plain, stardard and
widespread equipment, there will be no significant expansion.
Many hams
are using RPi units as 'routers' now, and this allows for
greater
flexibility.
> RPi is a complication. I learned through years that in 44net community there
will never be understanding about that.
And I also learned that we will never see significant expansion of 44net use.
We
already have problem with IPIP that requires very odd configurations.
Inventing new protocol that would not be supported in any existing
routers is nonsense.
If an RPi
is used it'd be quite simple actually. Also some routers
allow for you
to place a daemon in them as well and run it, most of
them are linux based.
> That is not solution. That is just more complication.
As long as 44net is inaccessible using plain, standard factory routers and standard
protocols, it will not be expanding.
We need
the very opposite - to use protocols that are wide spread and
available in almost every device.
We as a
community have developed protocols in the past that are in use
today. Why
couldn't we come up with something such as AGP (Amprnet
Gateway Protocol for example) that could pass through most ISP filters
on a device such as a Pi. We could then keep our "ASN" number as our
callsign-ssid to identify who we are and keep it from propagating to
the global internet and only for our own usage.
> I understand a principle, and I understand motivation but, c'mon. RPi is
not solution. It is part of a problem.
Whole IT world uses standard devices and standard protocols, and it works. Why should
anyone spend time, efforts and money to invent new protocol that does the same jsut a bit
different and which would bnever become standard outside 44net?
After all, with BGP we have problem only that we cannot easily use public but have to
use private ASNs - which is wrong way of doing it.
Al we need is another "instance" of BGP that would allow freely using new
set of ASNs. So, why inventing new protocol, just alter existing one so you can run at
lest two independent BGP layers on single machine.
But that would be custom protocol, non standard, not available anywhere except on
custom set hardware.
And again, that is repellent for people. If we want people to join in, it must be
simple and standard way using standard hardware and software.
Anything that requires installing linux and setting up custom machine and administer
would simply keep people away from 44net as it already does.
Please notice that I do not speak about concrete solutions. I am talking about
principles. When we adopt principles we could talk how to implement them. You simply have
to see big picture to be able to work on details.
--
73,
Pedja YT9TP
Checkout:
https://pedja.supurovic.net/
https://yu1abh.uzice.net/
https://www.facebook.com/yu1abh/
https://www.facebook.com/groups/yu1abh.konstruktori/
http://www.radio-amater.rs/
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org mailto:44Net@mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org mailto:44Net@mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org mailto:44Net@mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
______________________________________________
This email has been scanned by Netintelligence
http://www.netintelligence.com/email