Hello, we worked Saturday and Sunday from IQ3DQ without reflector, hot spots
and dongles.
Only 50 made the connections
73 Maurizio
--- In dstar_digital@yahoogroups.com, Steve Bosshard bossh...@... wrote:
I spoke with Steve G4UUI on the Ashford UK repeater this morning. GB7DS A
will be
Scott
Sorry to bust your bubble, but I did this over 2 weeks ago now on the real G2
system, not the German one that house a handful of repeaters.
As I am fed up with you not listening to what people are saying, may I just
repeat for the last time:
There is NO European Trust Server. Please
John
Yes, but my thoughts are why use a relational database to do the job of a
Routing Protocol ?
Something like ISIS or OSPF is easily able to cope with the number of repeaters
and stations we have. And having the Private IP Address space is actually
pretty good as we can keep it to an IP
Hello All
I've had several emails over the weekend asking very similar questions on my
software, so I'm going to make some comments and observations here.
Why ? Quite simple - I already have a very busy day (and evening) job, and the
time I have to reply/work on the code is very limited.
1)
Question for the group:
This webpage speaks of the D-STAR Hot-Point software.
http://darnsimple.net/wp/2009/05/digital-hot-point/
This uses the Dvdongle instead of a node adapter.
Is this the same software put out by W9ARP?
Thanks,
Tom
W8RED
My local Emergency Management Agency has made a huge investment into D*STAR
Radios, but now we have a need for these radios to have Wide Band Transmit
Capability, primarily for Interoperability during disasters. I am aware that
the radios would not be considered FCC Type Accepted, however this
--- In dstar_digital@yahoogroups.com, Eric Gildersleeve e...@... wrote:
I am aware that the radios would not be considered FCC Type Accepted, however
this modification would be with approval of the local government agency for use
on their frequencies.
Local county or municipal agencies do not
...a dstar repeater/gwy local dstar database
takes 2 minutes to receive the IP repeater updates
and the radio user updates from the TRUST server.
My home-made G2 dstar repeater/gateway receives updates from
the TRUST two minutes after another repeater sent its
update to the TRUST.
Is that
Scott
I think I explained this already.
It can take a VERY long time to receive the database sync from the Trust
Server. In some instances, up to 2 hours after requesting it.
What you are seeing is pretty quick - but I would expect that as you are on a
very small system.
David
--- In
Hmmm... that makes sense.
300 repeaters to 25 repeaters.
I now believe that is the case.
Scott
--- In dstar_digital@yahoogroups.com, dlake02 dl...@... wrote:
Scott
I think I explained this already.
It can take a VERY long time to receive the database sync from the Trust
Server. In
Hi dlake2,
I am trying to post this but it gets lost.
I will try again
Thank you for the input.
All I know there are two EU TRUST servers.
A TEST and a LIVE one.
In your IOCM dsipsvd.conf configuration file,
a repeater owner sets the TRUST_SERVER variable
to the TRUST server hostname that
dlake02 wrote:
John
Yes, but my thoughts are why use a relational database to do the job of
a Routing Protocol ?
Something like ISIS or OSPF is easily able to cope with the number of
repeaters and stations we have. And having the Private IP Address space
is actually pretty good
Hi John
Understood, but the best form of hashtable for routing is the Forwarding
Information Base on an IP router.
I was just trying to maintain as much compatibility with the current G2
architecture as possible whilst providing a scalable backbone.
But, I do understand what you mean about a
Don't forget the original design of DSTAR with the zones and multiple stacks in
a zone. Also, don't forget that there are repeaters that aren't attached to a
gateway computer and may never be. That's one of the biggest reasons for the G
routing in my mind.
Ed WA4YIH
From:
On Jul 27, 2009, at 2:57 PM, dlake02 wrote:
Hi John
Understood, but the best form of hashtable for routing is the
Forwarding Information Base on an IP router.
I was just trying to maintain as much compatibility with the current
G2 architecture as possible whilst providing a scalable
Don't believe that DNS updates are instantaneous. In common configuration, IP
address changes can easily take 6 hours.
And if you pull the TTLs down to something short, you start to bang the heck
out of the centralized name servers. Whoops, let me say the one centralized
name server, because
The whole zone concept really is dependent on the DOA (marketing
wise) 10 gHz backbone system, using ATM to bring multiple controllers
together to provide the zone and optionally share a gateway.
A smart controller/gateway would operate the same way whether attached
to the Internet or
This is part of the reason I favor having dynamically updated
Forwarding Information Bases for D-STAR frame addresses and not even
assign an IP to the frame address. On a highly mobile station, that
during a QSO might switch between gateways you don't want to wait on
centralized updates
18 matches
Mail list logo
