From: SaVaGE <pc-secure@home.nl>
To: netfilter@lists.netfilter.org
Subject: Re: Local IP not being local
Date: Tue, 29 Apr 2003 08:33:40 +0200 [thread overview]
Message-ID: <200304290833.40340.pc-secure@home.nl> (raw)
In-Reply-To: <20030429012755.66519.qmail@web11501.mail.yahoo.com>
Op dinsdag 29 april 2003 03:27, schreef Miguel Manso:
> Hi there,
>
> I've a linux machine acting as a router. I'm VERY happy with it and I'm
> learning a lot (iptables rocks).
>
> Now, I've something strange that I don't know how to solve.
>
> I've a static public IP, let's imagine - 100.100.100.1
>
> All the requests to that IP are redirected to the internal ip - 192.168.1.6
>
> Now, inside 192.168.1.6 if I ping 100.100.100.1 I get:
>
> 64 bytes from 100.100.100.1: icmp_seq=16 ttl=61 time=23.7 ms
>
> But, if I ping 'localhost' I get:
>
> 64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64
> time=0.044 ms
>
>
> This means that the ping that I'm doing to 100.100.100.1 is going to the
> router, going to the outside, coming back to the router and to the internal
> machine again.
>
> Can I "say" something to the linux router to just redirect all the requests
> to the 100.100.100.1 ip to the internal machine 192.168.1.6?
>
> Thanks a lot for the help.
>
> =====
> Miguel Manso
> mmanso@yahoo.com
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
My guess is, you have to alter your /etc/hosts file , cause when internal ip
not is recognized ,then a query to the outside wil be made.
/etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.6 yourname domain yourname
100.100.100.1 yourname2domain yourname2
Pascal (PC-Secure)
prev parent reply other threads:[~2003-04-29 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 1:27 Local IP not being local Miguel Manso
2003-04-29 6:33 ` SaVaGE [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=200304290833.40340.pc-secure@home.nl \
--to=pc-secure@home.nl \
--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