🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.os.linux.suse
Article #193

urgend: routing problem!!!?

#193
From: alex
Date: Sat, 17 Nov 2001 01:19
42 lines
3341 bytes
hi

i've installed a suse 7.2. this one will be our router and firewall. first
of all. the box has 3 NIC's. and the problem is - i cannot access everything
from the boxes behind the router... :-(((. on next monday everything need to
work...

ip's are examples:
eth0: official ip address - 213.14.46.4, gateway is 213.14.46.1, subnetmask
255.255.255.248 - 6 ip's possible
eth1: official ip address - 217.10.0.46, subnetmask 255.255.255.240 - 14
ip's possible
eth2: official ip address - 217.10.0.62, subnetmask 255.255.255.240 - 14
ip's possible

now - if i'm on the linux box (router) with ip 213.14.46.4. i can ping the
hole world and reach servers in the world... i can ping the ip's in eth1 and
eth2. and the hosts behind eth1 (i haven't tested behind eth2 - but schould
work, too). now the problem... i cannot access the world from (DMZ - behind
eth1). there is a box with ip 217.10.0.34. on this box i can ping the eth1
(the gateway i defined for this net - 217.10.0.46). BUT i cannot reach
gateway is 213.14.46.1 or any other host behind eth0 (internet).

i've stoped for testing my susefirewall2 (but there was no drops befor or
something else) and activated the ip_forwarding with echo "1" >
/proc/sys/net/ipv4/ip_forward - but it isn't working too! are you able to
explain me what to do to solve my problems?

is it possible that my ISP dosn't route my networks correctly? now i'm at
home and i've done a tracert from here to the networks. first of all i ping
and tracert to 213.14.46.4. this will work. now i have ping and tracert to
of 217.10.0.34... the way the tracert goes is different... inside the ISP
net the tracert goes another way!?!?!

if you can please describe me shortly what need to be done in principle to
get a suse working as a router. am i right about the way above? are the only
things to do setting up the NIC's with the official ip addresses and
activate ip_forwarding ore is there anything additional to do?!


absolutly confused... PLEASE HELP
Alex
Technical Details
Message-ID: <9t4du7$vkq$01$1@news.t-online.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!fr.usenet-edu.net!usenet-edu.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1041dd,91657daef03fa5fd,start
X-Google-Attributes: gid1041dd,public
X-Google-Thread: f4b73,91657daef03fa5fd,start
X-Google-Attributes: gidf4b73,public
X-Google-Thread: 10669a,91657daef03fa5fd,start
X-Google-Attributes: gid10669a,public
X-Google-ArrivalTime: 2001-11-16 17:21:11 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!fr.usenet-edu.net!usenet-edu.net!fr.clara.net!heighliner.fr.clara.net!newsfeed01.sul.t-online.de!newsmm00.sul.t-online.com!t-online.de!news.t-online.com!not-for-mail
From: "alex" <ntnewsNOSPAM@hrz3.hrz.tu-darmstadt.de>
Newsgroups: alt.os.linux.suse,ch.comp.os.linux,comp.os.linux.networking
Subject: urgend: routing problem!!!?
Date: Sat, 17 Nov 2001 02:19:03 +0100
Organization: T-Online
Lines: 46
Message-ID: <9t4du7$vkq$01$1@news.t-online.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: news.t-online.com 1005959944 01 32410 7WGLTaMXSlA4Vz 011117 01:19:04
X-Complaints-To: abuse@t-online.com
X-Sender: 520078324419-0001@t-dialin.net
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000