This is just a report, if somebody could find it useful.
I'm testing 0.9 b2 on an Aus V-series Barebone (MB M2A-VM AMD 690G chipset, 2Gb RAM dual-channel, Athlon X2 4400).
It's a kind of machine I often use with Windows XP. It's not perfect, but it works fine.
Onboard there is a Realtek 8169. I added another 8169 PCIE and 2 8139 PCI (a total of 4 net interface).
I made 2 fully virtualized VM, one for Endian firewall (Linux 2.6, IPCOP based, using 3 vbridges) and one for FreeNAS (FreeBSD 6.3 based using 1 vbridge).
Everything works very well. The new network framework is excellent.
The only problem I had is about PCI latency timer. With default bios value of 64 CLK, one or two cards randomly failed to be identified and the MAC address resulted totally scrambled with values made by random sequences of bytes 24, aa, 55, 00, ff (hex).
Every time I had to manually remove z25_persistent-net.rules and reboot.
The weakest card was the external PCIE. Changing the cards, obviously did not solve the problem.
I had to set PCI latency timer to 128 in order to get a stable machine.
It's a very strange behaviour because I never noticed nothing similar in Windows, so I suspect there are some kernel parameters to tune.
I'm not a kernel guru. Maybe someone could explain what exactly happened?
Claudio
I'm testing 0.9 b2 on an Aus V-series Barebone (MB M2A-VM AMD 690G chipset, 2Gb RAM dual-channel, Athlon X2 4400).
It's a kind of machine I often use with Windows XP. It's not perfect, but it works fine.
Onboard there is a Realtek 8169. I added another 8169 PCIE and 2 8139 PCI (a total of 4 net interface).
I made 2 fully virtualized VM, one for Endian firewall (Linux 2.6, IPCOP based, using 3 vbridges) and one for FreeNAS (FreeBSD 6.3 based using 1 vbridge).
Everything works very well. The new network framework is excellent.
The only problem I had is about PCI latency timer. With default bios value of 64 CLK, one or two cards randomly failed to be identified and the MAC address resulted totally scrambled with values made by random sequences of bytes 24, aa, 55, 00, ff (hex).
Every time I had to manually remove z25_persistent-net.rules and reboot.
The weakest card was the external PCIE. Changing the cards, obviously did not solve the problem.
I had to set PCI latency timer to 128 in order to get a stable machine.
It's a very strange behaviour because I never noticed nothing similar in Windows, so I suspect there are some kernel parameters to tune.
I'm not a kernel guru. Maybe someone could explain what exactly happened?
Claudio
