Re: Intel 82559 NIC corrupted EEPROM

2007-08-14 Thread Amin Azez
Regarding the thread accessible at: http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26 that ended with "looks like it is specific to your hardware", Can I check where we are with this? I've just had a small installation run fail on 3 boxes with the same problems,

Re: Intel 82559 NIC corrupted EEPROM

2007-08-14 Thread Amin Azez
Regarding the thread accessible at: http://groups.google.com/group/linux.kernel/browse_frm/thread/bdc8fd08fb601c26 that ended with looks like it is specific to your hardware, Can I check where we are with this? I've just had a small installation run fail on 3 boxes with the same problems,

Re: [PATCH] chaostables

2007-03-09 Thread Amin Azez
* Jan Engelhardt wrote, On 09/03/07 10:19: > Hello, > > On Mar 9 2007 09:35, Amin Azez wrote: > >> * Jan Engelhardt wrote, On 08/03/07 20:26: >> >>> xt_portscan needs to keep track of what packets the machine has already >>> seen. So on the f

Re: [PATCH] chaostables

2007-03-09 Thread Amin Azez
* Jan Engelhardt wrote, On 08/03/07 20:26: > xt_portscan needs to keep track of what packets the machine has already > seen. So on the first SYN, the connection is marked with "1". (Then we > send our SYN-ACK... and the connection turns ESTABLISHED.) The next > packet that is received will be

Re: [PATCH] chaostables

2007-03-09 Thread Amin Azez
* Jan Engelhardt wrote, On 08/03/07 20:26: xt_portscan needs to keep track of what packets the machine has already seen. So on the first SYN, the connection is marked with 1. (Then we send our SYN-ACK... and the connection turns ESTABLISHED.) The next packet that is received will be an ACK

Re: [PATCH] chaostables

2007-03-09 Thread Amin Azez
* Jan Engelhardt wrote, On 09/03/07 10:19: Hello, On Mar 9 2007 09:35, Amin Azez wrote: * Jan Engelhardt wrote, On 08/03/07 20:26: xt_portscan needs to keep track of what packets the machine has already seen. So on the first SYN, the connection is marked with 1. (Then we send

Re: e100 breakage located

2006-12-09 Thread Amin Azez
Jesse Brandeburg wrote: sorry for the delay, your mail got marked as spam. In the future please copy networking issues to netdev@vger.kernel.org, and be sure to copy the maintainers of the driver you're having problems with (they are in the MAINTAINERS file) On 11/22/06, Amin Azez <[EM

Re: e100 breakage located

2006-12-09 Thread Amin Azez
Jesse Brandeburg wrote: sorry for the delay, your mail got marked as spam. In the future please copy networking issues to netdev@vger.kernel.org, and be sure to copy the maintainers of the driver you're having problems with (they are in the MAINTAINERS file) On 11/22/06, Amin Azez [EMAIL