Loading ...
Sorry, an error occurred while loading the content.
 

Re: [irlp-embedded] Frequent ipupdate Messages

Expand Messages
  • Keith VE7GDH
    Dave VE3BIP wrote... ... server 209.160.72.104. Cant obtain current IP ... That s an odd node callsign for 2106...
    Message 1 of 2 , Mar 9, 2008
      Dave VE3BIP wrote...

      > We see ipupdate messages frequently as per the
      > examples below. Can some explain what is happening
      > when these messages occur? Is this something to be
      > concerned about? Any recommendations?
      > Notice the messages that I observed on node 2090 is slightly
      > different than node 2106.

      > Node 2090
      > Feb 07 2008 18:34:51 -0500 ipupdate: Comms error to
      server 209.160.72.104. Cant obtain current IP

      > Node 2106 - sorry timestamps missing
      > -500: ipupdate: the ip has changed from 70.52.154.299 to 70.52.153.82
      > -500: ipupdate: comm error to server 209.160.72.104 cant obtain
      > current ip

      That's an odd node callsign for 2106...
      http://status.irlp.net/IRLPnodedetail.php?nodeid=2106

      I take it you get the same results if you run ipupdate manually?

      What happens if you do the following on each node... does they find e.g.
      204.13.249.70?

      ping checkip.dyndns.org

      Also, what happens if you....

      ping 63.208.196.105

      Keith VE7GDH
      Node 1148
    Your message has been successfully submitted and would be delivered to recipients shortly.