On May 9, 2007, at 10:40 AM, Chris Buechler wrote:

Alexandre Blardone wrote:
Hello,

I'd like to force 100Mbps full duplex on my WAN interface,
I know i have to add the following in the config file for the WAN interface section
            <media>100baseTX</media>
            <mediaopt>full-duplex</mediaopt>
            <bandwidth>100</bandwidth>
            <bandwidthtype>Mb</bandwidthtype>
Is that all i have to do ?

If you're going to force, you have to force whatever device your WAN port is connected to (switch, modem, router, or...) or you'll end up with a duplex mismatch. You usually don't want to force speed and duplex, no networking vendor recommends this practice anymore though it's commonly ingrained in some people's heads because when autoneg was first introduced it didn't always work well. This is 2007, not 1997, you almost always want to use auto.

My ISP requires to force full duplex for the 40Mbps WAN connection i have; auto-negotiating does not work for this connection. If i could use auto negotiating i would, it would save me a lot of headaches.



Is there a way to check what the connection negotiated to (10 vs 100Mbps, half vs full duplex)?

Status -> interfaces.

perfect.



Should i also use that to set the other interfaces to gigabit ?

The gig E standard requires autonegotiation (and must be full duplex) but you can set 1000baseTX. Again, I wouldn't recommend it. It can't force with gig, I presume what the driver does in that case is only advertises itself as a gigabit capable device and if the other side can't negotiate at gigabit it won't bring up the interface.
I'll leave it to auto negotiate, it seems to work right now. I am running some tests.

Thanks for your help.
Alex



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to