15 Jul
2013
15 Jul
'13
3:21 p.m.
Not necessarily so..
The 44 addresses not in the encap.txt should be routed to ucsd
and they will hopefully tunnel them to that specific gateway.
There is normally a line for that in a munge script.
Bob
On 13-07-15 02:54 AM, Heikki Hannikainen wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Sun, Jul 14, 2013 at 2:04 AM, Bob Tenty <bobtenty(a)gmail.com> wrote:
There are more subnets who are announcing
themselfs over Internet with BGP
and who are still in the encap.txt
But but... I think they absolutely must stay in
encap.txt even if a
BGP announcement is place!
If they're removed, most of other traditional amprnet sites, which are
not announcing their own network using BGP, cannot send packets to the
BGP sites due to source address filtering (spoof protection). Most
gateways these days must send out all 44-to-44 traffic encapsulated
because they're only allowed to transmit out packets with their
gateway's public address as the source address of the outer IP packet.
- Hessu
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html