/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Steve Kram <[EMAIL PROTECTED]> wrote:
>
> DLink DE-220 ISA combo card as eth0 (external interface)
> Full duplex changed to half duplex (saw it on D. Ranch's forum)
> IRQ10 remained the same
> DLink DE-220 ISA ...as eth1 (internal interface)
> Full duplex changed to half duplex
> IRQ3 changed to IRQ12 (eliminated the possible conflict with COM2 port)
I am almost certain that changing to half duplex is what fixed your
problem. "Full duplex" means that the ethernet card is able to send a
packet at the same time that it is receiving one. However, on most
hub-based ethernets, this is impossible, and the sending packet will
collide with the receiving packet, causing a collision error and
requiring the protocols to re-send.
Only a direct-connect (via "crossed" cable) or a real switched ethernet
can be set to full duplex.
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience.
sometimes known as David DeSimone || Experience comes from bad judgment."
http://www.dallas.net/~fox/ || -- Life Lessons
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
