Thread Info
  • Locked Locked
  • Replies 41 replies
  • Subscribers 15 subscribers
  • Views 68993 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

Sophos UTM 9.406-3 released

twister5800


Up2Date 9.406003 package description:

Remark:
System will be rebooted

News:
Security Release

Bugfixes:
Fix [NUTM-1616]: [AWS] Change AMI type to HVM
Fix [NUTM-4839]: [AWS] AWS Instances in GovCloud need to use S3 buckets in GovCloud
Fix [NUTM-5013]: [Network] TCP Vulnerability (CVE-2016-5696)

RPM packages contained:
perf-tools-3.12.48-0.237935773.g86aa827.i686.rpm
ep-ha-aws-9.40-191.g83c01f2.rb1.noarch.rpm
ep-webadmin-9.40-640.g7ad4baa.rb8.i686.rpm
ep-cloud-ec2-9.40-26.g00cde1e.rb2.i686.rpm
kernel-smp-3.12.48-0.237935773.g86aa827.i686.rpm
kernel-smp64-3.12.48-0.237935773.g86aa827.x86_64.rpm
ep-release-9.406-3.noarch.rpm



This thread was automatically locked due to age.
Parents

  • Modifying the /var/chroot-dhcpc/etc/default.conf (and eth1.conf) did no good - I did take the interface down then up again, as well as rebooted the UTM and modem.

    Looking at the logs, eth1 (WAN) is having a problem getting a DHCP address from the modem.

    from system.log

    2016:09:15-11:05:14 opeth dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 4
    2016:09:15-11:05:18 opeth dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
    2016:09:15-11:05:29 opeth dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
    2016:09:15-11:05:35 opeth dhclient: No DHCPOFFERS received.
    2016:09:15-11:05:35 opeth dhclient: Trying recorded lease xx.xxx.xxx.xx
    2016:09:15-11:05:35 opeth dhclient: bound: renewal in 6585 seconds.
    2016:09:15-11:06:14 opeth dhclient: Killed old client process
    2016:09:15-11:06:14 opeth dns-resolver[4361]: DNS server failed to contact!

    (I've looked up solutions to this problem, and none helped.  It's possible I missed a solution out there somewhere however)

    I messed around with the timeout, modified the speed.  I'm at a loss here when "all" that was done was a firmware change.  I am temped to just nuke the thing and reload the iso image and my backup configuration.  But I want to learn from this.

  • in reply to korgull

    Well, now I'm stumped, my case might not have to do with the latest update after all.  I rolled back the firmware and restored my settings - same thing - WAN link is down.


    My WAN link won't even come up from the bare bones installation.  This appears to be a common problem, yet I can't find a solution.

  • in reply to korgull

    Disconnect your firewall from the modem, power down your firewall, power down your modem and leave your modem powered down for 1 minute.  Restore power to the modem and let it completely boot.  Plug the firewall back into the modem and power up the modem.  Leave your WAN link in automatic mode do not set a speed and duplex.  See if that gets you back.

Reply
  • in reply to korgull

    Disconnect your firewall from the modem, power down your firewall, power down your modem and leave your modem powered down for 1 minute.  Restore power to the modem and let it completely boot.  Plug the firewall back into the modem and power up the modem.  Leave your WAN link in automatic mode do not set a speed and duplex.  See if that gets you back.

Children
  • in reply to NathanPoulos

    NathanPoulos said:

    Disconnect your firewall from the modem, power down your firewall, power down your modem and leave your modem powered down for 1 minute.  Restore power to the modem and let it completely boot.  Plug the firewall back into the modem and power up the modem.  Leave your WAN link in automatic mode do not set a speed and duplex.  See if that gets you back.

    UNBELIEVEABLE!!!!!  I wasted several days on this! :(  Turns out all I had to do was wait a measly minute.


    Thanks

  • in reply to korgull

    Yup no problem. Modems will typically only attached to one MAC address and a basic quick reboot for some reason doesn't clear them.  Always good to do a good long power off when messing around with settings.  Also, setting the WAN NIC to gigabit or full duplex can be an issue.  Always use Auto negotiation unless you are hard setting both sides of the network cable.

Unfiltered HTML