Re: DMZ routing issues - HELP PLEASE

From: prg (rdgentry1_at_cablelynx.com)
Date: 04/03/05


Date: 3 Apr 2005 08:04:29 -0700


news.uunet.co.za wrote:

[please, don't top post or edit/drop info. makes answering a pain]

[re-arranged]
>
>
> "Davide Bianchi" <davideyeahsure@onlyforfun.net> wrote in message
> news:slrnd4vmg2.190.davideyeahsure@fogg.onlyforfun.net...
> > On 2005-04-03, news.uunet.co.za <pjtdownes@hotmail.com> wrote:
> > > I suspect that I need to set up routes on firewall2 to point back
to the
> > > LAN.

You'll need network routes for all subnets on all IS routers.

> > I suspect that you misconfigured your firewall, so all the
connection are
> > dropped by your second firewall.
> >
> > > Where am I going wrong?

Don't worry about firewalls till you have basic connectivity (ping)
working.

> > In not investigating the problem. Start by using a packet inspector
> > on the external firewall to see if packests sent by your lan are
routed
> > to the internet and if you get an answer, if you do, see which
answer
> > and follow it to wherever is routed to.

$ ping and $ traceroute (and excess brain cells;) should be all you
need to establish proper connectivity. Right now you just need to find
out _where_ your packets are being dropped.

> By bypassing the second firewall, this works:
> LAN ======> Firewall1======>Internet
>
> By connecting to the DMZ, this works:
> DMZ======>Firewall2======>Internet
>
> But when I put it all together, it does NOT work.
> LAN ======> Firewall1======>DMZ======>Firewall2======>Internet
>
> I believe that there is a route missing?

Your belief is likely (multiply) well founded ;)

If you can disconnect from the internet easily, do so.

Turn off _all_ firewalls.

Choose one host in lan and slowly, tediously get connectivity working.

$ ping the following:

127.0.0.1
local host's IP address
local host's GW router (lan nic on FW1)
DMZ nic on FW1
DMZ nic on FW2
Internet nic on FW2

Where does it fail to return?

Check $ /sbin/route -n
and confirm that there is an entry for _all_ subnets you wish to reach
(directly or indirectly) from/through this machine.

Continue nic-by-nic, machine-by-machine. Ie., get the lan host to
successfully $ ping all the way to Internet nic on FW2. Move on to FW1
and confirm $ ping to all other nic IPs, using the same tedious
process. Repeat on DMZ machine and FW2.

Once you can $ ping from anywhere to anywhere (that you desire), you
might want to connect to DMZ servers/daemons just to confirm all is
well and as expected.

If there are any glitches, you might try to $ traceroute to the IPs.

Now, you can bring up firewalls one at a time, starting at lan host,
then FW1, then DMZ, then FW2. Confirm that connectivity continues
working at each stage as it should. Now you know why disabling $ ping
(ECHO) replies out of a misguided sense of "added security" will
eventually cause grief ;)

Here is where a packet sniffer may be handy. Iptables' logs can also
be helpful if you configure/turn them on and know what you're looking
for.

Remember, that you can have only one _default_ route (normally), but
there is no reason why you cannot have multiple gateway/network routes.
 It might be good to review the networking howtos and add/confirm the
needed route entries one-by-one as you are establishing connectivity.

Yes, it is tedious and a pain-in-the-arse to be so anally methodical,
but if you don't keep the number of changes (varibles) to a minimum as
you go, you can really confuse yourself -- doesn't take much for me ;)

BTW, presumably, you are NATing only at FW2 and you are not running DNS
on the lan.

hth,
prg



Relevant Pages

  • Re: Help w/iptables & masquerade, I looked everywhere
    ... > linux box to actually route traffic. ... Problem is I can't actually access or ping the ... Do I need to do a route command? ... IP connectivity before futzing with the RH9/XP firewalls. ...
    (comp.os.linux.networking)
  • Re: Help w/iptables & masquerade, I looked everywhere
    ... If I ping from eth1 I get name resolution, ... I'm not worried about the workstations yet as I can't even ping from eth1 ... Do I need to do a route command? ... > IP connectivity before futzing with the RH9/XP firewalls. ...
    (comp.os.linux.networking)
  • Re: [Fwd: Re: bge Ierr rate increase from 5.3R -> 6.1R]
    ... Link detection in -current generally seems to be much worse than ... The first ping tends to fail ... an "ntpdate -b" early in the boot fails about ... route expiry and the possibly the driver's interaction with this. ...
    (freebsd-net)
  • Re: ping problem ...
    ... PING 192.168.1.1 56bytes of data. ... ifconfig and route output when ping fails. ... tell us a bit about your network. ... an implicit route through a local interface on the 192.168.x.y ...
    (comp.os.linux.networking)
  • Re: Linux routing mystery. No replies until machine sources traffic.
    ... The machine has an interface on each of these ... You cannot have more than one default route. ... A machine can ping ... 1.1.1.0/24 dev eth0 proto kernel scope link src 1.1.1.5 ...
    (comp.os.linux.networking)