Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 May 1999 22:31:40 -0600 (MDT)
From:      cwasser@v-wave.com
To:        Brandon Fosdick <bfoz@glue.umd.edu>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Crossover Ethernet
Message-ID:  <Pine.BSF.4.10.9905272217400.5388-100000@area51.v-wave.com>
In-Reply-To: <374E0508.C82BDA02@glue.umd.edu>

next in thread | previous in thread | raw e-mail | index | archive | help


On Thu, 27 May 1999, Brandon Fosdick wrote:

> I've been trying for two days now to get two 3.2-S boxes talking to each other
> with a crossover cable. After searching the archives it sounds like its an easy
> thing to do, for everybody else at least.

Without trying to re-invent the wheel, I am doing what you're doing above,
and here's what I did (if it'll help any, albeit 2nd machine is a
different OS):

"Server" P5-233MMX / 64MB (Soon to be Dual 550 Xeon/256MB)
FreeBSD 3.2-STABLE
XL0: set through DHCP
XL1: ip: 192.168.1.1  net: 192.168.1.0  bcast: 192.168.1.255
     netmask: 255.255.255.0

Route Info:

u: inet 192.168.1.0; u: link ; RTM_GET: Report Metrics: len 136, pid: 0,
seq 1, errno 0, flags:<UP,GATEWAY,STATIC>
locks:  inits: 
sockaddrs: <DST,NETMASK,IFP>
 192.168.1.0 (0) 0 ffff ff 
   route to: 192.168.1.0
destination: 192.168.1.0
       mask: 255.255.255.0
  interface: xl1
      flags: <UP,DONE,CLONING>
 recvpipe  sendpipe  ssthresh  rtt,msec    rttvar  hopcount      mtu
expire
       0         0         0         0         0         0      1500
-30870 

locks:  inits: 
sockaddrs: <DST,GATEWAY,NETMASK,IFP,IFA>
 192.168.1.0  255.255.255.0 xl1:0.60.97.5b.f8.79 area51

/*
   I knew the actual routing command for Linux but I used sysinstall to
   setup the routing, but here's the Linux equiv that I know works: 

   route -add net 192.168.1.0 netmask 255.255.255.0 broadcast
   192.168.1.255 [device])
*/

---

"Client" P5-200 / 64MB
Windows98
NIC0: ip: 192.168.1.2  net: 192.168.1.0  bcast: 192.168.1.255
      netmask: 255.255.255.0  gateway: 192.168.1.1
      (DNS info filled in by hand)

Running natd on the "server" for the clients inet access, local lan
traffic works fine (and ofcourse masqueraded traffic) .. Hope my ramblings
help some.

Chris



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9905272217400.5388-100000>