We upgraded to 7.2 a few months back and have had a few instances since
then where our default route got bound to another interface on the
rather than the one it always bound to in the past... has anyone elseseen
We have now seen it occur on two separate systems..
I am planning to use the 'preffered binding interface' option on the
default route to prevent this in the future, but it has always been set
"*NONE" in the past, and we've not seen the problem until recently.--
Does anyone know if something specific changed with 7.2 that might have
precipitated this problem?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.