Are you using a different callsign for the 2nd ratflector instance? I would think using the same callsign would be very close to the loop John warns against.
I take down occasionally for system updates. I send out a QST stating the system is gong offline for a few minutes (or hours) for updates. That way the users know to reconnect after the system reboots. The ratflector automatically restarts as a system service after reboot.
Mike, N0SO
toggle quoted message
Show quoted text
On Jan 13, 2015, at 12:29 PM, Dan Ozment
dan@... [d-rats_group] <
d-rats_group@...> wrote:
?
I take this a step further. I never want to take my primary ratflector
down. I've noticed if I take the ratflector down to add a link the
D-RATS clients connected to it don't always reconnect and the user may
not know they are kicked off.
So, I have a primary ratflector that stays up all the time, and my users
connect to it. If I want to link different ratflectors I start a new
instance of the ratflector app and link it to my primary ratflector and
any others I want to link in (including via RF). If the linking
ratflector goes down it doesn't kick users off the primary ratflector.
Dan
W4DTO
On 01/13/2015 01:15 PM, John Davis wb4qdx@... [d-rats_group] wrote:
> Its even simpler. In one ratflector, define anorher ratflector just like you define a radio except it's a network connection. I've done it successfully several times. Just be careful that you don't setup a loop.
>
> Johm WB4QDX
