On Friday 24 June 2005 06:15 pm, Vlad GALU wrote:
> On 6/25/05, Greg Rowe <[EMAIL PROTECTED]> wrote:
> > Greetings,
> > I've been chasing a network interface "freeze" problem on and off for
> > some time now and it's driving me nuts !
> Are you sure that's not your catalyst forgetting about the
On 6/25/05, Greg Rowe <[EMAIL PROTECTED]> wrote:
> Greetings,
> I've been chasing a network interface "freeze" problem on and off for some
> time now and it's driving me nuts !
>
> The problem occurs on two identical mail servers that sit behind a firewall.
> Both systems have two ethernet interf
On 6/25/05, Greg Rowe <[EMAIL PROTECTED]> wrote:
> Greetings,
> I've been chasing a network interface "freeze" problem on and off for some
> time now and it's driving me nuts !
>
> The problem occurs on two identical mail servers that sit behind a firewall.
> Both systems have two ethernet interf
Greetings,
I've been chasing a network interface "freeze" problem on and off for some
time now and it's driving me nuts !
The problem occurs on two identical mail servers that sit behind a firewall.
Both systems have two ethernet interfaces and when I'm having this problem
the external inter
On 6/24/05, ming fu <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In the 4.x kernel, ipfilter was hardcoded before ipfw in the ip_input().
> However, in the 5.x kernel, they register themselve to the pfil hook. As
> there isn't a priority number during the hook up, looks like who ever
> register first get
Hi,
In the 4.x kernel, ipfilter was hardcoded before ipfw in the ip_input().
However, in the 5.x kernel, they register themselve to the pfil hook. As
there isn't a priority number during the hook up, looks like who ever
register first get to filter the packet first.
In case I want to preserv
