On Thu, Jan 3, 2013 at 3:37 AM, Jorge Fábregas wrote:
> Ok, I've posted a similar setup I've used in the past that worked like a
> charm. The script is the actual /etc/sysconfig/iptables. You'll notice
> the syntax there is somehow different than when you manually create the
> rules (or put in a
Jorge Fábregas wrote:
Ok, I've posted a similar setup I've used in the past that worked like a
charm. The script is the actual /etc/sysconfig/iptables. You'll notice
the syntax there is somehow different than when you manually create the
rules (or put in a script) but you get the idea. Those r
2013/1/3 Jorge Fábregas :
> Ok, I've posted a similar setup I've used in the past that worked like a
> charm. The script is the actual /etc/sysconfig/iptables. You'll notice
> the syntax there is somehow different than when you manually create the
> rules (or put in a script) but you get the idea
On 01/02/2013 06:54 PM, Alan Evans wrote:
This is really related to iptables, not I presume Fedora-specific. But
I'm really hoping that somebody here will be able to school me on
iptables, so I don't have to find and subscribe to some other list
just to ask one question.
For what it is worth
Ok, I've posted a similar setup I've used in the past that worked like a
charm. The script is the actual /etc/sysconfig/iptables. You'll notice
the syntax there is somehow different than when you manually create the
rules (or put in a script) but you get the idea. Those rules WERE THE
MINIMUM re
I'll try this tomorrow when I get into work. But at first look it seems
awfully familiar, like it's something that I've already tried. Thanks,
though. At this point I'll try whatever somebody thinks might work.
-Alan
Maybe I should have put it this way.
This one does the redirect.
iptables -t
On 01/03/2013 03:47 AM, Alan Evans wrote:
> Anyway, the rule I posted is the only rule in use here. I have tried other
> iterations that did involve a MASQUERADE rule, but they didn't work either.
> Like I said, I've been scouring google to solve this for a long time.
I see but this doesn't makes
On Wed, Jan 2, 2013 at 7:50 PM, Gary Hodder wrote:
try this
> ppp0=Internet connection
> eth0=local area network connection
> This will forward port 22 on the Internet to machine 192.168.0.2 port 22
> on local network.
>
> iptables -A FORWARD -p tcp -i ppp0 -o eth0 -d 192.168.0.2 --dport 22 -j
> A
On Wed, Jan 2, 2013 at 6:13 PM, Jorge Fábregas wrote:
>
> Please elaborate more.
I'll try.
> Why does 192.168.0.35 perform DNS queries
> against the "external interface" of the firewall? Why not use the
> internal ip?
It doesn't.
I'll try to be more specific:
There are at least four machin
On Wed, 2013-01-02 at 15:54 -0800, Alan Evans wrote:
> This is really related to iptables, not I presume Fedora-specific. But
> I'm really hoping that somebody here will be able to school me on
> iptables, so I don't have to find and subscribe to some other list
> just to ask one question.
>
>
>
On 01/02/2013 07:54 PM, Alan Evans wrote:
> DNS queries (portal is also a DNS server) to the external
> interface stop working.
Hi,
Please elaborate more. Why does 192.168.0.35 perform DNS queries
against the "external interface" of the firewall? Why not use the
internal ip? If you manually pe
This is really related to iptables, not I presume Fedora-specific. But I'm
really hoping that somebody here will be able to school me on iptables, so
I don't have to find and subscribe to some other list just to ask one
question.
I'm faced with the problem of needing to punch a hole in a firewall
12 matches
Mail list logo
