I have a box hosted inside the firewall. The firewall is passing
external traffic to it fine. When an internal box tries to hit the
external ip, that should loop back inside, connections fail. External
sites can be loaded fine.
What can cause this and how can it be resolved?
thanks
some more details?
-network stucture
-iptables rules
On Tue, 2004-05-18 at 14:02, hanasaki wrote:
I have a box hosted inside the firewall. The firewall is passing
external traffic to it fine. When an internal box tries to hit the
external ip, that should loop back inside, connections
There are many reasons why you should not do this! Setting up DNS is as
easy as nsmasq or running a full DNS server. Posibly on another(your DHCP
server) system.
If you still have no clue, adding the dnat rule to the internal
interface(checking for the external IP) will do.
--- hanasaki [EMAIL
From: Lottie Ortiz
CC: L.oan Department
Date: Tue, 18 May 2004 06:28:59 -0500
Re: L.oan preap.roval
Sir:
We have reviewed you information and glad to inform you
that you qualifyfor 3% mor.tgage r.ate under
our company le.nding program.
Please use this
URL below to enter final details
external internet - firewall - internal web server
internet traffic on port 80 is passed to the internal web server
external internet based browsers can hit the server
inernal based browsers cannot
What iptables runs are needed to let the internal browsers hit the
internal server with the
Hallo debian-firewall@lists.debian.org 's world!
I'm Valerio from Rome, Italy.
I've set-up a firewall's scripts on some Debian servers @ university, work
home.
Can you please have a look at my script to know me any purposes?
And a second question: is in Debian 2.4.18 any utility for the
On Tue, May 18, 2004 at 07:00:15AM -0500, hanasaki wrote:
external internet - firewall - internal web server
internet traffic on port 80 is passed to the internal web server
external internet based browsers can hit the server
inernal based browsers cannot
What iptables runs are needed to
On Tue, 2004-05-18 at 15:16, [EMAIL PROTECTED] wrote:
Hallo debian-firewall@lists.debian.org 's world!
I'm Valerio from Rome, Italy.
Nice to meet you Valerio!
I've set-up a firewall's scripts on some Debian servers @ university, work
home.
Can you please have a look at my script to know
Cheers, Joe
On Tue, May 18, 2004 at 07:00:15AM -0500, hanasaki wrote:
external internet - firewall - internal web server
internet traffic on port 80 is passed to the internal web server
external internet based browsers can hit the server
inernal based browsers cannot
What iptables runs are needed to let the
Richard Verwayen wrote:
On Tue, 2004-05-18 at 15:16, [EMAIL PROTECTED] wrote:
And a second question: is in Debian 2.4.18 any utility for the firewall
rules like shorewall? (please don't hurt me: i don't know now (i'll study
it) how to rebuild kernel sigh!)
apt-get install shorewall
should
Do you have in internal DNS server? If you do, you can avoid the ugly
NAT approach and simply assign the domain name the internal IP.
external clients get external ip, internal clients get internal ip.
On Tue, 2004-05-18 at 22:00, hanasaki wrote:
external internet - firewall - internal web
This is vary ploblematic as Gorge points out. It's just best to be
avoided as setting up a DNS server is so easy. apt-get install resolvconf
dnsmasq; # Is best way togo.
--- Douglas Maxwell [EMAIL PROTECTED] wrote:
On Tue, May 18, 2004 at 07:00:15AM -0500, hanasaki wrote:
external internet -
The below is the approach I ended up using. George and I are thinking
alike. Hope thats a good thing!
host www.domain.com resolves to the internal hostname
when run internally.
I think this is also what [EMAIL PROTECTED] Mike Mestnik was
suggesting. Its a simple elegant solution that
--- George Georgalis [EMAIL PROTECTED] wrote:
On Tue, May 18, 2004 at 07:00:15AM -0500, hanasaki wrote:
external internet - firewall - internal web server
internet traffic on port 80 is passed to the internal web server
external internet based browsers can hit the server
inernal based
15 matches
Mail list logo
