Re: [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- From: "Rowan R." <yaardone@xxxxxxxxx>
- Date: Tue, 1 Dec 2009 13:06:33 -0800
Running bind on the firewall it would resolve DNS requests for
http://www.rowansweb.com/ coming from an internal zone to
the DMZ machine.
Whereas someone outside your network would simply
get pointed to your external IP, and the firewall would route
it to the DMZ.
I don't think it's a DNS issue, our DNS server is running on the
internal network (windows). If I try to connect using the IP it's a no
go. For some reason however I can connect to my ext:zone. I tried
changing my dmz interface to an ext:zone but no luck. see config
below.
192.168.1.0/24(masq)zone:int (eth0)-------[f/w ]----108.***.***.60
(eth2) zone:ext
[box]-----68.***.***.234(eth1) zone:dmz
for some reason my masq net cannot connect to eth1 doesn't matter if
it's zone:ext or zone:dmz
--
The general who advances without coveting fame and retreats without
fearing disgrace, whose only thought is to protect his country and do
good service for his sovereign, is the jewel of the kingdom.
- Sun Tzu
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- Follow-Ups:
- References:
- [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- From: Rowan R.
- Re: [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- From: John Andersen
- [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- Prev by Date: Re: [opensuse] zypper : Failed to download ./repodata/primary.xml.gz
- Next by Date: Re: [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- Previous by thread: Re: [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- Next by thread: Re: [opensuse] SuSEfirewall2: unable to connect to DMZ from behind NAT
- Index(es):
Relevant Pages
|