Hi Nate
No offense taken ! I don't know DNS in the kind of detail required. My
concern is the amount of network traffic DNS could take compared to that used
on a properly configured IP routing protocol. Again, I know the latter well -
not the former.
Your comment on the 10.X.X.X range is
At 07:17 PM 7/29/2009, you wrote:
Your comment on the 10.X.X.X range is interesting - whilst I would
gladly sweep that away in an instance, I am concerned that there is
a use that may break. Does anyone know what was in Icom's mind when
they used that range ?
I get the impression they were
On Jul 29, 2009, at 3:17 AM, dlake02 wrote:
No offense taken ! I don't know DNS in the kind of detail required.
My concern is the amount of network traffic DNS could take compared
to that used on a properly configured IP routing protocol. Again, I
know the latter well - not the former.
: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On
Behalf Of Stewart Bryant
Sent: Monday, July 27, 2009 4:31 PM
To: dstar_digital@yahoogroups.com
Subject: Re: [DSTAR_DIGITAL] Re: First home-made dstar G2 gateway went live
today.
dlake02 wrote:
I completely agree
dlake02 wrote:
The DNS is only to find the reference between the callsign and the IP
address. Entries would only be added once stations are authorised, so
any delay would not affect the live routing.
IP Routing would take care of station moves, not DNS.
Every repeater would look-up
I agree.
On Jul 28, 2009, at 12:37 AM, Nate Duehr wrote:
It doesn't have to be that way with a new Gateway... an IP connected
Zone that acts as one repeater system for local linking/regional
linking, sure would be a nice feature...
--
Nate Duehr, WY0X
n...@natetech.com
.
John D. Hays
On Jul 28, 2009, at 1:51 AM, dlake02 wrote:
I completely agree that DNS is inappropriate for instantaneous moves.
73 David - G4ULF
No offense intended David, but anyone who says this hasn't done it.
DNS can EASILY handle virtually instantaneous updates, when configured
and used
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
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
@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On
Behalf Of John Hays
Sent: Monday, July 27, 2009 5:38 PM
To: dstar_digital@yahoogroups.com
Subject: Re: [DSTAR_DIGITAL] Re: First home-made dstar G2 gateway went live
today.
Hi David (and Stewart),
On Jul 27, 2009, at 1:30 PM, Stewart Bryant
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
zone replication timeframes will also add a lot of delay.
Ed WA4YIH
From: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On
Behalf Of Stewart Bryant
Sent: Monday, July 27, 2009 4:31 PM
To: dstar_digital@yahoogroups.com
Subject: Re: [DSTAR_DIGITAL] Re: First home-made dstar
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
On Jul 23, 2009, at 6:26 PM, Tony Langdon wrote:
At 08:28 AM 7/24/2009, you wrote:
What is definately needed is a complete network, where all are
connected
together, some way.
I agree. I have concerns about there being one Trust server, but
this is more an architectural issue.
And
At 05:13 PM 7/24/2009, you wrote:
And there was a request, what... a year ago?... for volunteers to form
an Architectural Committee or something similar... Advisory Board?...
I forget what it was called, but it was OBVIOUSLY designed to be a
working forum for worldwide standards... from the K5TIT
Hi Jochen
First, you sent me an email asking if I would like to test my software on your
system several weeks ago - I apologise that I have been so busy, that I haven't
gotten round to it yet !
Second. I have some questions about your X-Trust system:
1) Each user requires a unique /28 IP
There is a certain expectation among D-STAR RF users that if they are
in range of a D-STAR repeater, that provides gateway services, that
they should be able to do callsign routing to any other D-STAR RF user
that is in range of a gateway equipped D-STAR repeater. This means
that they all
Scott
Some comments on your code logic please (all meant in the spirit of
co-operation, NOT criticism):
1) dstar_register_rptr. You use the call strcpy(ip, inet_ntoa(ia));
However ia has already been set to the IP Address of the Trust Server.
If this is a registration, the IP address sent in
You are looking at an old piece of source code.
The new one access the gip.
And 2 Linux servcices,not 3.
I prefer the RECEIVING IP updates to be
in a different logic from the SENDING IP updates.
Glad you are looking at my source code, bu that is a very old
program.
Scott.
--- In
...@yahoogroups.com] On Behalf Of dlake02
Sent: Friday, July 24, 2009 9:52 AM
To: dstar_digital@yahoogroups.com
Subject: [DSTAR_DIGITAL] Re: First home-made dstar G2 gateway went live
today.
There is a certain expectation among D-STAR RF users that if they are
in range of a D-STAR repeater, that provides
Scott
This is the source downloaded today:
dstar_gwy.zipi386 17.5 KiBSun Jul 19 2009 10:44
David
... and I only get the FULL db once, then I get
one or two radio or repeater updates once every 15-20 minutes.
I dont have a problem with receiving the initial FULL db,
I use Postgres which is very fast.
I get about 8000 dstar radio users and about 500 dstar repeaters in
the INITIAL FULL db and
Scott
Do not twist my words please.
I didn't say that a Trust Server didn't work.
What I said was that whilst Icom have designed the G2 Trust Server to be
able to be run as a devolved system, that piece of code doesn't work.
You cannot build the Icom system as a cascade of units.
IF the Icom
Scott wrote:
It is dstarusers.eu ands it is an ICOM TRUST server
as the k5tit trust.
I talk from my dstar repeater to the other dstar repeaters
in that TRUST.
(snip)
We will set up one in Canada and one in the US.
So who is the group that runs dstusers.eu?
And who is we?
A lot of your
Registrations for NEW dstar repeaters to an ICOM TRUST
do not have data like 10.x.x.x
I checked about 5 NEW repeater registrations to us trust
and 3 to European trusts.
No 10.x.x.x anywhere in any registration packet
for a NEW repeater.
Scott
--- In dstar_digital@yahoogroups.com, dlake02
I do not trust that number.
ICOM dstar TRUSTS(dsipsvd) use separators:
0x0a = RECORD separator.
0x09 = FIELD separator.
Since I do NOT trust that number, I use the RECORD separators and
get every RECORD in the FULL DB and every RECORD in
subsequent updates without doing computations on
On Fri, Jul 24, 2009 at 09:24:42AM -, ham44865 wrote:
Registrations for NEW dstar repeaters to an ICOM TRUST
do not have data like 10.x.x.x
I checked about 5 NEW repeater registrations to us trust
and 3 to European trusts.
No 10.x.x.x anywhere in any registration packet
for a NEW
On Fri, Jul 24, 2009 at 09:25:26AM -0400, Bob McCormick W1QA wrote:
Although I can acknowledge that there may be some situations where a group
may want to have their own trust server and private network ... I would
put my money on the majority of both D-STAR users and repeater
owners/trustees
Thompson
d...@waycom.com
- Original Message -
From: dlake02 dl...@cisco.com
To: dstar_digital@yahoogroups.com
Sent: Friday, July 24, 2009 5:23 AM
Subject: [DSTAR_DIGITAL] Re: First home-made dstar G2 gateway went live
today.
Scott
Do not twist my words please.
I didn't say that a Trust
Bob McCormick W1QA wrote:
Although I can acknowledge that there may be some situations
where a group may want to have their own trust server and
private network ... I would put my money on the majority
of both D-STAR users and repeater owners/trustees would
lean towards an architecture
NO, I meant the European TRUST at dstareusers.eu is
running as a TRUST server exactly as k5tit does
at dstarusers.org or something.
They have built a NEW TRUST server.
That is the point.
Now others will build more, as every country should have one.
That is the point.
I dont care which
It has changed 10 times since then. OLD stuff.
The one I am running now, it is flawless.
I will post another copy after I define it to run as a
Linux service.
Scott
--- In dstar_digital@yahoogroups.com, dlake02 dl...@... wrote:
Scott
This is the source downloaded today:
Send an e-mail to that group.
I am not the owner of that European TRUST.
They will explain it to you if you need more info.
They posted a message earlier.
All I know is they operate the ICOM TRUST.
Scott
--- In dstar_digital@yahoogroups.com, Bob McCormick W1QA ya...@... wrote:
Scott wrote:
That I agree with.
Scott
--- In dstar_digital@yahoogroups.com, Jay Maynard jmayn...@... wrote:
On Fri, Jul 24, 2009 at 09:24:42AM -, ham44865 wrote:
Registrations for NEW dstar repeaters to an ICOM TRUST
do not have data like 10.x.x.x
I checked about 5 NEW repeater registrations
--- Original message ---
From: ham44865 ham44...@yahoo.com
To: dstar_digital@yahoogroups.com
Sent: 24.7.'09, 19:00
NO, I meant the European TRUST at dstareusers.eu is
running as a TRUST server exactly as k5tit does
at dstarusers.org or something.
They have built a NEW TRUST
Building isolated trust domains is wrong, and we'll end up with
yet-another
IP overlay like D-Plus, D-Extra, IRLP, Echolink, eQSO, etc, etc.
A smaller and smaller Amateur community, more and more disconnected
from each other.
Yes, that is how a properly implimented network works. You have
On Fri, Jul 24, 2009 at 03:59:28PM -, ham44865 wrote:
--- In dstar_digital@yahoogroups.com, dlake02 dl...@... wrote:
This is the source downloaded today:
dstar_gwy.zipi386 17.5 KiBSun Jul 19 2009 10:44
It has changed 10 times since then. OLD stuff.
The one I am
Hi Eric,
I did NOT create anything myself.
I see other ICOM TRUST server groups popping up.
Scott
--- In dstar_digital@yahoogroups.com, Erik Finskas la...@... wrote:
Who are WE in this aspect? Why do you want to create numerous parallel
networks unvisible ro each other? You then fail
I release a copy every two weeks or so, sometimes
twice during the same day.
All the OPEN SOURCE dstar project is at
http://dstardextra.sourceforge.net/
Where you will also find dextra_srv that links an ICOM gateway
to dstar reflectors and dextra_reflect that creates/runs
a Linux machine as
On Fri, Jul 24, 2009 at 04:42:09PM -, ham44865 wrote:
I release a copy every two weeks or so, sometimes
twice during the same day.
Then don't complain when someone comments on a version you haven't releaed
yet.
I made my dstar G2 gateway OPEN SOURCE from the beginning at the above
I see 2 of them, similar setup to the usroot...org something
xtrust3.dstarusers.eu
xtrust2.xreflector.net
I sent an e-mail and asked If I can register ny dstar
repeater KJ4NHF for testing first,
Once testing went OK, I moved to the LIVE ICOM TRUST
they administer and run
Scott
--- In
Scott
Software and flawless - two words that simply don't belong together.
I notice in your database structure that you choose not to record the
start_ipaddr field.
As you have no knowledge of the 10.X.X.X/28 address, how do you add users to
the trust domain ?
David
--- In
Scott
In the initial packet, the IP address is set to a 10.X.X.X/28 address. You
won't see that in the database, because it is only sent until the Zone RP is
authorized.
Once authorized, the IP address used is the one that the Trust Server picks up
from source IP of the poll.
Also, once
On Jul 24, 2009, at 12:33 PM, dlake02 wrote:
Scott
In the initial packet, the IP address is set to a 10.X.X.X/28
address. You won't see that in the database, because it is only sent
until the Zone RP is authorized.
Once authorized, the IP address used is the one that the Trust
Server
You are LOOKING at the OLD VERSION again.
The new one is NOT released yet,
I mentioned that in the previous post.
Scott
--- In dstar_digital@yahoogroups.com, dlake02 dl...@... wrote:
Scott
Software and flawless - two words that simply don't belong together.
I notice in your database
You are looking at the OLD version.
Scott
--- In dstar_digital@yahoogroups.com, dlake02 dl...@... wrote:
Scott
In the initial packet, the IP address is set to a 10.X.X.X/28 address. You
won't see that in the database, because it is only sent until the Zone RP is
authorized.
Once
The EUROPEAN TRUST is OPEN SOURCE,not closed.
So,they are using ICOM repeaters and ICOM hardware
for dstar routing and normal/regular dstar radio communications
RF and such
but for linking to dstar reflectors
they are using the OPEN SOURCE dextra_srv for linking to dstar
reflectors powered by
I am going to release my G2 code and make it OPEN SOURCE at:
http://dstardextra.sourceforge.net/
You will also find there the OPEN SOURCE dextra_srv
which links dstar repeaters/gateways to dstar reflectors.
I can not use dplus on my gateway/repeater because
it is CLOSED source.
So I use the
I see 3 SYNC packets:
One SYNC packet with 10.x.x.x from my repeater to the TRUST.
--- TRUST responds witj OK= 0 0 0 40 0 0 0
--- One SYNC packet from TRUST to my repeater with 10.x.x.x
That is the IP update I sent before.
The third SYNC packet with PC-IP address and more
John
The whole use of the 10.X.X.X addresses seems like a real mess, but in fact, it
could be put to very good use.
The advantage is that every callsign has a unique address in the system, down
to a device level.
A very similar concept exist in the cellular networks - each device has it's
David,
I'm only Cisco IOS literate with a manual in hand :) but I see the
appeal of the reuse of IP protocols. I just think it confuses the
issue in D-STAR
I feel the callsign (including the 8th character designator) in the D-
STAR protocol is unique enough for endpoint determination.
On Fri, Jul 24, 2009 at 08:17:27PM -, ham44865 wrote:
You are LOOKING at the OLD VERSION again.
The new one is NOT released yet,
I mentioned that in the previous post.
Release early, release often. Until then, quit complaining.
--
Jay Maynard, K5ZC at K6ZC port B
On Fri, Jul 24, 2009 at 07:48:47PM -, dlake02 wrote:
There is one problem will Open Source, and that is the possibility that
someone will change something that breaks things for everyone else.
The effect there could be to close down all open source development.
This is not a problem
You know, all of the Linux network code is Open Source (thanks Fred),
it hasn't brought the Internet down. Please, Please, Please don't
let fear keep you from making your code open source, David. Starting
with good open source gateway/trust server code, from responsible
developers, will
Not complaining Jay,it is an old source release he is reading.
Just the facts.
Scott
--- In dstar_digital@yahoogroups.com, Jay Maynard jmayn...@... wrote:
On Fri, Jul 24, 2009 at 08:17:27PM -, ham44865 wrote:
You are LOOKING at the OLD VERSION again.
The new one is NOT released yet,
This is great news! It tears down another proprietary hook to allow other
vendor marketing groups to begin considering DSTAR equipment implementations.
73's,
Tim - N8DEU
--- In dstar_digital@yahoogroups.com, John Hays j...@... wrote:
You know, all of the Linux network code is Open Source
(Please don't top-post.)
On Fri, Jul 24, 2009 at 11:39:36PM -, ham44865 wrote:
--- In dstar_digital@yahoogroups.com, Jay Maynard jmayn...@... wrote:
On Fri, Jul 24, 2009 at 08:17:27PM -, ham44865 wrote:
You are LOOKING at the OLD VERSION again.
The new one is NOT released yet,
At 02:13 AM 7/25/2009, you wrote:
Why dont you all join your your forces and start designing a next
generation trust system which has multiple instances for redundancy but
still acts like one so everybody could use it and enjoy a global D-STAR
network..
This is what needs to be looked at for the
I do not understand why you are hostile.
Scott
--- In dstar_digital@yahoogroups.com, Jay Maynard jmayn...@... wrote:
(Please don't top-post.)
On Fri, Jul 24, 2009 at 11:39:36PM -, ham44865 wrote:
--- In dstar_digital@yahoogroups.com, Jay Maynard jmaynard@ wrote:
On Fri, Jul 24, 2009
(Please don't top-post.)
On Sat, Jul 25, 2009 at 01:46:43AM -, ham44865 wrote:
--- In dstar_digital@yahoogroups.com, Jay Maynard jmayn...@... wrote:
Perhaps. Still, you'd get a lot farther with You've got an old version. The
current code is at...and where to find it. Heck, it's on
I am releasing as often as every week.
Cant do it faster. Comments are fine,
They dont bother me.
Scott
--- In dstar_digital@yahoogroups.com, Jay Maynard jmayn...@... wrote:
(Please don't top-post.)
On Sat, Jul 25, 2009 at 01:46:43AM -, ham44865 wrote:
--- In
On Jul 24, 2009, at 9:12 AM, Jay Maynard wrote:
Agreed. Anyone who joins his system to a network that's not the main
D-Star
network, with the trust server specified as the one run by the K5TIT
crew,
without a very good reason for doing so (such as testing beta
software for
On Jul 24, 2009, at 10:13 AM, Erik Finskas wrote:
Who are WE in this aspect? Why do you want to create numerous parallel
networks unvisible ro each other? You then fail to understand the
whole
concept of D-STAR callsign routing.
You do realize you'll never get an answer to these
There are 4 European ICOM TRUST servers.
You would need permission with them to register your
home-made ICOM compatible G2 Gateway, same thing with the US.
I also have instructions on how to create a NEW ICOM
TRUST server. They have created their own ICOM TRUST server,
just like K5TIT did.
Same here, I do not care much about:
Who's on first, What's on second, I Don't Know's on third.
It does not matter.
I will release the whole OPEN SOURCE code of my 3 server programs
at http://dstardextra.sourceforge.net/
My 3 server programs that make up the ICOM compatible
G2 Gateway will be:
Hello Group,
for evryone who like to do some tests or who want's to join the
trust, please feel free to register with:
xtrust2.xreflector.net
This setting for this may be done in the dsipsvd.conf located in
/opt/products/dstar/dstar_gw/dsipsvd/
in the line beginning with
TRUST_SERVER =
The
Scott
There is no European Trust server !
There is one trust server because Icom only allow one in an entire network.
That is the K5TIT trust server.
There are small pockets of isolated groups in Germany that are running a
handful of repeaters, but these are no good to man-nor-beast as they
I say, the more OPEN SOURCE TRUST servers the better.
I have talked to people in Europe and Canada and they want their
own ICOM TRUST servers.
I am talking to Canadian dstar repeater owners.
They will also set their own ICOM TRUST server soon.
This back and forth
of data from each country
At 08:28 AM 7/24/2009, you wrote:
What is definately needed is a complete network, where all are connected
together, some way.
I agree. I have concerns about there being one Trust server, but
this is more an architectural issue. Like other networks have done,
there should be a number of
First home-made dstar G2 gateway went live today.
No, G4ULF was first last week with GB7MH, and his connect to ICOM backbone
dplus dstarmon - see his earlier post. Is better?
7/3, Aro
dstar_gwy_srv can be used on any DSTAR ICOM system,
Europe,US, Japan,...
It is idependent of any backbone,if there is such a word
backbone when it comes to dstar.
I believe you mean dstar TRUST groups, not backbone.
Scott
--- In dstar_digital@yahoogroups.com, aro_bugger aro_bug...@... wrote:
--- In dstar_digital@yahoogroups.com, ham44865 ham44...@... wrote:
First, congratulations on the advances in your project! I have looked at and
built the code for your gateway from
http://sourceforge.net/projects/dstardextra/ and will be doing some testing on
it.
Also it was cool to see
You are correct.
It does not matter which TRUST group your home-made dstar G2 Gateway
software belongs to.
As long your home-made dstar G2 Gateway software can communicate
with the ICOM TRUST dsipsvd software, you are OK,
because every TRUST server uses the same ICOM dsipsvd software
for
75 matches
Mail list logo
