Re: can't resolve names, ipchains or dns problem

2001-03-18 Thread Mircea Luca
Nick wrote:
 
 Hi list,
 
 I have an internal network setup behind linux on a single static IP
 I am having problem reolving names but can ping IP's numericaly.
 
 I set up dhcp to allocate 192.168.1.0/24 throught the internal network
 Then I setup ipchains very basic, just to get it all going
 
 ipchains -P forward DENY
 ipchains -A forward -s 192.168.1.0/24 -j MASQ
 
 kernel is set to forward, echo 1  /proc/sys/net/ipv4/ip_forward
 
 So I can ping from an internal machine to any global IP address, but when it
 comes to ping www.yahoo.com, get a bad host message.
 
 Using 192.168.1.1 as gateway for internal machines
 looked at /etc/resolv.conf,  looks ok
 /etc/hosts
 /etc/network/interfaces all good too
 
 route tables look ok
 have 255.255.255.255 line for dhcp windozs
 default gateway ok
 
 I can ping domain names and ip address from the linux firewall.
 Just doesn't seem to want to forward those requests for the internal network
 
 HELP!!!
 

Did you setup your dhcp server to give the dns addresses to clients ?
When you use dhcp the /etc/resolv.conf is replaced by the one used by
the dhcp
cient hence the dhcp server have to send them.



Re: can't resolve names, ipchains or dns problem

2001-03-18 Thread Albrecht Frank
Nick wrote:
 
 Hi list,
 
 I have an internal network setup behind linux on a single static IP
 I am having problem reolving names but can ping IP's numericaly.
 
 I set up dhcp to allocate 192.168.1.0/24 throught the internal network
 Then I setup ipchains very basic, just to get it all going
 
 ipchains -P forward DENY
 ipchains -A forward -s 192.168.1.0/24 -j MASQ
 
 kernel is set to forward, echo 1  /proc/sys/net/ipv4/ip_forward
 
 So I can ping from an internal machine to any global IP address, but when it
 comes to ping www.yahoo.com, get a bad host message.
 
 Using 192.168.1.1 as gateway for internal machines
 looked at /etc/resolv.conf,  looks ok
 /etc/hosts
 /etc/network/interfaces all good too
 
 route tables look ok
 have 255.255.255.255 line for dhcp windozs
 default gateway ok
 
 I can ping domain names and ip address from the linux firewall.
 Just doesn't seem to want to forward those requests for the internal network
 
 HELP!!!
 
 -Nick

Hi Nick,
install the packet ipmasqadm on your firewall box and edit the files in
/etc/ipmasq/rules. there are good samples and default values for 
masquerading.

Greetings
Albrecht



Re: can't resolve names, ipchains or dns problem

2001-03-18 Thread Daniel de los Reyes
El Sun, Mar 18, 2001 at 10:59:26AM +0100, Albrecht Frank dijo:
-| Nick wrote:
-|  
-|  Hi list,
-|  
-|  I have an internal network setup behind linux on a single static IP
-|  I am having problem reolving names but can ping IP's numericaly.
-|  
-|  I set up dhcp to allocate 192.168.1.0/24 throught the internal network
-|  Then I setup ipchains very basic, just to get it all going
-|  
-|  ipchains -P forward DENY
-|  ipchains -A forward -s 192.168.1.0/24 -j MASQ
-|  
-|  kernel is set to forward, echo 1  /proc/sys/net/ipv4/ip_forward
-|  
-|  So I can ping from an internal machine to any global IP address, but when 
it
-|  comes to ping www.yahoo.com, get a bad host message.
-|  
-|  Using 192.168.1.1 as gateway for internal machines
-|  looked at /etc/resolv.conf,  looks ok
-|  /etc/hosts
-|  /etc/network/interfaces all good too
-|  
-|  route tables look ok
-|  have 255.255.255.255 line for dhcp windozs
-|  default gateway ok
-|  
-|  I can ping domain names and ip address from the linux firewall.
-|  Just doesn't seem to want to forward those requests for the internal 
network
-|  
-|  HELP!!!

Sorry if it is a dumb sugestion, but are you assigning the needed DNS
servers to your client machines with the dhcp server?
If you don't, or you don't manually set each client's resolv.conf (dumb
thing to do if you use dhcpd) then yor client machines won't be able to
resolve names.

HTH
-- 
__
Daniel de los Reyes
S2-Selling Soluciones
Valencia Spain
e-mail: [EMAIL PROTECTED]
Powered by Debian GNU-Linux 2.2r2
__



can't resolve names, ipchains or dns problem

2001-03-17 Thread Nick
Hi list,

I have an internal network setup behind linux on a single static IP
I am having problem reolving names but can ping IP's numericaly.

I set up dhcp to allocate 192.168.1.0/24 throught the internal network
Then I setup ipchains very basic, just to get it all going

ipchains -P forward DENY
ipchains -A forward -s 192.168.1.0/24 -j MASQ

kernel is set to forward, echo 1  /proc/sys/net/ipv4/ip_forward

So I can ping from an internal machine to any global IP address, but when it 
comes to ping www.yahoo.com, get a bad host message.

Using 192.168.1.1 as gateway for internal machines
looked at /etc/resolv.conf,  looks ok
/etc/hosts
/etc/network/interfaces all good too

route tables look ok
have 255.255.255.255 line for dhcp windozs
default gateway ok

I can ping domain names and ip address from the linux firewall.
Just doesn't seem to want to forward those requests for the internal network 


HELP!!!

-Nick



Re: can't resolve names, ipchains or dns problem

2001-03-17 Thread Alvin Oga

hi nic

if yu can ping using the ip#...

just add your dns server ip# into /etc/resolv.conf

c ya
alvin

On Sat, 17 Mar 2001, Nick wrote:

 Hi list,
 
 I have an internal network setup behind linux on a single static IP
 I am having problem reolving names but can ping IP's numericaly.
 
 I set up dhcp to allocate 192.168.1.0/24 throught the internal network
 Then I setup ipchains very basic, just to get it all going
 
 ipchains -P forward DENY
 ipchains -A forward -s 192.168.1.0/24 -j MASQ
 
 kernel is set to forward, echo 1  /proc/sys/net/ipv4/ip_forward
 
 So I can ping from an internal machine to any global IP address, but when it 
 comes to ping www.yahoo.com, get a bad host message.
 
 Using 192.168.1.1 as gateway for internal machines
 looked at /etc/resolv.conf,  looks ok
 /etc/hosts
 /etc/network/interfaces all good too
 
 route tables look ok
 have 255.255.255.255 line for dhcp windozs
 default gateway ok
 
 I can ping domain names and ip address from the linux firewall.
 Just doesn't seem to want to forward those requests for the internal network 
 
 
 HELP!!!
 
 -Nick
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]