RE: natd or firewall problem?

2005-02-06 Thread Gelsema, Patrick
I think that has to depend on how your natting and firewalling is set up.
Aka how do you manage incoming traffic, outgoing and forwarding traffic
between 2 interfaces.
I'm using ipchains for it, and I got my rules per interface setup, and do
thorough checks regarding sources.

But it is something that could work. Just have to work out your firewall
rules.

I use 2 types of dns, one for internal use, and the other for external. 

My 0,2 cents

Patrick


 -Original Message-
 From: Chris Hodgins [mailto:[EMAIL PROTECTED] 
 Sent: Saturday, February 05, 2005 4:06 PM
 To: Gelsema, Patrick
 Cc: 'Cristian Salan'; 'Gelsema, Patrick'; 
 freebsd-questions@freebsd.org
 Subject: Re: natd or firewall problem?
 
 
 Gelsema, Patrick wrote:
  Thats right, you can do the following:
  Put the ip-address with its FQDn 
 (www.webserverwhatever.com) in every 
  hosts file (taken its windows) or in its hosts file on 
 freebsd. Or you 
  run an internal DNS with an internal zone for your domain whilst 
  running on the internet the external zone.
  
  Regards,
  
  Patrick
  
 
 Out of interest, why would using the external ip address not work. 
 Would the packets not just be directed out to the router as per usual 
 and then the router would notice it should forward the packets to the 
 www server?  What am I missing?  The only problem I can think 
 of might 
 be sending packets back to the internal ip address.
 
 Thanks
 Chris
 
 [snip]
 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: natd or firewall problem?

2005-02-05 Thread Gelsema, Patrick
Hi,

IN order to enlighten you we need some more information. Sounds to me you
could be having issues with internal/external DNS and ip-addresses. In
other words, you are querying your www server from a dns and is getting
the Internet ip back instead of the lan ip. Can you connect to your www
server with ip?

Regards

Patrick

 Hello dear list,

 I have one FreeBSD router in front of the internal network. Now I've
 installed another FreeBSD box which must be the www sever.
 I've managed to redirect the port 80 at the router and the web server
 is visible to the outside world. But the problem is now at the other
 internal workstations which are unable to browse the web server.

 Please enlighten me,
 Cristian Salan
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: natd or firewall problem?

2005-02-05 Thread Cristian Salan
  Hello dear list,
 
  I have one FreeBSD router in front of the internal network. Now I've
  installed another FreeBSD box which must be the www sever.
  I've managed to redirect the port 80 at the router and the web server
  is visible to the outside world. But the problem is now at the other
  internal workstations which are unable to browse the web server.
 
  Please enlighten me,
  Cristian Salan

On Sat, 5 Feb 2005 12:42:13 +0100 (CET), Gelsema, Patrick
[EMAIL PROTECTED] wrote:
 Hi,
 
 IN order to enlighten you we need some more information. Sounds to me you
 could be having issues with internal/external DNS and ip-addresses. In
 other words, you are querying your www server from a dns and is getting
 the Internet ip back instead of the lan ip. Can you connect to your www
 server with ip?

I can only connect using the internal ip address. Otherwise, yes, when
querying for the name I get the external IP address. There is no DNS
server on this lan. Is this the problem?

Cristian Salan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: natd or firewall problem?

2005-02-05 Thread Gelsema, Patrick
Thats right, you can do the following:
Put the ip-address with its FQDn (www.webserverwhatever.com) in every hosts
file (taken its windows) or in its hosts file on freebsd. Or you run an
internal DNS with an internal zone for your domain whilst running on the
internet the external zone.

Regards,

Patrick

 -Original Message-
 From: Cristian Salan [mailto:[EMAIL PROTECTED] 
 Sent: Saturday, February 05, 2005 1:51 PM
 To: Gelsema, Patrick
 Cc: freebsd-questions@freebsd.org
 Subject: Re: natd or firewall problem?
 
 
   Hello dear list,
  
   I have one FreeBSD router in front of the internal 
 network. Now I've 
   installed another FreeBSD box which must be the www sever. I've 
   managed to redirect the port 80 at the router and the web 
 server is 
   visible to the outside world. But the problem is now at the other 
   internal workstations which are unable to browse the web server.
  
   Please enlighten me,
   Cristian Salan
 
 On Sat, 5 Feb 2005 12:42:13 +0100 (CET), Gelsema, Patrick 
 [EMAIL PROTECTED] wrote:
  Hi,
  
  IN order to enlighten you we need some more information. 
 Sounds to me 
  you could be having issues with internal/external DNS and 
  ip-addresses. In other words, you are querying your www 
 server from a 
  dns and is getting the Internet ip back instead of the lan 
 ip. Can you 
  connect to your www server with ip?
 
 I can only connect using the internal ip address. Otherwise, 
 yes, when querying for the name I get the external IP 
 address. There is no DNS server on this lan. Is this the problem?
 
 Cristian Salan
 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: natd or firewall problem?

2005-02-05 Thread Cristian Salan
On Sat, 5 Feb 2005 13:54:23 +0100, Gelsema, Patrick
[EMAIL PROTECTED] wrote:
 Thats right, you can do the following:
 Put the ip-address with its FQDn (www.webserverwhatever.com) in every hosts
 file (taken its windows) or in its hosts file on freebsd. Or you run an
 internal DNS with an internal zone for your domain whilst running on the
 internet the external zone.
 
 Regards,
 
 Patrick

Thank you Patrick, that's what I was afraid of. I've never managed to
understand the DNS service but I think the time has come.

Best regards,
Cristian Salan
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: natd or firewall problem?

2005-02-05 Thread Chris Hodgins
Gelsema, Patrick wrote:
Thats right, you can do the following:
Put the ip-address with its FQDn (www.webserverwhatever.com) in every hosts
file (taken its windows) or in its hosts file on freebsd. Or you run an
internal DNS with an internal zone for your domain whilst running on the
internet the external zone.
Regards,
Patrick
Out of interest, why would using the external ip address not work. 
Would the packets not just be directed out to the router as per usual 
and then the router would notice it should forward the packets to the 
www server?  What am I missing?  The only problem I can think of might 
be sending packets back to the internal ip address.

Thanks
Chris
[snip]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]