Board index Linux Networking

crossover cable networking problem

crossover cable networking problem

Post by Rajeev Sudr » Fri, 02 Nov 2001 07:09:14



Dear all,
Sorry for cross posting. I have had a networking problem for some time:
Laptop A, winME/Redhat7.1 with an intel pcmcia network card (192.168.0.1)
Laptop B, win98/peanut8.4 linux in a compaq docking station with the
netflex3 NIC on the docker.

I have them cabled together using a crossover cable to not have to use a
hub. With the hub and relevent cabling, all configs of OS's work fine with
ping tests. Without, all configurations except for the following work fine:

Laptop A (WinME) --- Laptop B (peanut linux).

The problem is with the netflex3 NIC. peanut kernel version is 2.4.3 and
uses the tlan driver. Is a kernel upgrade the best way of resolving this?
could it be a switch/parameter that needs to be passed to the driver? The
boot messages state that the card is trying to autonegotiate a connection
and suggests to check the hub/cabling.

Kinda confused. Would love any suggestions!
TIA, Raj

 
 
 
Top

crossover cable networking problem

Post by Eric » Sat, 03 Nov 2001 04:27:54


I would set the NIC to the speed and duplex you need.  There can be problems
with autonegotiation.  The driver (from the kernel source) should tell you
where to find info on how to set the speed and duplex.  Once you have this,
the next step is passing the settings to the running driver.  There are two
different ways, one if you have a static kernel (you have to modify you
lilo.conf), and another if you are using modules for this driver (the
settings go in the modules.conf).


Quote:> Dear all,
> Sorry for cross posting. I have had a networking problem for some time:
> Laptop A, winME/Redhat7.1 with an intel pcmcia network card (192.168.0.1)
> Laptop B, win98/peanut8.4 linux in a compaq docking station with the
> netflex3 NIC on the docker.

> I have them cabled together using a crossover cable to not have to use a
> hub. With the hub and relevent cabling, all configs of OS's work fine with
> ping tests. Without, all configurations except for the following work
fine:

> Laptop A (WinME) --- Laptop B (peanut linux).

> The problem is with the netflex3 NIC. peanut kernel version is 2.4.3 and
> uses the tlan driver. Is a kernel upgrade the best way of resolving this?
> could it be a switch/parameter that needs to be passed to the driver? The
> boot messages state that the card is trying to autonegotiate a connection
> and suggests to check the hub/cabling.

> Kinda confused. Would love any suggestions!
> TIA, Raj


 
 
 
Top

crossover cable networking problem

Post by Masud Re » Sat, 03 Nov 2001 09:22:49



> Dear all,
> ping tests. Without, all configurations except for the following work fine:

> Laptop A (WinME) --- Laptop B (peanut linux).
> could it be a switch/parameter that needs to be passed to the driver? The
> boot messages state that the card is trying to autonegotiate a connection
> and suggests to check the hub/cabling.

A hub is a repeater. In your case, you have eliminated that since you
are using a cross cable and talking directly.

Try disabling the autonegotiate on both sides or enable it on both
sides.

Hope it works!

Masud

 
 
 
Top

1. Problem networking 3c905's via crossover cable

I'm trying to network two computers (Greyeyes and Henry)
using redhat-5.1 (kernel 2.0.35-pre from the stock install
and 2.0.35-final from the updates.).  I'm using a crossover
cable and no hub.  The cards are 3c905Bs.

I've got the cards installed and the 3c59x driver loads automatically
and seems to recognize them without any IRQ conflicts.  I think I've
got the network addresses and so on and so forth all set up. (And I've
tried working things by hand just to make sure the network scripts
aren't fouled up somehwere.)  But I still have a problem.

Running tcpdump in a window on both machines, I start pinging from
Greyeyes => Henry.   Absolutely no response.

Ping from Henry => Greyeyes.  Greyeyes receives arp requests from Henry
which it thinks it answers.  Henry, however, never receives the answer.

Ping from Henry to the broadcast address (192.168.0.255) -- Henry answers the
call.  Greyeyes thinks it's responding, but Henry never sees it.

Can anyone help me?  Even helping to figure out if I have a problem with
Greyeyes sending packets or Henry's ability to receive might help.

Here's output from ifconfig and route on Greyeyes.  Henry gives similar
results; HWaddr is different of course, inet addr:192.168.0.1,
RX packets:0 errors:0 dropped:0 overruns:0      [always]
Interrupt:10 Base address:0xd400


eth0      Link encap:Ethernet  HWaddr 00:10:4B:79:24:05
          inet addr:192.168.0.7  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:49 errors:0 dropped:0 overruns:0
          TX packets:75 errors:0 dropped:0 overruns:0
          Interrupt:12 Base address:0x3000


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
207.49.29.102   0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        2 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        1 lo
0.0.0.0         207.49.29.102   0.0.0.0         UG    0      0        6 ppp0

Thanks for any help,
Toshio
--

.ucsc.edu     \\=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

2. Dell PowerEdge 2850 & Solaris 10 (1/06) Install

3. linux <-> 2k crossover cable network

4. how to continue a process after logout ?

5. Linux/Win2k network with crossover cable

6. top for Solaris

7. question about networking with a crossover cable and a router

8. How to writer a video card driver

9. Two Netgear FA311 NICs, one crossover cable, and no networking!

10. How to run rcp over crossover cable on crude network config

11. Looking for HOWTO for Win95/Linux network with crossover cable

12. Linux Networking via Crossover cable

13. Crossover cable for pc to pc network?


All times are UTC
Board index