On Wed, May 30, 2007 at 02:32:21PM +0300, Alexander Motin wrote:
A> Nikos Vassiliadis wrote:
A> >> In my case doing a few times:
A> >> ifconfig fxp0 192.168.1.71/16
A> >> ifconfig fxp0 192.168.1.71/24
A> >> locks the box.
A>
A> Doing this you are dropping all routes going via that network. Proba
Pang wrote (2007/05/31):
> I have asked many techs in Asianetcom and they blamed on TCPIP window
> sizing. I am not sure what it is, so I do a search in Google and find
More typical problem than TCP window size is Ethernet connection itself,
for example one side thinks it has 100 Mb/s half dupl
I'm working on improving the fiber support for the bce driver. One of
the devices supported by the
driver (the 5708) supports a 2.5G mode which is negotiated through next
pages operations during
normal auto negotiation. The mechanism for negotiating this speed uses
standards based
mechanisms, bu
> > I'm working on improving the fiber support for the bce
> driver. One of
>
> Should be fine but you might want to post a patch to be concrete.
>
> Sam
I'm just looking at adding a media type as follows:
#define IFM_2500_SX 21 /* 2500BaseSX - multi-mode fiber */
I've only br
David Christensen wrote:
I'm working on improving the fiber support for the bce driver. One of
the devices supported by the
driver (the 5708) supports a 2.5G mode which is negotiated through next
pages operations during
normal auto negotiation. The mechanism for negotiating this speed uses
stan
David Christensen wrote:
I'm working on improving the fiber support for the bce
driver. One of
Should be fine but you might want to post a patch to be concrete.
Sam
I'm just looking at adding a media type as follows:
#define IFM_2500_SX 21 /* 2500BaseSX - multi-mode fiber
