Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ralf Spenneberg <lists@spenneberg.org>
To: Daniel Arjona <darjona@transito.gob.pa>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: I can't resolve DNS name
Date: 30 Aug 2003 13:42:59 +0200	[thread overview]
Message-ID: <1062243778.1605.8.camel@kermit> (raw)
In-Reply-To: <0afd01c36e54$67e73620$0221a0c0@DANIEL>

Am Fre, 2003-08-29 um 19.38 schrieb Daniel Arjona:
> Observations:
> I have LRH 8.0 and iptables is in the my unique server with squid, qmail and
> others.
> My router is directly connected to the NIC of the server.
> When i try to connect to any FTP Server, i recieve this message "I can't
> resolve DNS name"
> I can't do ping to any IP Address
Looking at the iptables output below, I do not see any drop rule. Your
firewall code does not stop any packet. If you can't resolve any name,
test your name resolution and ping an ip-address, like:
ping 217.160.128.61
If that does not work, check your routing.
> echo 1 > /proc/sys/net/ipv4/ip_forward
> [root@transito root]# iptables -t nat -L
> Chain PREROUTING (policy ACCEPT)
> target     prot opt source               destination
> 
> Chain POSTROUTING (policy ACCEPT)
> target     prot opt source               destination
> MASQUERADE  all  --  192.160.33.0/24      anywhere
> 
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
>  ******************************************
> 
> [root@transito root]# iptables -L -n
> 
> Chain INPUT (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
> ACCEPT     all  --  192.160.33.0/24      0.0.0.0/0
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0          tcp dpt:25
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0          tcp dpt:110
> 
> Chain FORWARD (policy ACCEPT)
> target     prot opt source               destination
> ACCEPT     tcp  --  192.160.33.0/24      0.0.0.0/0          tcp dpt:80
> ACCEPT     tcp  --  192.160.33.0/24      0.0.0.0/0          tcp dpt:143
> ACCEPT     tcp  --  192.160.33.0/24      0.0.0.0/0          tcp dpt:53
> ACCEPT     udp  --  192.160.33.0/24      0.0.0.0/0          udp dpt:53
> ACCEPT     tcp  --  192.160.33.0/24      0.0.0.0/0          tcp dpt:21
> ACCEPT     tcp  --  192.160.33.0/24      0.0.0.0/0          tcp dpt:1214
> 
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination

Cheers,

Ralf
-- 
Ralf Spenneberg
RHCE, RHCX

Book: Intrusion Detection für Linux Server   http://www.spenneberg.com
IPsec-Howto				     http://www.ipsec-howto.org
Honeynet Project Mirror:                     http://honeynet.spenneberg.org


      parent reply	other threads:[~2003-08-30 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 17:38 I can't resolve DNS name Daniel Arjona
2003-08-30  1:33 ` cc
2003-08-30 11:42 ` Ralf Spenneberg [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1062243778.1605.8.camel@kermit \
    --to=lists@spenneberg.org \
    --cc=darjona@transito.gob.pa \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox