Steve,
I am running EchoLink Proxies at 44.60.44.253:443 and 44:60.44.254:80
I am woking on a SIP based VoIP system, it is not up at this time.
~Lynwood KB3VWG
Chris KQ6UP,
I noted the same behavior last month regarding my station connecting to others. You may wish to read over the January 2013 discussions regarding this.
It was determined that stations were using various Network Operating Systems and that users assumed services are available that were not. It was noted that there was difficulty with a JNOS stations reaching my station, this problem dissappeard when I maintained an open Telnet connection to them.
We came to a concurrence that for testing it's good to have all online 44 IPs respond to ping. Please note traceroute employs UDP ports 33434-33534, when setting up my router's firewall, I had to especially make sure I permitted echo-request and UDP ports 33434-33534 to my AMPR Hosts.
Others note that they perform a Telnet to AMPR Hosts in order to test them; that is not advisable, as not all AMPR IP hosts are Telnet enabled.
Also, feel free to Ping or Traceroute from the following address: http://kb3vwg-010.ampr.org/tools
~Lynwood KB3VWG
All,
I'm currently able to perform zone transfers for ampr.org and 44.in-addr.arpa from the AMPR Nameservers using BIND, I have a DNS server available at 44.60.44.3, it resolves the entire Internet for 44 hosts.
Also, only RF transmissions in the US are governed by the FCC (for Part 97 purposes); therefore, the ID must be in the transmission in some form or fashion, not necessarily in the DNS record. As all IPs are issued to an amateur, the IP can be identified (for the Internet's sake). If you are concerend about over the air ID, this will not solve the issue, as you are not identifying yourself in the process (which is the requirement). IP-over-AX.25 does not have such an issue as 802.11, which may use SSID, MAC Address Encoding, or perform some other regular transmission over RF-method that identifies your station.
~Lynwood KB3VWG
It should be noted that Windows actually uses ICMP type 30 packets for it's traceroute function:
ftp://ftp.iana.org/assignments/icmp-parameters/icmp-parameters.txt
where as most Unix systems use UDP port 33434 (I don't think it uses a range of ports.. just this one):
ftp://ftp.iana.org/assignments/port-numbers
Ps. Thanks for putting up that AMPR test portal Lynwood.. VERY helpful!
--David
Let me know if you're looking for VoIP peers. I've only got a very few numbers, but I'm willing to let you call them toll free until or unless things get out of hand.
On Fri, 2013-02-01 at 16:57 -0500, lleachii@aol.com wrote:
(Please trim inclusions from previous messages) _______________________________________________ Steve,
I am running EchoLink Proxies at 44.60.44.253:443 and 44:60.44.254:80
I am woking on a SIP based VoIP system, it is not up at this time.
~Lynwood KB3VWG _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
-
C.J. Adams-Collier KF7BMP -
David Ranch -
lleachii＠aol.com