Date: Tue, 10 Sep 1996 14:04:01 -0400 (EDT) From: Charlie ROOT <root@cgdlf.caf.wvu.edu> To: support@cdrom.com Subject: FreeBSD routing problems Message-ID: <Pine.BSF.3.91.960910134459.173A-100000@cgdlf.caf.wvu.edu> Resent-Message-ID: <Pine.BSF.3.95.960910145431.5368N@mother.cdrom.com>
next in thread | raw e-mail | index | archive | help
Hi,
My name is Daniel Frasnelli. I'm an employee of the College of
Agriculture and Forestry at West Virginia University. Currently, I am
trying to set up an ethernet bridge using a 486/33 w/16mb ram running
FreeBSD 2.1.5. The network hardware is: 3 3Com503 cards and a CentreCOM
MR820T eight port hub. We (the net admin and myself) are attempting to
bridge a Win '95 machine through the FreeBSD box to the local network.
While installing FreeBSD, I indicated that this machine will route
packets between interfaces, and enabled routed in the /etc/sysconfig file.
Both myself and the net admin were under the impression that the bridging
would be done transparently, but we have not yet been able to use the win
95 machine while it's connected to the hub. We would like to use
bridging, and not routing, because the local network also passes
Microsoft Network traffic. I've created output files for ifconfig -a,
netstat -r, and ipfw l a as they appear after booting. Myself and
several other people have tried different configurations, none of
which worked, but the output is how they appear automatically. Before I
read those files into this message, I'll explain what the hosts are, and their
ip addresses.
- telcom (157.182.4.1) is the gateway for this building
- cgdlf (157.182.4.45) is the address of the first ethernet card (bsd)
- cgdlg (157.182.4.46) is the address of the second card
- caf1 (157.182.4.65) is the DNS we're using
- as1010 (157.182.6.208) is the Win 95 machine
The physical wiring is as follows:
ed0 (157.182.4.45) is connected to the wall jack (local net)
ed1 (157.182.4.46) is connected to the AUI port of the hub
as1010 (.6.208) is connected to port #1 of the hub
routed is enabled and has the -q flag.
Here is the output of ifconfig -a:
ed0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 157.182.4.45 netmask 0xfffffc00 broadcast 157.182.7.255
ether 02:60:8c:8c:9f:0e
ed1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 157.182.4.46 netmask 0xfffffc00 broadcast 157.182.7.255
ether 02:60:8c:a7:26:76
ed2: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500
ether 02:60:8c:6c:2b:b8
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
netstat -r:
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default telcom UGSc 0 0 ed0
localhost localhost UH 0 0 lo0
157.182.4/22 link#1 UC 0 0
telcom link#1 UHLW 1 0
caf1 8:0:20:1d:f5:f0 UHLW 0 8 ed0 1166
and ipfw l a (for evaluation, we have no restrictive rules):
FireWall chain entries: 300 0
01000 allow all from 127.0.0.1 to 127.0.0.1
65000 allow all from any to any
65535 deny all from any to any
Any and all help/suggestions/fixes you can offer would be greatly
appreciated. The net admin is a Solaris person himself, so he's getting
a great kick out of my misconfiguration <g>.
Thanks again, and thanks for a great product,
Daniel Frasnelli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960910134459.173A-100000>