Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 May 2007 08:20:50 -0700 (PDT)
From:      Craig Russell <crussell_1969@yahoo.com>
To:        freebsd <freebsd-questions@freebsd.org>
Subject:   Re: Wierd Network problem
Message-ID:  <20070514152051.48723.qmail@web51612.mail.re2.yahoo.com>
In-Reply-To: <72cf361e0705132354o39c81836gea8934324b45a777@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Yes,
I could use something other than cpanel, and
directadmin was actually one of my choices but
unfortunately, that decision was not mine.  I'm only
responsible for getting the software that was chosen
to work.

My issue with the patch was that it was written for
if_bge.c dated in March 2006 and I actually compiled a
new kernel using the release from December 2006. 
Everything that I read about the bug said that it was
fixed in the 6.2-release tree so I thought that would
be ok. 

Tcpdumps did show massive amounts of bad chksum's from
packets off of the network so it looks as though that
was my issue.  Not sure why it didn't work after the
recompile.  I ended up having to install a new card
and a linksys gigabit card is working nicely now.

Thanks for all of the suggestions.

Craig Russell

--- Martin Hepworth <maxsec@gmail.com> wrote:

> Craig
> 
> applying the patch should be easy enough. You could
> always use something
> better than cpanel, I've always perferred
> directadmin myself.
> 
> --
> martin
> 
> On 5/13/07, Craig Russell <crussell_1969@yahoo.com>
> wrote:
> >
> > Yes, I have tried different cables, even different
> > physical ports (although same type of port). 
> There
> > was a bug filed against 6.1 for the bge interfaces
> > that maybe related, although the bug indicated
> > absolutely no network conductivity.  There was a
> patch
> > released and I'm trying to recompile with that
> patch.
> > I must admit I'm having a hard time figuring out
> how
> > to apply the patch but once I get past that hurdle
> > I'll see what happens.
> >
> > If I can't ge the bge interface working my next
> best
> > solution will be to just install another card in
> one
> > of the pci slots and use that instead.  Ideally, I
> > would upgrade to 6.2 but cpanel won't support 6.2
> so
> > I'm stuck on 6.1 for the time being.
> >
> > Thanks for the reply,
> >
> > Craig Russell
> >
> > --- Martin Hepworth <maxsec@gmail.com> wrote:
> >
> > > Criag
> > >
> > > have you tried cables? Could be a duff network
> cable
> > > or even speed mismatch
> > > between you and the router/switch.
> > >
> > > -
> > > martin
> > >
> > > On 5/12/07, Craig Russell
> <crussell_1969@yahoo.com>
> > > wrote:
> > > >
> > > > I have a dell poweredge 6650 installed with
> > > freebsd
> > > > 6.1 and on the local router, everything works
> > > great
> > > > (ie, a computer on a different subnet off the
> same
> > > > router can access it fine) but coming from
> outside
> > > of
> > > > the network access is incredibly slow.  My
> first
> > > > thought was that it must be a routing issue,
> but I
> > > > have two other freebsd 6.1 servers on that
> same
> > > subnet
> > > > and I can access them fine from outside.  I
> dug a
> > > > little further and compared the servers that
> are
> > > > working with those that are not and these are
> the
> > > > differences that I have found.
> > > >
> > > > On the servers that are working (dell
> poweredge
> > > > 2450's) the interface is an fxp0 and here is
> the
> > > > output of ifconfig:
> > > > fxp0:
> > > >
> flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> > > mtu
> > > > 1500
> > > > options=8<VLAN_MTU>
> > > > inet6 fe80::2b0:d0ff:fee1:f66a%fxp0 prefixlen
> 64
> > > > scopeid 0x1
> > > > inet 64.25.218.2 netmask 0xffffff80 broadcast
> > > > 64.25.218.127
> > > > ether 00:b0:d0:e1:f6:6a
> > > > media: Ethernet autoselect (100baseTX
> > > <full-duplex>)
> > > >         status: active
> > > >
> > > > on the server that is not working:
> > > >
> > > > bge0:
> > > >
> flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> > > mtu
> > > > 1500
> > > >
> options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
> > > > inet6 fe80::211:43ff:fedc:9aa2%bge0 prefixlen
> 64
> > > > scopeid 0x1
> > > > inet 64.25.218.10 netmask 0xffffff80 broadcast
> > > > 64.25.218.127
> > > > ether 00:11:43:dc:9a:a2
> > > > media: Ethernet autoselect (100baseTX
> > > <full-duplex>)
> > > > status: active
> > > >
> > > > The first thing that i noticed is that on the
> > > option
> > > > line there is quite a bit of difference
> between
> > > the
> > > > two.  So using the command line ifconfig tool
> I
> > > > removed RXCSUM, TXCSUM from the bge0
> interface.
> > > > Voila!  Speed increased and the server was
> > > actually
> > > > accessible from off net.  Unfortunately, as
> soon
> > > as I
> > > > tried to access any other port, the interface
> > > crashes.
> > > > Eventually the watchdog picks up on that and
> > > restarts
> > > > the interface.  But the problem is completely
> > > > repeatable.
> > > >
> > > > The server that I am having problems with is
> > > running
> > > > cpanel 10.9; the two that are working are
> running
> > > the
> > > > dns-only version of cpanel.  I am not picking
> up
> > > any
> > > > errors in the logs.  This could be related to
> > > cpanel,
> > > > or not, I'm not really sure, although it
> shouldn't
> > > be.
> > > >
> > > > The other unique thing about the setup, that
> very
> > > well
> > > > may be affecting is that the router in
> question
> > > has
> > > > two subnets configured on the internal port.
> > > There is
> > > > a nat'd subnet for our local users and there
> is
> > > the
> > > > public subnet that these servers sit on.  The
> > > final
> > > > resting place for all three is in a datacenter
> > > that
> > > > isn't built yet, so rather than reconfigure
> > > everything
> > > > once that was done I simply routed the final
> > > subnet to
> > > > our office and set it up their.  The router is
> a
> > > > mikrotik RB112 board which only has one
> ethernet
> > > port
> > > > so I couldn't dedicate a port for the new
> subnet.
> > > As
> > > > I said, my first thought was that the problem
> was
> > > in
> > > > the router, but the other two servers are
> running
> > > > fine.
> > > >
> > > > Any suggestions?
> > > >
> > > > Thank you,
> > > > Craig Russell
> > > >
> _______________________________________________
> > > > freebsd-questions@freebsd.org mailing list
> > > >
> > >
> >
>
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > > To unsubscribe, send any mail to "
> 
=== message truncated ===




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20070514152051.48723.qmail>