44/8 is still routable on the internet. I doubt you use all 16 million addresses locally you could just route a Class C 44.x.x.x/24 where you have your local resources so your not routing the whole 44/8 to a internal network. You could also add another hop with a higher metric to check your internet route for 44.0.0.0 hosts that are not in your network. Joe kd2nfc node 46596
On Aug 15, 2018, at 3:45 PM, info@rainerbertsch.de wrote:
Hi there, can someone tell me why the server register.allstarlink.org <http://register.allstarlink.org/> give an answer with the IP 44.98.254.145 ?
ping register.allstarlink.org <http://register.allstarlink.org/> PING register.regsvcs.allstarlink.org <http://register.regsvcs.allstarlink.org/> (44.98.254.145): 56 data bytes 64 bytes from 44.98.254.145: icmp_seq=0 ttl=51 time=151.827 ms 64 bytes from 44.98.254.145: icmp_seq=1 ttl=51 time=151.208 ms
In our systems all ll IP-adresses with ip 44.x.x.x are routed to the HAMNET, never to the Internet. Therefore the system never can reach the registration server.
Or is there something wrong in my thoughts ?
73 de Rainer, DF3SY
Node 43024
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.