OK, now for some new information!
Ever wonder what happens on port 40001??? HERE YOU GO!!

[r...@localhost ~]# tail -f /var/log/dsgwd.log
Dec 31 19:02:00 localhost dsgwd[5499]: ethernet if_index is 2
Dec 31 19:11:38 localhost dsgwd[5442]: STARTUP dstar GW(type2) (C)
2004-2008 Icom Inc. Revision 2.2
Dec 31 19:11:38 localhost dsgwd[5442]: ethernet if_index is 3
Jan  1 17:27:00 localhost dsgwd[5482]: STARTUP dstar GW(type2) (C)
2004-2008 Icom Inc. Revision 2.2
Jan  1 17:27:00 localhost dsgwd[5482]: ethernet if_index is 2
Jan 30 20:18:49 localhost dsgwd[5482]: inz_recv:Connected from GW
(71.100.255.222)
Jan 30 20:28:58 localhost dsgwd[5482]: inz_recv:Disconneted from GW
(71.100.255.222)
Jan 30 20:52:12 localhost dsgwd[5482]: inz_recv:Connected from GW
(71.100.255.222)
Jan 30 21:04:02 localhost dsgwd[5482]: inz_recv:Disconneted from GW
(71.100.255.222)
Jan 30 21:04:28 localhost dsgwd[5482]: inz_recv:Connected from GW
(71.100.255.222)


each connect and disconnect came from KJ4ACN's DD via my laptop.
what you seeing here is the log file from K1XC, the test subject
for this...

NOW here's KJ4ACN's log:
Jan 30 20:48:33 dstargw dsgwd[14279]: inz_recv:Disconneted from GW
(96.254.156.26)
Jan 30 20:48:33 dstargw dsgwd[14279]: inz_recv:Disconneted from GW
(96.254.156.26)
Jan 30 20:52:12 dstargw dsgwd[14279]: inz_recv:connected to GW
(72.151.129.248)
Jan 30 20:52:12 dstargw dsgwd[14279]: inz_recv:connected to GW
(72.151.129.248)
Jan 30 21:03:51 dstargw dsgwd[14279]: inz_recv:connected to GW
(198.77.230.9)
Jan 30 21:03:51 dstargw dsgwd[14279]: inz_recv:connected to GW
(198.77.230.9)
Jan 30 21:03:51 dstargw dsgwd[14279]: inz_recv:Connected from GW
(198.77.230.9)
Jan 30 21:03:51 dstargw dsgwd[14279]: inz_recv:Connected from GW
(198.77.230.9)
Jan 30 21:04:28 dstargw dsgwd[14279]: inz_recv:connected to GW
(72.151.129.248)
Jan 30 21:04:28 dstargw dsgwd[14279]: inz_recv:connected to GW
(72.151.129.248)



Again, this was happening when ever I issued a ping
<callsign>.dstar.local

More to play with over the weekend.
Those of you with ID-1's, I am going to hook it up
to my linux box here at the house and try a few
tests, one of them is seeing if you all can pull up
the INTRAnet website I have for KJ4ACN, that I am
doing this project on....
SO if you 23cm DD'ers want to try something,
load up and http to 10.122.66.82 and see what you get.

Please email your results to my email box off the list....

Evans
 

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Evans Mitchell
KD4EFM / AFA4TH FL / WQFK-894
Sent: Friday, January 30, 2009 8:02 PM
To: [email protected]; [email protected]
Subject: {Disarmed} [DStar-Gateway] Question for both email groups...
ID-1 DD stuff.... researching

"Posting question to DSTAR-GATEWAY & DSTAR DIGITAL"

Does anyone know of an email group for ID-1 users, or
ID-1 projects???? Like to join and continue with this project.

I am working some events that are rather neat, but I am not sure either
one of these reflectors will be to my advantage while I am testing out a
couple of things here.... BUT this is what I have done so far...

Using the id-1 hooked up to a laptop, perform the
following: 
laptop contains kd4efm-id1 ip: 10.122.66.82 255.0.0.0 DNS set to
10.0.0.1 172.16.0.20

ipconfig says: 10.122.66.82, 172.16.0.7
gw's: 10.0.0.1, and 172.16.0.1

--BK--

using ping, knowing a call sign, pinging the call sign and recording the
results....
i.e.: ping ki4swy.dstar.local
results: 
pinging ki4swy.dstar.local [10.94.166.128] with 32 bytes of data reply
from 10.122.66.82 Dest. host unreachable (of course 4 times)

OBSERVED!!!: ID-1 responded RPT?:KJ4ACN G

NOW, using nx4y.dstar.local
again same statement, but 10.131.80.216, and of course, Dest. Host
UNRch.

OBSERVED!!!: ID-1 responded RPT?:W4RNT

WOW, W4RNT responded.....

tried yet another know user, WD4LWG,
same statements, this time RPT?:NI4CE
shows on the display during the 4 ping packets.....

OK, now I am seeing something here, knowing one's id, it's possible to
ping a person based on the "<pcname>.dstar.local" and observing the
output...

so for grins and giggles, let's ping Steve NU5D!!!
yup, same statements, but now I see on the display:
(pinging nu5d.dstar.local) RPT?:K5CTX

for each known user call sign, I get a response (if that IS WHAT IT
IS??) using the information I supplied above...

Question is, even though the laptop says, destination host unreachable,
that would be due to the internal network versus the real world, HOW is
the gateway forwarding the information to the other gateway???
EVEN IF THE END USER HAS THEIR ID-1 on, yet no ping reply, but the
gateway responds back RPT?:<gateway call sign>

I would guess the dstar gateway daemon is doing what it is supposed to
do, ROUTING the ping request, much like callsign routing...???...

Thanks for reading this, but I find this to be very neat and wild!

PS: I pinged Gerry Dalton too, display says: RPT?:K5TIT

Evans F. Mitchell
KD4EFM / AFA4TH FL / WQFK-894

Fla. D-Star Tech Support Group
www.florida-dstar.info

Polk ARES A.E.C.
www.polkemcomm.org

Train Safety:
There is a train coming
in either direction
at any time, ALWAYS
stop, look, & listen.
NEVER STOP ON A TRACK,
NO MATTER WHAT!



 

Reply via email to