14915Re: [aprsisce] Re: ISPort setup (was Bluetooth link)
- Jan 1, 2012First, you need the development version in order to have the IS-Server type port available . . . .However, I believe the code is all there and you can edit the XML file to create the port on teh "RELEASE VERSION" by:<!--RFPort[#]-->
<RFPort Name="Callsign-SSID">I think this needs to be the callsign - mine is
<Protocol>IS-Server</Protocol>Key to working #1
<Device> @Valid IP:Valid port</Device>Valid IP >>Next key to working usable address :127.0.0.1 is your own machine,and 0.0.0.0 will reply to anythingIf the computers are networked, use the valid IP of that machine (like: 18.104.22.168)Valid Port >>Use 14580 to be just like the real IS-servers, or use something else,but your other linking machines must matchI use 14585 on my local networkGood Luck - Happy New Year
--- On Sun, 1/1/12, mm1ptt <chris.mm1ptt@...> wrote:
From: mm1ptt <chris.mm1ptt@...>
Subject: [aprsisce] Re: Bluetooth link
Date: Sunday, January 1, 2012, 8:45 AMHow do I create an internal IS-server port?
I would like to setup APRSIS32 as the IS-server on my local network with UI-View and UISS connecting to and passing data through APRSIS32 to the real IS-servers.
I read from here:
To select 'IS-server' from the drop down menu but I dont have that option I have: KISS, AGW, KWD710(PKT), KWD710(APRS),FTM310v1.3, TEXT, and CWOP.
When I set a TEXT port and try to connect with UI-View I get a error message saying something like server port was forcefully closed.
--- In firstname.lastname@example.org, "Lynn W Deffenbaugh (Mr)" <kj4erj@...> wrote:
> I'm really not going to try to write a tutorial on TCP/IP communications
> and the implications and choices of "available' ports for new services.
> I'm hoping someone out there can point you to a suitable tutorial on the
> subject as it involves some semi-advanced networking concepts and has
> nothing particular to to do with APRS nor APRSISCE/32.
> That said, 127.0.0.1 is the IP address of your current machine (most of
> the time).
> Machines get specific IP addresses for each networking adapter that they
> may have. Win32 and Windows Mobile behave the same in this respect.
> ipconfig is the command-line command that will show you ALL of the
> network adapters you have a desktop Windows machine. There is no
> out-of-the-box way of discovering this information for a Windows Mobile
> device, but client's don't need to know this.
> Port numbers must be unique and available for any given service on the
> host that's attempting to offer the service. "Standard" TCP/IP services
> have "well-known" port numbers. http servers are on port 80. ftp
> servers are on 21. AGW's Packet Engine is normally on port 8000.
> APRS-IS filtered ports are typically 14580. APRS-IS full feed ports are
> typically 10152.
> What network adapter and/or port you might want to offer your own
> IS-Server from APRSIS32 is completely up to your whims. The IP address
> you use on the server side determines what clients will be allowed to
> connect. 0.0.0.0 means the client can be anywhere. 127.0.0.1 means the
> client must be on the same machine. <AdapterIPAddress> means that the
> client must be on that adapter's connected network (or at least LOOK
> like it's on that network - read up on NAT and firewalls and spoofing
> and such). As for the port, it just has to be a number that's available
> on the server machine. I use 2998, 2999, 3000, 6568, 6569, 40000, and
> who knows what all else, but what ports you can use depend on what you
> have running on your machine.
> And once you have the IS-Server configured, you can point your APRSISCE
> instance to the proper IP and port to connect to it. BUT as soon as
> you go mobile, you can't use the local IP address anymore and may not
> even be able to connect in from the Internet (capital I) because of any
> firewalls or NAT routers that your APRSIS32 server is hiding behind.
> Oh, and ActiveSync also makes up a private IP network between your
> desktop and Windows Mobile device while they're connected that only
> works when they're connected.
> Yep, more than I really want to go into. If you want to run a local
> APRS-IS server, there's a certain amount of networking saavy that you
> better have to make it work as supporting such efforts is really a
> one-off unique thing for each installation.
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> PS. The more versatile the tool, the larger the instruction manual.
> Ever see a cookbook that actually describes how to "fold an egg"? Nope,
> they all assume you've got some applicable knowledge from somewhere else.
> On 12/21/2011 4:02 PM, James Higgins wrote:
> > Lynn
> > I did see TCP/IP as one of the choices on each PC, however, it asked
> > for a IP port? Is there a procedure written that gives the port
> > numbers and any thing else I will need?
> > Jim KC2SZ
> > On Wed, Dec 21, 2011 at 3:39 PM, Lynn W Deffenbaugh (Mr)
> > <kj4erj@... <mailto:kj4erj@...>> wrote:
> > http://aprsisce.wikidot.com/doc:development-version
> > Even that version only supports the Serial Port Profile of
> > Bluetooth for connections to TNCs, and that only with the
> > Microsoft Bluetooth stack. You're not going to be able to lash an
> > APRSISCE instance to an APRSIS32 instance via Bluetooth via any
> > connections other than TCP/IP.
> > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> > On 12/21/2011 3:36 PM, James Higgins wrote:
> >> Lynn
> >> I am running the general release from 2011/08/20 on both PC's.
> >> I would like to do the direct Bluetooth.
> >> How do I download the latest development software?
> >> Jim KC2SZ
> >> On Wed, Dec 21, 2011 at 3:09 PM, Lynn W Deffenbaugh (Mr)
> >> <kj4erj@... <mailto:kj4erj@...>> wrote:
> >> 1) APRSIS32 doesn't support an IS-Server connection via
> >> BlueTooth - Only
> >> TCP/IP, but I'm not sure if that's what you're trying to do.
> >> 2) APRSISCE doesn't support an APRS-IS client connection via
> >> BlueTooth -
> >> Only TCP/IP, but I'm not sure if that's what you're trying to do.
> >> 3) Are you running the latest development on both platforms?
> >> I think
> >> the direct Bluetooth support is only in that release and not
> >> in the
> >> current general release from 2011/08/20 or so.
> >> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
> >> Win32
> >> On 12/21/2011 2:49 PM, James Higgins wrote:
> >> > I am trying to connect a Bluetooth link between a PocketPC
> >> Dell X50v
> >> > running WinCE 5.0 and aprsisce to an EEEPC running XP and
> >> aprsis32. I
> >> > am running the latest release of aprsis on both the
> >> PocketPC and EEEPC
> >> > however, I don't see any mention of Bluetooth under the Ports
> >> > configuration menu.
> >> >
> >> > The Bluetooth link works great under Active Sync on both
> >> these PC's.
> >> >
> >> > I have been able to connect a TH-72 to the EEEPC running
> >> apris32 and
> >> > now I want to pass this IS to the PocketPC via Bluetooth.
> >> >
> >> > Would appreciate any help setting up the Bluetooth link.
> >> >
> >> > Thanks
> >> >
> >> > Jim KC2SZ
> >> >
> >> >
> >> > ------------------------------------
> >> >
> >> > Yahoo! Groups Links
> >> >
> >> >
> >> >
> >> >
- << Previous post in topic Next post in topic >>