That's exactly the problem. The ISP has set it's end to 100 mbit/s, full
duplex and not autonegotiate. They don't want to change it as this is
the default config that they ship everywhere. Doing autonegotation on
the m0n0 detects the correct speed but a wrong duplex mode which makes
the link nearly unusable (and I have voip running over it as well which
is highly critical realtime traffic). I only know this used to work with
older version (had to use it in some similiar cases already) of m0n0wall
but doesn't work with the versions I tested anymore. I don't want to
place a manageable switch in between the m0n0 and the provider device
just to be able to configure speed and duplex. Other option is to go
back to an older version of m0n0 where this still worked.
> -----Original Message-----
> From: Phil Brutsche [mailto:phil at brutsche dot us]
> Sent: Thursday, May 29, 2008 1:03 AM
> To: Holger Bauer
> Cc: m0n0wall at lists dot m0n0 dot ch
> Subject: Re: [m0n0wall] Problem forcing speed and duplex mode
> (in 1.233 as well as in 1.3b11)
> If you can't hard-code the speed and duplex on both sides of
> the ethernet link you shouldn't do it at all. If you do,
> you're setting yourself up for reliability and performance problems.
> What you are describing (host forced to 100 full, switch set
> to auto-negotiate and deciding to use 100 half) is exactly
> what the Ethernet specification says should happen when two
> ethernet devices are unable to use N-Way autonegotiation.
> The best thing to do would be to set the switch port
> properly, but if the ISP won't help the only real solution
> you have is to leave the Soekris at it's defaults, which are
> to auto-negotiate the link parameters.
> Holger Bauer wrote:
> > I'm at a loss and that ISP-provided device is out of my control and
> > they only allow that one default configuration. No way to change it
> > unfortunately.
> Phil Brutsche
> phil at brutsche dot us