🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

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

Re: iptables/routing and DMZ's

#225
From: alex
Date: Fri, 12 Oct 2001 07:15
92 lines
4711 bytes
hi Jonathan

i'm not shure that i've understood you correctly. i will think this is a
routing configuration problem, too. the firewall stuff comes afterwards to
this... but i'm new in linux and routing, too. routing is one of the things
i've never needed in the past 5 years of my work :-).

do i need to route a specific ip address for e.g. 210.2.5.20 to eth1? how
will this be done in detail? (sorry for this stupid answer but i'm a neebie
on this). something like route packets from 210.2.5.17 (eth0) to
(210.2.5.19) eth1 and eth1 gives the packets to 210.2.5.20?

Regards
Alex


"Jonathan Hume" <jonathan.hume@ntlworld.com> schrieb im Newsbeitrag
news:3BC628F2.60503@ntlworld.com...
> Hi Alex,
>
> Doh, I think I got the wrong end of the stick!
>
> I'm not sure if I know the answer, but for clarity am I right in
> thinking that what you'd like to do is the following:
>
> eth0=210.2.5.16-31 ---  Router ---  eth1=210.2.5.19
>                             |
>                             |
>                              -------- eth2=210.2.5.25
>
>
>   i.e. pick up everything on eth0 for the address range 210.2.5.16
> through 210.2.5.31, and then route to either eth1 or eth2 for the
> appropriate IP addresses. Additionally you'd like both eth1 and eth2 to
> be outside of the firewall, i.e. in the DMZ.
>
> If this is the case then your original mask looks to me to be correct
> since it masks of your block of assigned addresses. Maybe what really
> needs to be played with is the Yast2 Network Routing configuration
> rather than the firewall stuff (note I'm guessing since this is getting
> well out of my depth :-) ).
>
> Good luck
>
> JH
>
>
>
>
>
> alex wrote:
> >>As Cedric says they need be on seperate subnets, however when your
> >>current subnet mask is bitwise AND'ed with either of the two current
> >>addresses you specify it can't see any difference between the subnets.
> >>The solution   is to reallocate either of the two IP addresses so that
> >>they  appear different using your existing subnet mask or to change the
> >>last part of your subnet mask to
> >>248 = 1111 1000
> >>
> >
> > i get from my isp 16 addresses this can only be done by a subnet
> > 255.255.255.240 (210.2.5.16-31) - i think so!? if i am wrong - please
> > correct me... and please tell my why (newbie :-((( ). this is the
situation
> > i'm in - and i need to workaround - how ever!
> >
> > can i change the subnetmask without telling this my isp? realy i haven't
> > anytime worked with calculating ip subnets... and haven't deep tcpip
> > knowledge :-((( one of my greatest problems...
> >
> > am i right and will this be working if i will change this to
> > eth0 = 210.2.5.17 / 255.255.255.252 - (210.2.5.16-19)
> > eth1 = 210.2.5.20 / 255.255.255.248 - (210.2.5.16-23)
> > eth2 = 210.2.5.24 / 255.255.255.248 - (210.2.5.24-31)
> >
> > hm... looks wrong... eth0 and eth1 having overlapping ip's... in eth0
.19 is
> > broadcast adress and in eth1 the .23 - this looks like only 2 hosts in
> > dmz... shit...
> >
> > hm. i don't realy need to route the official ip address over eth2 - i
can
> > masquerade - if no other way is possible... but this might bei a bad
> > workaround, on my view.
> >
> >
> > Alex
> >
> >
> >
> >
>
Technical Details
Message-ID: <9q65al$o2k$07$1@news.t-online.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!isdnet!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
References: <9q3qa9$tbr$06$1@news.t-online.com> <3BC5D700.8040408@ntlworld.com> <9q4vv7$csk$00$1@news.t-online.com> <3BC628F2.60503@ntlworld.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1041dd,b373d989fc833e9e
X-Google-Attributes: gid1041dd,public
X-Google-Thread: f4b73,b373d989fc833e9e
X-Google-Attributes: gidf4b73,public
X-Google-Thread: 10669a,b373d989fc833e9e
X-Google-Attributes: gid10669a,public
X-Google-ArrivalTime: 2001-10-12 00:17:55 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!isdnet!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: Re: iptables/routing and DMZ's
Date: Fri, 12 Oct 2001 09:15:32 +0200
Organization: T-Online
Lines: 94
Message-ID: <9q65al$o2k$07$1@news.t-online.com>
References: <9q3qa9$tbr$06$1@news.t-online.com> <3BC5D700.8040408@ntlworld.com> <9q4vv7$csk$00$1@news.t-online.com> <3BC628F2.60503@ntlworld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: news.t-online.com 1002870933 07 24660 J2UWSUSGSpAV7q 011012 07:15:33
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