The only reason for this to happen (at least that I can see) is that the 
interface numbers change.  Within the entriesfile we keep the interface number 
(RINT) and when performing the "route add" or when showing the settings in the 
GUI we use that parameter. 
If the numbers of the interfaces change or new are added or some removed then 
the interface number will indeed change and this could cause this behaviour. 
 
 

Dirk Bulinckx 
Servers Alive - http://www.woodstone.nu (http://www.woodstone.nu/) 
StellarDNS (DNS Hosting) - http://www.stellardns.com 
(http://www.stellardns.com/)  

--------------------------------------------------------------------------------

From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of 
Anthony Laatz
Sent: Monday, May 21, 2012 11:46 PM
To: Servers Alive Discussion List
Subject: [SA-list] Network Route Build Faiure





I am using 7.0.2515, and I’ve also upgraded to the latest  7.0.2515. 

 

Under one of the entries on the NETWORK tab,  I have the entry create a 
temporary route so it can check a specific router just outside of our network. 
It’s been running clean for the past couple months. Today I rebooted the 
machine SA is on since Windows updates wanted to. When it came back up the 
INTERFACE option on that NETWORK tab changed from the local NIC to the loopback 
interface, thus causing the check to fail. I first upgraded to 7.0.2525 to see 
if that would resolve it and it didn’t. So I changed it manually, saved 
it and ran it again and it worked. I also restarted the machine again and the 
change to the local NIC stuck. So I am unable to recreate the issue, but this 
isn’t the first time this has happened with this particular setting. I 
have this route creation setup in multiple entries under different groups. All 
the options related to the interface changed to the Loopback interface. 

 

Though it is not a big or critical issue, it does happen randomly and will 
catch you off guard.  Like I said I cannot recreate it consistently so I 
don’t know if there is much that can be done to resolve it.  L 

 

Thank you, 

 

anthony Laatz | appletree Answers 

p: 800.270.7030 f: 866.827.8802 

e: ala...@appletreeanswers.com (mailto:ala...@appletreeanswers.com) 

 

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list. 

To unsubscribe send a message with UNSUBSCRIBE in the subject line to 
salive@woodstone.nu
If you use auto-responders (like out-of-the-office messages), make sure that 
they are not sent to the list nor to individual members. Doing so will cause 
you to be automatically removed from the list.

Reply via email to