Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 2 subscribers
  • Views 1320 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Local ethernet no longer found after up2date auto update

lelandv
Hi All, 

Having just allowed Astaro7 to perform the auto up2date installation (the latest one that required the reboot), the local ethernet (VMware Bridged Mode) is no longer found so the system has no connectivity.  Before this update it worked fine.

There's nothing in the boot log or dmesg to indicate anything out of the ordinary, but in the console the only interfaces active are lo0 and ppp0.

Any ideas?

Thanks, 

Leland


This thread was automatically locked due to age.
Parents
  • 0
    leland, what version update did you do?  V7.304 -> V7.305 or ???
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    leland, what version update did you do?  V7.304 -> V7.305 or ???


    It was 7.304 to 7.305 -- which required the reboot... after the reboot the ethernet interface "disappeared".

    Was going to further update it to 7.306 to prepare for 7.4 but of course without a network connection, the box can't really do that at the moment... [:(]

    L.
  • 0 in reply to lelandv
    Have you tried rebooting?  Are the interfaces still defined, but just not bridged?
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Reboot no good.

    At the linux console, there is, all of a sudden, not even an ethernet interface showing in ifconfig -a
    Just a loopback and a ppp interface.

     * lelandv reinstalls from scratch

    *grumble*
  • 0 in reply to lelandv
    We had similiar problems in the past with our Astaros running as vm on an ESX server with AMD CPU... On the one with Intel CPUs the problem never occured.

    We started using the downloaded VMware images and the problem was gone.
Reply
  • 0 in reply to lelandv
    We had similiar problems in the past with our Astaros running as vm on an ESX server with AMD CPU... On the one with Intel CPUs the problem never occured.

    We started using the downloaded VMware images and the problem was gone.
Children
Cookie Information Banner