Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Feb 1997 16:32:12 -0500 (EST)
From:      John Brann <jbrann@brann.org>
To:        brandon@cold.org (Brandon Gillespie)
Cc:        freebsd-questions@freebsd.org
Subject:   Re: setting up two ethernet devices--seperate networks
Message-ID:  <199702282132.QAA17469@freebie.brann.org>
In-Reply-To: <Pine.NEB.3.95.970228131353.8207A-100000@cold.org> from Brandon Gillespie at "Feb 28, 97 01:21:50 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Brandon Gillespie wrote...
> Hrm, well:
> 
> # netstat -rn
> Routing tables
> 
> Internet:
> Destination        Gateway            Flags     Refs     Use     Netif Expire
> default            206.81.134.1       UGSc        0        0       ed0
> 127.0.0.1          127.0.0.1          UH          0        0       lo0
> 192.168.1          link#2             UC          0        0 
> 206.81.134         link#1             UC          0        0 
> 206.81.134.1       link#1             UHLW        1        0 
> 206.81.134.2       0:c0:f0:a:25:de    UHLW        0       10       ed0 1181
> 206.81.134.54      0:40:95:a6:10:46   UHLW        1       61       ed0 1181
> 
> dmesg on the cards:
> 
> ed0 at 0x340-0x35f irq 5 on isa
> ed0: address 00:80:c8:3e:de:38, type NE2000 (16 bit) 
> ed1 at 0x300-0x31f irq 10 maddr 0xd8000 msize 16384 on isa
> ed1: address 00:00:c0:fa:87:2b, type WD8013EP (16 bit) 
> 
> And ifconfig is ran as/with the following results:
> 
> ifconfig ed0 inet 206.81.134.97 netmask 255.255.255.0
> ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 206.81.134.97 netmask 0xffffff00 broadcast 206.81.134.255
>         ether 00:80:c8:3e:de:38 
> 
> ifconfig ed1 inet 192.168.1.1 netmask 255.255.255.0
> ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
>         ether 00:00:c0:fa:87:2b 
> 
> Now, I can get networking to work through the 206.81.134.0 network
> (doesn't matter the interface--I've switched it to either ed0 or ed1 and
> both work).  I tried adding a static rout for ed1 like:
> 
> route add -net 192.168.1.0 -interface ed1
> 
> But this didn't work, and reported the error:
> 
> writing to routing socket: File exists
> add net 192.168.1.0: gateway ed1: File exists
> 
> *sigh*
> 
> -Brandon Gillespie
> 


OK, the ifconfigs and dmesg stuff look fine to me, too.  The only thing
I can see which is different in my routing table:

Internet:
Destination        Gateway            Flags     Refs     Use     Netif Expire
default            207.122.63.1       UGSc        9      172       ed0
10/24              link#2             UC          0        0 
10.0.0.2           0:40:5:33:dc:51    UHLW        0        6       lo0
10.0.0.255         ff:ff:ff:ff:ff:ff  UHLWb       1     8297       ed1
127.0.0.1          127.0.0.1          UH          2    20363       lo0
207.122.63         link#1             UC          0        0 
207.122.63.1       0:0:c:8e:ce:b5     UHLW       10        0       ed0   1175
207.122.63.57      0:0:c0:96:ce:b6    UHLW        0       42       lo0

is that I have explicit routes to the two IP addresses of my ethernet cards
(207.122.63.57 and 10.0.0.2) and that rather strange line for 10.0.0.255
(I have a class 'C' netmask on the 10. network - hence that is the
broadcast address.)  None of these were created explicitly, I suspect
Samba of doing something on that network to creat the strange broadcast line.

This may be an obvious question, but can the multi-homed FreeBSD box
ping both its own addresses?  If so - what does the routing table look like
afterwards?

John
-- 
Prohibit work, prohibit pay - people are dying!  
			Situationist International slogan

finger jbrann@brann.org for pgp public key



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702282132.QAA17469>