Hi!
I'm trying to make a WAN card (Tau-PCI) to work
via netgraph. I have:
[cp0] <-> [ppp0] <-> [ng0]
cp0 is node written by Cronyx (www.cronyx.ru) for their WAN
adapters. ppp0 is ng_ppp and ng0 is ng_iface.
Starting sequence is like this:
ngctl <<
mkpeer iface dummy ipx
msg n
> Improperly negotiating 100-BT/FD and generating lots of late collisions,
> for one. Is the switch managed? What does it's syslog output or the
> local CLI say about the port(s) in question? In Cisco parlance, you may
> want to clear the interface counters and observe 'sh int...' output while
>
Hello:
Judging from your output I would say two things:
1) You have a bad cable. CRC and framing errors are usually a result of bad
media.
2) You should set the port to auto/auto, not 100/Full hard set, unless you
have specifically set that up in rc.conf. If one side is hard set and the
other i
> Hello:
>
> Judging from your output I would say two things:
>
> 1) You have a bad cable. CRC and framing errors are usually a result of
bad
> media.
> 2) You should set the port to auto/auto, not 100/Full hard set, unless you
> have specifically set that up in rc.conf. If one side is hard set a
On 6/27/03 12:29 PM, "Shawn Ramsey" <[EMAIL PROTECTED]> wrote:
>> Hello:
>>
>> Judging from your output I would say two things:
>>
>> 1) You have a bad cable. CRC and framing errors are usually a result of
> bad
>> media.
>> 2) You should set the port to auto/auto, not 100/Full hard set, unless
> > Ok.. It is set hard to 100BT/FD on both ends. I don't know if you saw
this,
> > but since resetting the stats a few hours ago, it shows no errors at all
on
> > their end, but were still getting errors on our end... The CRC and frame
> > errors could have been from a media mismatch when things w
On Fri, 27 Jun 2003, Ying-Chieh Liao wrote:
> On Fri, Jun 27, 2003 at 09:28:31 -0400, Robert Watson wrote:
> > You might compare the dmesg output from before/after and see if there are
> > any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps
> > the changes in interrupt routing
On Thu, Jun 26, 2003 at 23:40:24 -0700, Kris Kennaway wrote:
> Check that it's negotiating the media type and options correctly. On
> the gohan machines it has been failing to negotiate full-duplex mode
> for the past few months, leading to LAN transfer speeds on the order
> of 20kps unless I set
On Fri, Jun 27, 2003 at 13:27:28 +0800, Ying-Chieh Liao wrote:
> my previous kernel is about May 10, and the fxp works fine for me
> but I cvsuped and make world/kernel yesterday (6/26), and then terrible thing
> happens... the connection becomes v...e...r...y... s...l...o...w...
> my ping time to
You might compare the dmesg output from before/after and see if there are
any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps
the changes in interrupt routing have resulted in some new behavior.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECT
On Fri, Jun 27, 2003 at 09:28:31 -0400, Robert Watson wrote:
> You might compare the dmesg output from before/after and see if there are
> any obvious changes in IRQ allocation, shared interrupts, etc. Perhaps
> the changes in interrupt routing have resulted in some new behavior.
I lost my old ke
11 matches
Mail list logo
