From: Manish Kathuria <manish@tuxspace.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] multiple isp + nat
Date: Fri, 13 Jan 2006 16:44:30 +0000 [thread overview]
Message-ID: <43C7D61E.3090106@tuxspace.com> (raw)
In-Reply-To: <1a9f78a60601130300h7a4458a1te78801863c7845e2@mail.gmail.com>
Janne Raatikainen wrote:
> I configured multiple isp (actually only multiple gw) according
> http://lartc.org/howto/lartc.rpdb.multiple-links.html.
>
> Now NAT (Internet) seems to work, both external interfaces work ( I
> didnt configure load balancing because I dont need it). However I have
> problem that I can not ping from NAT to public ip of my Linux box.
> Problem is that I can not connect from 192.168.1.0/24 network to
> services listening 84.248.213.195, but I can connect to Internet from
> NAT through that interface gateway (84.248.192.0). Connecting with
> public ip worked fine when I had simple NAT, with single
> Internet-connection.
Have you used any firewall rules which prevent INPUT from the LAN ?
>
> I also notice that portforwarding from Linux-box (public ip) to computer
> under nat doesnt work too. Anyone has idea what is the problem?
You will have to accept the traffic in the FOWARD chain in addition to
the port forwarding rule for the system which is being accessed.
I think it will be better if you list your firewall rules here to make
the things clear. It will make it easier to identify the reason.
Do I have to use some different kind of iptables-rules (fwmark?), than
I used
> when I had only one connection to Internet, or do I have to add some
> route or gw?
>
> Janne
>
--
Manish
http://www.tuxspace.com/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-01-13 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 11:00 [LARTC] multiple isp + nat Janne Raatikainen
2006-01-13 16:44 ` Manish Kathuria [this message]
2006-01-14 10:06 ` Janne Raatikainen
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=43C7D61E.3090106@tuxspace.com \
--to=manish@tuxspace.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.