-On [2325 08:00], Andrew Sherrod ([EMAIL PROTECTED]) wrote:
>
>My 3.4 machine at work has periodic problems with the
>fxp. No performance issues (perhaps a little slow, but
>the network is congested enough that this is hard to
>measure). However it does periodically display an
>error message a
My 3.4 machine at work has periodic problems with the
fxp. No performance issues (perhaps a little slow, but
the network is congested enough that this is hard to
measure). However it does periodically display an
error message about "PHYS" and "unsupported". I am
home right now, so I can't reprodu
> Also I tried to set mtu 1200 to my fxp, and login other
> machines with mtu 1500, and did `ls -lR /`, and also there
> seems to be no problem.
Woops, this latter check was meaningless for checking
fragments. No fragments were happening due to tcp mss
negotiation and path mtu discovery.
Yoshin
> [cc:'d shin]
:-) I have only fxp and fe for 4.0/5.0 machines at my work
place, but I have a 4.0 machine with ep at my home. I think
I'can test it tonight if it also happens in my environment.
As far as I confirmed it here, many pinging with -s 1600 won't
make any problems between my 3.x/4.0/5
| > Is anyone else seeing odd behaviour with a fairly recent -current, an ep
| > driver nic card and fragmented packets?
|
| If I understand things correctly, Matt Dillon and a cast of thousands
| just committed a fix to this problem. Try cvsup'ing and make'ing world
| and see if that help
Dan Moschuk wrote:
>
> Is anyone else seeing odd behaviour with a fairly recent -current, an ep
> driver nic card and fragmented packets?
If I understand things correctly, Matt Dillon and a cast of thousands
just committed a fix to this problem. Try cvsup'ing and make'ing world
and see i
[cc:'d shin]
-On [2324 00:04], Dan Moschuk ([EMAIL PROTECTED]) wrote:
>
>Is anyone else seeing odd behaviour with a fairly recent -current, an ep
>driver nic card and fragmented packets?
Yes. And add to that a fxp card as well next to the ep card.
For some weird reason (almost) every packe
Is anyone else seeing odd behaviour with a fairly recent -current, an ep
driver nic card and fragmented packets?
--
Dan Moschuk ([EMAIL PROTECTED])
"Waste not fresh tears on old griefs."
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messa
