From owner-freebsd-isp Fri Jun 15 2:39:20 2001 Delivered-To: freebsd-isp@freebsd.org Received: from exchange.is.innn.is (exchange.innn.is [213.176.158.3]) by hub.freebsd.org (Postfix) with ESMTP id 9292137B401 for ; Fri, 15 Jun 2001 02:39:10 -0700 (PDT) (envelope-from bjorn@innn.is) Received: by exchange.is.innn.is with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Jun 2001 09:42:10 -0000 Message-ID: <6973E4999161D411A57600010233D19728A86D@exchange.is.innn.is> From: =?iso-8859-1?Q?Bj=F6rn_Patrick_Swift?= To: 'Enriko Groen' , "'freebsd-isp@freebsd.org'" Subject: RE: Multipath Date: Fri, 15 Jun 2001 09:42:09 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, If I'm not mistaken what could do is either doing host routing though = the firewall or net routing. I'd recommend net routing in this case. Example; One way to do this is running your local net on 192.168.0.0 = mask 255.255.0.0. Then you have your * local users running on 192.168.1.1-254 mask 255.255.0.0, * mail servers and web cams on 192.168.2.1-254 mask 255.255.0.0, * watchdog on 192.168.3.1-254 mask 255.255.0.0 and your firewall as 192.168.4.1 mask 255.255.0.0 being the default = gateway. Then the routing table would work like this (once you configure it..) 192.168.2.0/24 -> ADSL 192.168.3.0/24 -> fiber the rest -> cable You could of cource divide your lan into smaller subnets but this is probably the easiest way. Given that there are no typos this should do the trick .. if it = doesn't, please correct me :) Cheers, Bjorn -----Original Message----- From: Enriko Groen [mailto:enriko.groen@netivity.nl] Sent: 15. j=FAn=ED 2001 09:26 To: 'freebsd-isp@freebsd.org' Subject: Multipath Hi, I posted a similar question some time ago, but I'm still confused. At this moment I have a FreeBSD firewall which has 4 network interfaces = for different services: Internal network, Fiber connection (256 kbit line), cable connection, = ADSL connection I would like to use every connection for specific trafic Fiber for watchdog queries to our webserver Cable for general surfing for local users ADSL for mail and webcam=20 I don't really know what to use to point the ip-traffic in its right direction. I had a look at NAT. I think I need NAT just to translate the source, = but NAT comes in when the direction is already determaned.=20 Do I need routing? If so, any suggestions of a package or protocol? I'm a complete newbie to routing. I had a look at Zebra and Gated but = as far as I understand they don't really do what I want. In general I would like to route traffic coming in and going out for my mailserver. Routing on protocol (POP3 and SMTP) would be great. But if = thats hard/impossible routing based on IP would be fine. Local network mailserver ---\ |-- querytraffic --=3D fiber =20 local user ------- firewall ---|-- surftraffic ---=3D cable =20 watchdog ---/ |-- mailtraffic ---=3D adsl =20 Any answers or directions to information will be very much appreciated. -- Enriko Groen, Hosting manager -------------------------------------------------------- netivity bv www.netivity.nl enriko.groen@netivity.nl 038 - 850 1000 van nagellstraat 4 8011 eb zwolle -------------------------------------------------------- =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message