11 Mar
2019
11 Mar
'19
10:02 a.m.
Steve, VK5ASF, has very correctly pointed out a case where this
proposed change would cause problems. Marius concurs, and therefore
I have decided to cancel the planned change. The RIP transmissions
will NOT begin to include the BGP routes on March 15th.
NO CHANGE WILL BE MADE.
Thank you to both Steve and Marius for bringing this problem to my
attention.
Please accept my apologies for any confusion that may have occured.
Best wishes and 73 to all,
- Brian
On Mon, Mar 11, 2019 at 10:25:23AM +0100, Toussaint OTTAVI wrote:
Le 11/03/2019 à 01:12, Brian Kantor a écrit :
Beginning on March 15th, the pseudo-RIP
transmissions from amprgw
will include the various subnet prefixes which are being advertised
by BGP. They will show a next-hop address of 169.228.34.84, which
is amprgw.
Hi,
Does this include the new 44.190.0.0/16 subnet, which is intended to
host Internet-connected stuff, such as Echolink, DMR, XLX, etc ?
I would probably say "no"... But I have very few experience with ripd
tunnels, so I can not say if that could be useful or not...
For people who can't deal with local routing tables, maybe it's better
to have "long path" connectivity through amprgw than no connectivity at
all... But using such a path for VoIP does not seem to be a good idea...
73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net