howto: crossover connection between two linux machines?

anGeR · 10-30-2003, 03:06 AM

Yo ppl!
I've got two linux RH9 machines and I want to make crossover connection between them.
So I want to know what should I do?
I've got two nic's and crossover cable and they are connected. So what services do I need and how to make connection so they can see each other?

I hope that you will help me

thx ppl!

Cyclo · 10-30-2003, 04:17 AM

Plug in the hardware, plug in the cables, then (assuming they each only have one network card)

Load the appropriate kernel moduels for the NICs (cant help you there, :google: is your friend)

On first machine:

ifconfig eth0 10.0.0.1

On second machine

ifconfig eth0 10.0.0.2

You can also use 192.168.0.1 and 192.168.0.2 if you feel like it. Then (unless you have strange firewall settings) it should work

/bin/bash · 10-30-2003, 05:22 AM

In /etc/modules.conf file you should have a line like this on each machine:
alias eth0 <nic_module>

anGeR · 10-30-2003, 10:00 AM

the problem was in crossover cable - it didn't work!
Now everything is ok but there is one problem :
In one machine I've got isdn and lan card and in the other only lan card. Network between them works. But when both (isdn and lan) cards are activated on the first machine I can't connect to internet, while the network between two comps works.
But when I deactivate lan card, connection to internet is back again.
Any ideas how to solve this problem ?

thx on previous answers

GJB · 10-31-2003, 06:15 PM

Seems as though you got a route problem. look at route -n before and after you put up your isdn link ... my best guess is that after you put up the isdn link the default route is pointing to your other machine or something while it shoutd be pointing at ppp0 wich should be your isdn connection.

GJB

anGeR · 11-01-2003, 08:08 AM

thx ppl!
I will try those options you gave me and if problem still remains I'll post again

fhleung · 09-13-2008, 07:59 AM

It is another newBie question.

What about the crossover connection between a linux and a Window machine?

I connect 2 machines with crossover cable.
Pin 1 to Pin 3
Pin 2 to Pin 6

On window side, the network card icon at bottom right side is ok.

Both machines with static private IP but ping not working, anyone know how to config?

Please help

billymayday · 09-13-2008, 08:08 AM

Brought up a 5 year old thread? Newbie isn't the reason!

fhleung · 09-28-2008, 04:40 AM

Quote:

Comp A IP= 192.168.1.1
Comp A GW= 192.168.1.100

Comp B IP= 192.168.1.100
Comp B GW= 192.168.1.1

Need to enter DNS ip for window machine side.

fakie_flip · 06-27-2009, 07:51 PM

Yes, He brought up a 5 year old thread and ,so am I too. This is why. I found this page through a Google search because I was having a problem connecting two computers together through a network connection with a crossover cable. The point IS that people find these pages through LQ and Google searches looking for answers!

I've done it before. Right now I am doing it between an XP machine and and a Ubuntu machine, both 64-bit. Not only have I got it working that the computers communicate fast through gigabit lan cards on each end, but I am also sharing the internet from the XP machine to the Ubuntu machine using multiple network connections and currently connected to the net with Internet Tethering through a Blackberry Curve which I dialed into as a modem. Okay, let me get to the point. Here was what I forgot to make it work. If you do all the steps but miss one like I did, then it won't work. The trick is doing this.

If on an Ubuntu machine or one with sudo setup similar:

PHP Code:



echo "1" | sudo tee /proc/sys/net/ipv4

OR:

PHP Code:



sudo bash -c "echo "1" > /proc/sys/net/ipv4

If on the majority of linux distros:

PHP Code:



su -
echo "1" > /proc/sys/net/ipv4

angelo.c · 07-07-2013, 04:43 AM

Hi fakie_flip!

I came across same issue when setting up 2 computers with crossover cable and it doesn't work as well.

I tried your command echo "1" > /proc/sys/net/ipv4 but it says "/proc/sys/net/ipv4 is a directory.

jefro · 07-08-2013, 10:35 AM

"the return of the thread"

A nic generally has a way to auto correct for cable type. Crossover or patch is OK as long as one nic can autocorrect.

Problems happen sometimes when nic is powered up with no connection and won't adjust correctly to patch or crossover.

You'd be surprised how many cables are not correct or of a good quality. Use good quality cable and be sure it is current for cards. Cat6 if gig.

Sometimes the auto speed gets out of whack too.

Use network tools to help decide, even looking at lights on nic may help.

schneidz · 07-08-2013, 10:41 AM

this is what i did:
http://www.linuxquestions.org/questi...6/#post3804866

RootMason · 07-08-2013, 02:15 PM

Gotta laugh at a decade-old question! Kudos to Linux-Questions for being around so long.

I agree with Jefro, most current NICs have the capability to auto-negotiate. Crossover cables should not be necessary.

"... modern implementations of the Ethernet over twisted pair standards usually no longer require the use of crossover cables."

I can agree with Jefro's ideas of snags you might run into, such as problems with autonegotiation, and add one of my own: sticky MACs.

angelo.c · 07-08-2013, 10:42 PM

RootMason,thanks for your reply.

It turns out I mixed up 2 cables with different ethernet cards.

Sorry about that.