From owner-freebsd-questions Wed Oct 23 02:23:08 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08047 for questions-outgoing; Wed, 23 Oct 1996 02:23:08 -0700 (PDT) Received: from cyclone.degnet.baynet.de (cyclone.degnet.baynet.de [194.95.214.129]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA08027; Wed, 23 Oct 1996 02:22:53 -0700 (PDT) Received: from neuron (ppp6 [194.95.214.136]) by cyclone.degnet.baynet.de (8.6.12/8.6.9) with SMTP id LAA02486; Wed, 23 Oct 1996 11:22:00 +0100 Message-ID: <326DFE77.549B@degnet.baynet.de> Date: Wed, 23 Oct 1996 10:16:07 +0000 From: Darius Moos Reply-To: moos@degnet.baynet.de X-Mailer: Mozilla 3.0Gold (Win95; I) MIME-Version: 1.0 To: freebsd-hackers CC: FreeBSD-questions Subject: Is this network possible with FreeBSD ??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk 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------++ | | ++-------o-------++ || 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