public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus <profmakx@profmakx.de>
To: Dennis <dennis@etinc.com>
Cc: umbertogs@uol.com.br, linux-kernel@vger.kernel.org
Subject: Re: trouble with eepro100+catalyst
Date: Sun, 05 Nov 2000 18:42:14 +0100	[thread overview]
Message-ID: <3A059BF6.8E99F434@profmakx.de> (raw)
In-Reply-To: <5.0.0.25.0.20001021123524.02372be0@mail.etinc.com>

Dennis, Your comment isn´t that productive
What about ECN? Have acitivated it (proc/sys/net/ipv4/tcp_ecn, if I remember
correctly)

Markus

Dennis wrote:

> At 11:06 PM 10/20/2000, umbertogs@uol.com.br wrote:
> >We're having lots of trouble with eepro100 and Cisco Catalyst switch,
> >and my net are a vlan. I am using RedHat 6.2/7.0 and not ping to gateway,
> >but with o Slackware 7.0 ok. What's the magic?
> >
> >Regards,
> >
> >Umberto
> >Systems Analyst
> >.comDominio
> >Brazil
>
> Ciscos and catalysts have all kinds of problems connecting to PCs. They
> like to talk to each other mostly. Unfortunately, the widespread propaganda
> that cisco is flawless hinders the true diagnosis in many cases.
>
> get yourself a cheap 10/100 hub or switch and wire it between the units and
> then go watch some sports instead of banging your head for nothing
>
> Sometimes its better to sacrifice performance (ie catalysts) for  something
> that works.
>
> Dennis
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

           reply	other threads:[~2000-11-05 17:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5.0.0.25.0.20001021123524.02372be0@mail.etinc.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A059BF6.8E99F434@profmakx.de \
    --to=profmakx@profmakx.de \
    --cc=dennis@etinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=profmakx@web.de \
    --cc=umbertogs@uol.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox