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

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.

0 BrucekConvergent over 16 years ago in reply to Marcel_01

Any word on this? I've installed the update on a couple of machines, no problems yet; one had e1000 nics in it. None had e100 though, like Barry.

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 BarryG over 16 years ago in reply to Marcel_01

Barry, you wrote about errormessages appearing 3 times on bootup. Can you remember the lines from normal bootup where those error messages appeared in-bettween? If I had to guess, I'd assume the following:
- Errors appeared 3x (basically at same time) after 'Starting NIC initialization'
- Your interfaces disappeared afterwards ('ifconfig -a' or 'ip addr' did not show them anymore)
- Rebooting did not help (same procedure every bootup)

Hi Marcel,
That's right... the 2 errors appeared together 3x, near the end of the boot sequence. I'm pretty sure it was after the NIC init.

ifconfig did not show any of the internal interfaces / vlans.

rebooting didn't help.

If needed, I can install the upgrade again, maybe this afternoon (about 3 hours from now), or tonight, but I can't leave it like that for too long.
What timezone are you in?
If I could do it at night, and if you're in Europe, then you could work on it during your day while I'm sleeping.

Also note that I sent a config backup file to support under the case # posted in this thread before ([Ticket#2009041010000117] CaseID 00094825).

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 Marcel_01 over 16 years ago in reply to BarryG

Barry,

thanks for getting back on this. We'd like to clarify but will check for the specific hardware in our lab first to double check if it is hardware or VLAN related (or both).

Can you please let me know on which interfaces you use VLANs? (e.g. post an ifconfig -a output.. IPs can be scrambled)

Thanks,
Marcel

PS: I'm located in Germany (GMT+2).
Cancel
Vote Up 0 Vote Down

Cancel

0 BarryG over 16 years ago 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 BrucekConvergent over 16 years ago 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.
Cancel
Vote Up 0 Vote Down

Cancel
0 BarryG over 16 years ago 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
Cancel
Vote Up 0 Vote Down

Cancel
0 trollvottel over 16 years ago 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.
Cancel
Vote Up 0 Vote Down

Cancel
0 BrucekConvergent over 16 years ago 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.
Cancel
Vote Up 0 Vote Down

Cancel
0 BAlfson over 16 years ago 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
Cancel
Vote Up 0 Vote Down

Cancel
0 trollvottel over 16 years ago in reply to BAlfson

I' ve just updated my first post, please read. New Up2Date package!
Cancel
Vote Up 0 Vote Down

Cancel