From: "Vishal Gandhi Kommineni" <vishal@southernonline.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] speed problem
Date: Fri, 03 Jan 2003 05:46:59 +0000 [thread overview]
Message-ID: <marc-lartc-104157222823242@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104149697120410@msgid-missing>
I dont see any collisions when make ifconfig, i feel the problem is in
forwarding the packets by the linux box inbetween the interfaces, it is here
that there is lot of packet loss,
Do you think it to be so
Thanks & Regards,
Vishal Gandhi
----- Original Message -----
From: "Lars Gaarden" <larsg@eurorights.org>
To: "LARTC" <lartc@mailman.ds9a.nl>
Sent: Thursday, January 02, 2003 4:52 PM
Subject: Re: [LARTC] speed problem
> Vishal Gandhi Kommineni wrote:
> > Warm wishes for the new year 2003,
> > thanks for the reply, i found that there are collission when i use a hub
in
> > between,
> > How do i make sure that both the ethernet cards are running in half or
full
> > duplex mode,
> > how do i check if weathere an ethernet is in half or full duplex mod
>
>
> Could you provide the output from 'ifconfig' and 'route -n' on A, B and
> C? This is either a reverse DNS, duplex mismatch or routing problem.
>
> To see if your are full or half duplex, see if ifconfig reports any
> collisions on the eth interface - on full duplex you never get any
> collisions.
>
> If it takes a long time from you try to connect until it starts
> downloading, you have a DNS problem.
>
> If the download is incredibly slow and one or more of the network
> interfaces on A, B or C report a huge amount of collisions, you
> have a duplex problem.
>
> Routing problems usually result in not being able to connect at
> all, which doesn't seem to be the case here.
>
> --
> The content of this message can either be used according to normal
> copyright law (including quoting and personal copies) or by the terms of
> the GNU Free Documentation License http://www.gnu.org/licenses/fdl.html
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-03 5:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 8:53 [LARTC] speed problem Vishal Gandhi Kommineni
2003-01-02 9:04 ` ulrich schwarz
2003-01-02 9:37 ` Vishal Gandhi Kommineni
2003-01-02 11:22 ` Lars Gaarden
2003-01-02 16:19 ` Martin A. Brown
2003-01-03 5:43 ` Vishal Gandhi Kommineni
2003-01-03 5:46 ` Vishal Gandhi Kommineni [this message]
2003-01-03 5:49 ` Vishal Gandhi Kommineni
2003-01-03 17:58 ` Dan Kramarsky
2003-01-04 5:26 ` Vishal Gandhi Kommineni
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=marc-lartc-104157222823242@msgid-missing \
--to=vishal@southernonline.net \
--cc=lartc@vger.kernel.org \
/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