27 May
2017
27 May
'17
9:11 a.m.
The only things that might collide on users systems are the RIP
transmissions, and I already have them separated in time by three
seconds, that's three times the length of the transmission.
I'm in the process of sending an email to the registered email
address of every single gateway registered with the portal which
will tell them about the changes coming. I feel that this is
necessary because a lot of them don't subscribe to the 44net
mailing list, despite my strong recommendation that they do so.
We'll see how many complaints I get.
- Brian
On Sat, May 27, 2017 at 06:31:48AM -0400, lleachii--- via 44Net wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Brian,
If you haven't consider this...make sure that the cron jobs aren't
configured to execute on both machines at the same time. I'm not sure how
you configured the intervals, but if you're able to set them 60-180 seconds
apart, that should work.
My machine (and others that receive IPENCAP from ANY) may exhibit odd
behavior if receiving duplicate routes...especially while the RIP44 daemon
is executing the routes.
This also make me think about the ICMP Redirect thing...how bout changing
the password to the routes on Old_AMPRGW, that will be a first phase-out for
OPs running RIP44, as they should observe they can't send traffic to us any
longer. After that, the only remaining OPs on Old_AMPRGW would be those who
use the Munge Script method. At some point, you will turn off Old_AMPRGW
anyway, something should have been noticed by that point in time.
- Lynwood
KB3VWG
No issues with turning them on as long as the RIP
content is the same...
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net