Date: Thu, 31 Oct 1996 09:33:17 -0100 From: Darius Moos <moos@degnet.baynet.de> To: FreeBSD-questions <questions@freebsd.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org>, danny@panda.hilink.com.au Subject: Re: Is this network possible with FreeBSD ??? Message-ID: <3278806D.2FA6@degnet.baynet.de> References: <326DFE77.549B@degnet.baynet.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi again,
now here comes my summary.
many people answered me that my problem MUST be handeled by FreeBSD
and gave me hints and tips and solutions.
I have tried them all and they did NOT work !!!
To simplify the situation, i've tried to get the network running, that
is pictured below (at the end of this mail).
Now look at all the configurations i've tried:
The ISPA-Router was always configured to send packets with dst-ip
1.2.3.253 through ed1.
The FreeBSD-box had always 1.2.3.36 as the default-router.
1. FreeBSD:
ifconfig ed0 inet 1.2.3.253
The problem:
When sending a packet to www.freebsd.org it returns back as it
should do (no problem), BUT when sending a packet to the
1.2.3.x-net (ie. 1.2.3.10 or 1.2.3.11 or 1.2.3.252 or...)
nothing happens. The packet don't even get on the Telco-wire.
The packet don't get to the ISDN-card.
The reason:
(i do not really know but i'm assuming this to be the reason)
FreeBSD broadcasts for the dst-ip on the ethernet-segment
FreeBSD is part of through ed0. Since there are only two IPs
and two ethernet-adr.es on the wire, the broadcast for the
dst-ip (ie. 1.2.3.10 or 1.2.3.11 or 1.2.3.252 or...) gives no
result. So the packet does not get on its way to the 1.2.3.x-net.
The solution would be:
A configuration-command for FreeBSD to send all packets through
ed0.
2. FreeBSD:
ifconfig ed0 inet 1.2.3.253 netmask 0xffffffff
The problem:
The router (1.2.3.36) was not found when the default-route is
set in /etc/netstart.
The reason:
Network unreachable error
The solution would be:
A configuration-command for FreeBSD to send all packets through
ed0.
3. FreeBSD:
ifconfig ed0 inet 1.2.3.253 broadcast 1.2.3.0
The problem:
The router (1.2.3.36) was not found when the default-route is
set in /etc/netstart.
The reason:
There were no broadcast-packets at all and therefor the Router
was not found and entered as LINK# in the routing-table.
The solution:
I do not know what a solution could look like in this situation.
4. FreeBSD:
ifconfig ed0 inet 1.2.3.253 broadcast 1.2.3.36
The problem:
The Router (1.2.3.36) was found but again all other hosts on
the 1.2.3.x-net were not found
The reason:
FreeBSD was broadcasting for this hosts on the ethernet but there
was not answer, because this hosts are only reachable through
the ISDN-connection and not directly through the ethernet-wire.
The solution would be:
A configuration-command for FreeBSD to send all packets through
ed0.
I have tried this four cases also with the additional parameter "-arp"
but that did not help either and the effects were the same.
Then i've tried to make 1.2.3.253 an alias on ed0. The Router was
configured to send all packets with dst-ip 192.168.4.1 through ed1.
5. FreeBSD:
ifconfig ed0 inet 192.168.4.1
ifconfig ed0 inet 1.2.3.253 netmask 0xffffff00 alias
The problem:
When sending a packet to www.freebsd.org it returns back as it
should do (no problem), BUT when sending a packet to the
1.2.3.x-net (ie. 1.2.3.10 or 1.2.3.11 or 1.2.3.252 or...)
nothing happens. The packet don't even get on the Telco-wire.
The packet don't get to the ISDN-card.
The reason:
(i do not really know but i'm assuming this to be the reason)
FreeBSD broadcasts for the dst-ip on the ethernet-segment
FreeBSD is part of through ed0. Since there are only two IPs
and two ethernet-adr.es on the wire, the broadcast for the
dst-ip (ie. 1.2.3.10 or 1.2.3.11 or 1.2.3.252 or...) gives no
result. So the packet does not get on its way to the 1.2.3.x-net.
The solution would be:
A configuration-command for FreeBSD to send all packets through
ed0.
The same is true for case 2,3,4 with the additional ifconfig-alias
command and the symptoms are the same as described in this cases.
Further i have tried an netmask of 0xffffffff for the alias command
(i know this is not intended for that situation but i've tried anyway)
It did not work either.
So summarizing all my experiences i've collected with this configuration
i have to come to the conclusion, that the specified network is NOT
possible with FreeBSD. But what's really disappointing is the fact,
that Linux-1.(something) can handle this network :( , maybe because it
is breaking some standards.
So my final question is:
To whom in the developers-group should i send this report ?
Is this report of any use ?
Darius Moos.
Here the promised picture:
+---------------+
| FreeBSD-2.1.0 |
|+-------------+|
|| NE 2000 ||
|| 1.2.3.253 ||
|| ed1 ||
++------o------++
|
|
++-------o-------++
|| NE 2000 ||
|| 1.2.3.36 ||
|| ed1 ||
|+---------------+|
| |
| ISPA +-------+ Telco-wire
| Router | ISDN o------------o ISP 1.2.3.x
| +-------+ net
| |
++---------------++
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3278806D.2FA6>