Got it!?? Jeff, I read your email about 100 times and finally
understood (my fault, not yours)!??
?
So, I've got three PCs running.? One is the ratflector/client.?
The second is a DRATS client connected to ratflector/client via packet.? The
third is connected to the ratflector over the internet.??? All three can
communicate!? Nirvana at last!? ?The packet traffic is a little chatty because
of the TCP header (I suppose), but I think it's workable.?? Tomorrow I will try
to add a fourth PC connected via DSTAR RF.? Will also be able to add another
packet-connected PC.
?
Thanks for your work on this, Jeff and others.?? Brilliant
solution!?
?
Working through this has helped me understand the TCP Forwarding
and Gateway functions as well.?? May be even more possibilities there.
?
Wow!? Huge leap, IMHO!?
?
73,
Dan
W4DTO
?
From:
d-rats_group@... [mailto:d-rats_group@...] On Behalf
Of ae5me@... Sent: Friday, January 17, 2014 11:52 AM To: d-rats_group@... Subject: RE: [d-rats_group] RE: D-Rats, Packet, and UZ7HO
?
?
Good news from the Tulsa DRATS group. ?We were able to run multiple
clients on the TCP forwarding to the "server" to tie in packet users
to the ratflector repeater. ?Have some issues with it generating a lot of
traffic on a given channel, but it works.
?
Thinking
of using DPRS tied to APRS for short messaging (since TCP adds a lot of
overhead to it). ?Has anyone tied DPRS into DRATS? ?Another way to
tie packet side to DSTAR (I think).