From: "André Serralheiro" <serralheiro@gmail.com>
To: Luca Ferrari <fluca1978@infinito.it>
Cc: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: a little help on iptables
Date: Thu, 7 Sep 2006 17:15:39 +0200 [thread overview]
Message-ID: <b2a039d0609070815i6d97262ejaa08b2ea149cea4e@mail.gmail.com> (raw)
In-Reply-To: <200609071640.33138.fluca1978@infinito.it>
Hi Luca
It could be easier to give you a hand if you provides us with the
output of: ifconfig; route -n and iptables -L (and iptables -L -t nat)
you call always try to execute the following:
route add default gateway x.x.x.x netmask y.y.y.y ethX
for the default gateway and:
route add -net z.z.z.z netmask k.k.k.k dev ethY
for the other route
Hope it helps
Andre Serralheiro
On 9/7/06, Luca Ferrari <fluca1978@infinito.it> wrote:
> Hi all,
> this is the situation: I've got a firewall double-homed, with a NIC assigned
> to a public IP and the other to the LAN network. Until now I've used the
> external NIC as default gateway, since my router has a public address too.
> Now I'd like to use another router on the lan as default, leaving untouched
> the external interface (since the firewall must be accessible from the
> outside world). So I've changed the default gw to the lan one, and it works,
> but I get the external ip unreachable, and I think it's because it does not
> know the gateway interface. So, how can I specify for the external interface
> the gateway to use? If I try to do it thru the route command it replies sayng
> that the network is unreachable. Any help?
> Thanks,
> Luca
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-09-07 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 14:40 a little help on iptables Luca Ferrari
2006-09-07 15:15 ` André Serralheiro [this message]
2006-09-07 16:24 ` urgrue
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=b2a039d0609070815i6d97262ejaa08b2ea149cea4e@mail.gmail.com \
--to=serralheiro@gmail.com \
--cc=fluca1978@infinito.it \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).