2006/11/7, Marat N.Afanasyev <[EMAIL PROTECTED]>:
Oliver Fromme wrote:
> Marat N.Afanasyev wrote:
> > bge0: flags=8843 mtu 1500
>
> Ok, I also have a machine with bge(4) NIC within reach.
> I've had a look at it for similar symptoms (see below).
>
> > bge0 1500 00:50:45:5f:4f:78 23410
Oliver Fromme wrote:
Marat N.Afanasyev wrote:
> bge0: flags=8843 mtu 1500
Ok, I also have a machine with bge(4) NIC within reach.
I've had a look at it for similar symptoms (see below).
> bge0 1500 00:50:45:5f:4f:78 2341018 799 3062828
> 0 0
799 is not good, but I wouldn't
Marat N.Afanasyev wrote:
> bge0: flags=8843 mtu 1500
Ok, I also have a machine with bge(4) NIC within reach.
I've had a look at it for similar symptoms (see below).
> bge0 1500 00:50:45:5f:4f:78 2341018 799 3062828
> 0 0
799 is not good, but I wouldn't call it "huge amount of
Oliver Fromme wrote:
Marat N.Afanasyev <[EMAIL PROTECTED]> wrote:
> I've encountered a very strange situation about two hours ago. I use
> squid as transparent proxy and forward all the packets from port 80 to
> port 8000. Problem is, first of all, I have a lot of ierrs on interface
> when
Marat N.Afanasyev <[EMAIL PROTECTED]> wrote:
> I've encountered a very strange situation about two hours ago. I use
> squid as transparent proxy and forward all the packets from port 80 to
> port 8000. Problem is, first of all, I have a lot of ierrs on interface
> when looking to interface s
Hello!
I've encountered a very strange situation about two hours ago. I use
squid as transparent proxy and forward all the packets from port 80 to
port 8000. Problem is, first of all, I have a lot of ierrs on interface
when looking to interface stats using netstat. The second problem is far
m
