Date: Tue, 29 Oct 1996 21:13:43 -0100 From: Darius Moos <moos@degnet.baynet.de> To: moos@degnet.baynet.de Cc: freebsd-hackers <freebsd-hackers@FreeBSD.org>, FreeBSD-questions <questions@FreeBSD.org> Subject: Re: Is this network possible with FreeBSD ??? Message-ID: <32768197.775E@degnet.baynet.de> References: <326DFE77.549B@degnet.baynet.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Rehi,
to all who remember my original mail concerning the bogus network.
First of all ... i have faild to get it running in it's all
functionality.
Now, more IMPORTANT, i want to thank all the persons that replied to
my mail.
Thanks for their time and effort, help and suggestions go to:
- Daniel O'Callaghan
- Gary Palmer
- Joe Greco
- Mathias Pantzare
- Michael Smith
- Narvi
- Olivier Robert
- Pedro Giffuni
- Richard Wackerbarth
- Thinker Li
Thank you all.
Now why did i fail to manage the bogus network:
I could not figure out how to configure the ed0_a device appropriately
for the given situation.
I've tried it the following ways:
1. FreeBSD: ifconfig ed0_a inet 1.2.3.253
The ISPA-router was configured to push all packets for 1.2.3.253
in direction ed0_b with ed0_b == 1.2.3.36
The problem:
The FreeBSD-box did not find the other boxes in the 1.2.3.-net
because for packets to 1.2.3.x it was broadcasting on the
ed0_a-ethernet-device and there was not response (i think this
is what happend but i could be wrong).
The solutions would have been:
packet from |___ ed0_a |____ ed0_b |____ isdn |____ 1.2.3.x-box
FreeBSD-box | | | |
to 1.2.3.x |
2. FreeBSD: ifconfig ed0_a inet 192.168.3.1
ifconfig ed0_b inet 1.2.3.253 netmask 0xffffffff alias
ISPA-router: ed0_b was configured to 192.168.3.103 and further
to push all packets for 1.2.3.253 to the FreeBSD-box
via ed0_b.
The problem:
Packets, adressed to internet had an IP-src-adr. of 192.168.3.1 and
and did not return to the FreeBSD-box.
I do not know what a solution could look like.
3. FreeBSD: ifconfig ed0_a inet 192.168.3.1
ifconfig ed0_b inet 1.2.3.253 netmask 0xffffffff alias
ISPA-router: ed0_b was configured to 192.168.3.103 and
ed0_b was configured to 1.2.3.36 and further
to push all packets for 1.2.3.253 to the FreeBSD-box
via ed0_b.
The problem:
Packets, adressed to internet had an IP-src-adr. of 192.168.3.1 and
and did not return to the FreeBSD-box.
I do not know what a solution could look like.
Now the boss of the company decided to crash FreeBSD and to reinstall
Linux, because linux could handle this bogus network as a gateway :(
I am a little bit disappointed that i've failed to solve this problem
and that linux will now be installed instead of FreeBSD, but ...
... SHIT happens sometimes.
Hope there will be a new customer next days, that wants a gateway and
does not have such a bogus network-topology.
Darius Moos.
Here my original mail for those that does not remember any more
Darius Moos wrote:
>
> Hi,
>
> i have an urgent problem with the network-setup of FreeBSD.
> I've set up FreeBSD-2.1.0 for a company (I never set up an other OS
> for any company). I was gave permission, to trash their linux and
> install FreeBSD-2.1.0 instead. The installation went fine but now
> i am running into a problem with their network-configuration.
> Their ISP (a real linux-fetishist) says "FreeBSD is TOO BRAINDAMAGED
> to handle this problem". I do not think so. The network-configuration
> is pictured below. Also more details are written below.
> Now my problem (maybe I AM braindamaged):
> 1. How to ifconfig the ether-device of the FreeBSD-box ?
> 2. How to set up the routing of the FreeBSD-box ?
> so that the FreeBSD-box acts as a mail- and WWW-proxy gateway for the
> company's private network.
>
> +---------------+
> | FreeBSD-2.1.0 |
> |+-------------+|
> || NE 2000 ||
> || 192.168.3.1 ||
> || 1.2.3.253 ||
> ++------o------++.... ed0_a
> |
> |
> ++-------o-------++.... ed0_b
> || NE 2000 ||
> || 192.168.3.103 ||
> || 1.2.3.36 ||
> |+---------------+|
> | |
> | +-------+
> | Router | ISDN o------------o ISP 1.2.3.x
> | +-------+
> | |
> |+---------------+|
> || 100 MBit ||
> || 192.168.3.104 ||
> ++-------o-------++
> |
> |
> ++-------o-----++
> || 100 MBit ||
> || 192.168.3.2 ||
> |+-------------+|
> | |
> | 192.168.3.x |
>
> The linux that i have trashed had no problems with this configuration
> BUT i do not know how to ifconfig the network device of the FreeBSD-
> machine and how to setup the correct routing. The FreeBSD-machine
> should be known with a registered IP in the internet. I've replaced the
> real registered IP with 1.2.3.253. All the other machines (except the
> router) in the company should run only on the private network
> 192.168.3.0. The FreeBSD-machine should be the email and WWW-proxy
> gateway for the private company network.
> The problem so far:
> - When i ifconfig the network-card of the FreeBSD-machine with
> "ifconfig ed0 inet 1.2.3.253 netmask 0xffffffff", the
> 1.2.3.36-IP is not reachable and therefor unknown to the routing.
> - I can not use a netmask of 0xffffff00 for the ether-device of the
> FreeBSD-box.
> - When i ifconfig the ether-device of the FreeBSD-box with
> "ifconfig ed0 inet 192.168.3.1 netmask 0xffffff00" and
> "ifconfig ed0 inet 1.2.3.253 netmask 0xffffffff alias"
> the outgoing packets never come back, since the FreeBSD-box sends
> its packets with src of 192.168.3.1
> What i would need is a
> ifconfig ed0 inet 1.2.3.253 netmask 0xffffffff
> ifconfig ed0 inet 192.168.3.1 netmask 0xffffffff alias
> route add -net 1.2.3 ed0
> but ether-devices as destination in the route-statement are not allowed.
> Under the linux this was possible (the ISP says).
> Now this situation is braindamaged itself, but this does not count as
> argument to the boss of this company. The boss had a running system
> with this network-configuration and he stands on the point that this
> has to be possible or the OS (FreeBSD) is not the right OS so far.
> Please please help me with this network-setup, so i can prove, that
> FreeBSD IS the right OS for all networking.
> BTW: this mail is closely related to my other mail about FreeBSD-support
> for HP-10/100-VG or Compex 100VG network-cards.
>
> Many thanks for all your help in advance.
>
> Darius Moos.
>
> --
>
> email: moos@degnet.baynet.de
--
email: moos@degnet.baynet.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32768197.775E>