Date: Tue, 14 Mar 1995 04:47:21 -0500 (EST) From: Denis Fortin <fortin@zap.zap.qc.ca> To: jg@euronet.nl (Jan_Guldemond) Cc: questions@FreeBSD.org Subject: Re: Routing and Ethernet Message-ID: <199503140947.EAA02990@zap.zap.qc.ca> In-Reply-To: <199503140844.JAA03075@mail.euronet.nl> from "Jan_Guldemond" at Mar 14, 95 03:44:41 am
next in thread | previous in thread | raw e-mail | index | archive | help
> ed0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 193.78.175.2 netmask 0xffffff00 broadcast 193.78.175.255
> ether 00:00:1b:4f:b9:38
> ed1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> inet 193.78.175.3 netmask 0xffffff00 broadcast 193.78.175.255
> ether 00:00:1b:4f:bd:fc
> [...]
> There is no route to all the working stations (193.78.175.0), so I try to
> add this route ("route add 193.78.175.0 193.78.175.3").
What you're doing is telling FreeBSD:
* I have an interface called 193.78.175.2, and through it you can talk
to 193.78.175.* (via the netmask 0xffffff00).
* I also have an interface called 193.78.175.3, and through it you can talk
to 193.78.175.* (via the netmask 0xffffff00).
Hence the "File already exists" message.
You cannot have two physically different wires that have the same network
(193.78.175.*) on them. This is a TCP/IP issue, not a FreeBSD problem.
You should either subnet your network into two portions via the netmasks
(e.g. the first wire gets 193.78.175.x for x >= 128, and the second one
gets 193.78.175.x for x <= 127), or get a second network.
--
Denis Fortin fortin@acm.org
DMR Group Inc, (514) 877-3301 These opinions are my own
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503140947.EAA02990>