Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 83 replies
  • Subscribers 2 subscribers
  • Views 30376 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

Soft-Release v7.402

trollvottel
Today we soft-released v7.402 on our FTP-Servers (ftp.astaro.de for sure). The GA release will follow a few days later, if everything goes well. Use the easter holidays to find out [:D]

Please check intensively, if your NIC sorting stays as expected. We updated Intel e1000 driver and integrated e1000e so there is still a small possibility something may go wrong although we tested that thoroughly.

Update:
We just uploaded a fixed Up2Date package for v7.402 to our FTP-Server (ftp.astaro.de, Mirrors may take a while to sync). This new version should not break your VLANs (and probably other devices) anymore.

Make sure you download the correct new version:
MD5sum: a24570c061234f1ebf0509c1104f9423
Size: 143157552 bytes

It is possible to "repair" a broken v7.402 update by decrementing /etc/version to v7.401, deleting /var/lib/nics, installing the new fixed update and then re-assign the phyiscal hardware devices to your vlan devices via webadmin.

Sorry for inconvenience but thanks to your support, the GA release will not have that problem [H]


This thread was automatically locked due to age.
Parents
  • 0
    Today we soft-released v7.402 on our FTP-Servers (ftp.astaro.de for sure). The GA release will follow a few days later, if everything goes well. Use the easter holidays to find out [:D]

    Please check intensively, if your NIC sorting stays as expected. We updated Intel e1000 driver and integrated e1000e so there is still a small possibility something may go wrong although we tested that thoroughly.


    Are only the drivers have been updated?
    [LEFT]Can you provide the full list of changes in 7.402 version?[/LEFT]
  • 0 in reply to WaMaR
    Hi WaMar,


    Up2Date 7.402 package description:

    Remarks:
     Configuration will be upgraded
     System will be rebooted

    News:
     Updated Intel e1000 driver - NIC ordering should not be affected, nevertheless please check after installation
     Updated SIP support for better integration
     Improved database maintenance processing times
     Improved Multipath to handle more than 64 rules
     Improved ACC integration

    Bugfixes:
     Fix [7900]: VLAN sometimes fails on LAG devices
     Fix [9376]: Ipsec VPN tunnel not coming up after takeover
     Fix [10108]: ASG 525-F eth8 and eth9 may loose link
     Fix [10147]: IPsec tunnels with remote network 'Any' will not work
     Fix [10158]: Multipath persistence by connection not working properly
     Fix [10189]: Usergroups with umlauts are not working in HTTP Proxy profiles
     Fix [10200]: Problem with auto packetfilter rules for outgoing traffic

    RPM packages contained:
     ulogd-2.0.1-18.i686.rpm                           
     chroot-ipsec-7.4-33.i686.rpm                      
     ddclient-3.7.3-8.i686.rpm                         
     kernel-default-2.6.16.62-110.i686.rpm             
     kernel-smp-2.6.16.62-110.i686.rpm                 
     iptables-1.3.5-24.i686.rpm                        
     libnfnetlink-0.0.39-3.i686.rpm                    
     libnetfilter_conntrack-0.0.99-3.i686.rpm          
     conntrack-tools-0.9.6-4.i686.rpm                  
     ctsyncd-0.9.3-12.i686.rpm                         
     chroot-smtp-7.4-199.i686.rpm                      
     ethtool-3-15.2.2.i686.rpm                         
     ep-init-7.4-185.i686.rpm                          
     ep-libs-7.4-225.i686.rpm                          
     ep-mdw-7.4-474.i686.rpm                           
     ep-confd-7.4-607.i686.rpm                         
     ep-webadmin-contentmanager-7.4-227.i686.rpm       
     ep-aua-7.4-210.i686.rpm                           
     ep-syslog-ng-7.4-114.i686.rpm                     
     ep-notifier-db-7.4-80.i686.rpm                    
     ep-reporting-7.4-283.i686.rpm                     
     ep-chroot-ipsec-7.4-62.i686.rpm                   
     ep-chroot-smtp-7.4-220.i686.rpm                   
     cm-nextgen-agent-7.4-59.i686.rpm                  
     ep-chroot-pop3-7.4-109.i686.rpm                   
     ep-httpproxy-2.1-175.i686.rpm                     
     ep-webadmin-7.4-635.i686.rpm                      
     ep-webadmin-languages-7.4-41.i686.rpm             
     ep-up2date-7.4-130.i686.rpm                       
     ep-up2date-downloader-7.4-118.i686.rpm            
     ep-tools-7.4-106.i686.rpm                         
     u2d-mpfc-7-1.i686.rpm                             
     ep-toolbox-7.4-59.i686.rpm                        
     kernel-bigsmp-2.6.16.62-110.i686.rpm              
     ep-asg-7.4-33.i686.rpm                            


    Ian M
  • 0 in reply to Marcel_01
    Hi Marcel,
    VLANs are all on eth1.
    eth2 and eth3 are inactive (and not connected to a switch) since I converted to VLANs awhile back.


    # ifconfig -a
    eth0      Link encap:Ethernet  HWaddr 00:A0:C9:B8:8B:48
              inet addr:a.b.c.d  Bcast:255.255.255.255  Mask:255.255.248.0
              UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:9720248 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1661241 errors:1 dropped:0 overruns:0 carrier:1
              collisions:0 txqueuelen:1000
              RX bytes:1577209853 (1504.1 Mb)  TX bytes:483498142 (461.0 Mb)

    eth1      Link encap:Ethernet  HWaddr 00:90:27:2A:75[[[[[:D]]]]]5
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:1628585 errors:2 dropped:0 overruns:0 frame:2
              TX packets:1770593 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:487000528 (464.4 Mb)  TX bytes:1099452649 (1048.5 Mb)

    eth1.10   Link encap:Ethernet  HWaddr 00:90:27:2A:75[[[[[:D]]]]]5
              inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:301 errors:0 dropped:0 overruns:0 frame:0
              TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:15080 (14.7 Kb)  TX bytes:828 (828.0 b)

    eth1.11   Link encap:Ethernet  HWaddr 00:90:27:2A:75[[[[[:D]]]]]5
              inet addr:192.168.211.1  Bcast:192.168.211.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:859519 errors:0 dropped:0 overruns:0 frame:0
              TX packets:971112 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:143278713 (136.6 Mb)  TX bytes:608628375 (580.4 Mb)

    eth1.13   Link encap:Ethernet  HWaddr 00:90:27:2A:75[[[[[:D]]]]]5
              inet addr:192.168.11.1  Bcast:192.168.11.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:765782 errors:0 dropped:0 overruns:0 frame:0
              TX packets:795796 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:319767624 (304.9 Mb)  TX bytes:486479550 (463.9 Mb)

    eth2      Link encap:Ethernet  HWaddr 00:A0:C9:5D:FC:A2
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    eth3      Link encap:Ethernet  HWaddr 00:A0:C9[[[[[:D]]]]]1:BF:BD
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    ifb0      Link encap:Ethernet  HWaddr E6:70:0C:99:70:51
              UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:3702424 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:32
              RX bytes:0 (0.0 b)  TX bytes:2208346266 (2106.0 Mb)

    ifb1      Link encap:Ethernet  HWaddr C6:06:3F:0D:5E:5C
              BROADCAST NOARP  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:32
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    ifb2      Link encap:Ethernet  HWaddr 02:BA:33:C2:4F:79
              BROADCAST NOARP  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:32
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    ipsec0    Link encap:Ethernet  HWaddr 00:A0:C9:B8:8B:48
              inet addr:76.83.24.57  Mask:255.255.255.255
              UP RUNNING NOARP  MTU:1420  Metric:1
              RX packets:1474 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1228 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:10
              RX bytes:1431901 (1.3 Mb)  TX bytes:284104 (277.4 Kb)

    ipsec1    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              NOARP  MTU:0  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:10
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    ipsec2    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              NOARP  MTU:0  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:10
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    ipsec3    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              NOARP  MTU:0  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:10
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:2810076 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2810076 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:679866925 (648.3 Mb)  TX bytes:679866925 (648.3 Mb)

    tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
              inet addr:10.242.2.1  P-t-P:10.242.2.2  Mask:255.255.255.255
              UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:100
              RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


    I'm not sure what ifbX are... I'm not doing bridging, although I have in the past.

    Thanks,
    Barry
  • 0 in reply to BarryG
    hmm.... ifb0 is showing traffic in those stats... are you sure you don't have 2 ports set to bridge together?  Maybe there's some "garbage" config info floating around in that configuration db that's "sort of" bridging some ports together?

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    hmm.... ifb0 is showing traffic in those stats... are you sure you don't have 2 ports set to bridge together?  Maybe there's some "garbage" config info floating around in that configuration db that's "sort of" bridging some ports together?


    It's disabled according to webmin:

    Bridge status Enable  

    Bridge configuration 

    No bridge is currently configured.
    Enable Bridge status above to configure a new bridge.


    Barry
  • 0 in reply to BarryG
    AFAIK, ifbX devices are mirror devices. They can be used to mirror specific (filtered) traffic from an ethX to ifbX.

    Explanation and example usage: Net:IFB - The Linux Foundation

    They are not used for bridging.
  • 0 in reply to trollvottel
    So why is that interface there?  I don't see it on any of my other installations.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Bruce, the article Mario offered included a mention of QoS.  Could that be it?
     
    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
    I' ve just updated my first post, please read. New Up2Date package!
  • 0 in reply to trollvottel
    Mario, do you have to delete the /var/lib/nics file if you don't have VLANs defined, in order to reinstall the up2date?  If one deletes that file, does it affect connectivity at all whilst getting the up2date installed, and will the NICs come back up OK after the reboot?  For that matter, in order for future up2dates to install, do you have to reinstall the newer "fixed" 7.402 up2date, or will future ones overwrite the one I have installed?

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Is this the GA or a fixed "beta" ?
  • 0 in reply to PabloDiablo
    Is this the GA or a fixed "beta" ?


    fixed beta....just read the update on page 1 [:D]
Reply Children
No Data
Cookie Information Banner