[ previous ] [ next ] [ threads ]
 From:  "Holger Bauer" <Holger dot Bauer at citec dash ag dot de>
 To:  "Todd D. Volz" <todd at stir dot org>, <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)
 Date:  Thu, 29 May 2008 09:56:52 +0200
Thank you for your suggestion. In fact this link is a point to point
link and I have a m0n0 running on a wrap at each end of the link. The
problem is the same at both ends using 2 different wraps, cables,... .
The m0n0s actually just do some trafficshaping on the link, no
firewalling, no vpn...nothing else. As I tested m0n0 1.233 and 1.3b11
which are based on different bsd versions I doubt that it is a freebsd
bug but maybe something in the way that m0n0 assigns the settings to the
nic. The nics are oboard SIS in pcengines wraps. This worked with old
versions on the same hardware with the same nics and from runing
ifconfig it actually seems to assign the speed and duplex, it's just
nnot used for some reason and falls back to autonegotiation (which in
the case of the ISP devices fails).


	From: Todd D. Volz [mailto:todd at stir dot org] 
	Sent: Thursday, May 29, 2008 9:42 AM
	To: Holger Bauer
	Subject: Re: [m0n0wall] Problem forcing speed and duplex mode
(in 1.233 as well as in 1.3b11)
	What is the command that you are using in your config to set the
speed and duplex?
	Is it possible to load Free-BSD 4.11 Stable on this box and see
if you can replicate the problem?
	How about FreeBSD 6?
	Although you have been able to make this work before through
m0n0wall, this does not seem like a problem with m0n0wall, but a problem
with FreeBSD, or a problem with the configuration.
	As the monowall system is fairly rigid, these additional steps
would be my next steps, provided the cabling has been verified, and the
NIC is still working correctly (I know they rarely go bad, but sometimes
they do).
	Another test would be to test your monowall box with another
manageable switch/device that you can set to 100/full.
	My steps for this would be:
	hook up laptop to ISP device with known good cable and 100/full
NIC settings, verify speed/duplex and no, crc/fcs errors.
	Next keep laptop settings and use existing ethernet patch cable
going to monowall box.
	If these work next it is off to test your monowall hardware with
devices under your control. (like above mentioned managed switch)
	If this step fails to work correctly (as I imagine it will fail)
then you need to try and verify your hardware with different software
other than monowall.
	If the hardware passes you then get to work the FreeBSD path
mentioned above, as I'm sure that if Manuel gets on this thread he will
state that driver issues need to be directed toward the FreeBSD
community.  If you can get the NICs to work in FreeBSD (versions that
Monowall uses) then you may be able to get Manuel's attention.
	A quick search of the forums didn't yield anything promising,
but you may also trying posting this question there.
	good luck.
	----- "Holger Bauer" wrote: 
	> 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
	> 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.
	> Holger
	> > -----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
	> > (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
	> > 
	> > 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
	> > 
	> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
	> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch