From: Jeffrey Walton <noloader@gmail.com>
To: development@lists.ipfire.org
Subject: IP traffic being dropped rather than forwarded
Date: Sun, 22 Jul 2018 11:40:20 -0400 [thread overview]
Message-ID: <CAH8yC8mYn_+9TriHg6AQS0K2Rs1gvA4k26a=ifkR+FY0GkPatA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Hi Everyone,
My apologies if this is the wrong list. I did not see a Users list at
https://lists.ipfire.org/mailman/listinfo . Please let me know a
better list if one is available.
I'm following https://wiki.ipfire.org/configuration/firewall/rules/port-forwarding.
I've setup a port forwarding rule to send inbound TCP|UDP/1522 traffic
to an internal host/22 (i.e., forward to SSH). See
https://postimg.cc/image/ubpzpkaaf/ .
Inspecting the Firewall Log shows the traffic is being DROP_INPUT. See
https://s15.postimg.cc/sl6ynm2wr/Firewall-2.png .
I don't understand two items. First, why is this listed under Outgoing
Firewall Rules? This is something to handle incoming traffic, not
outgoing traffic.
Second, the "Destination" and the "Firewall: 22" part. I'm pretty sure
I configured <any>:1522 to forward to <internal host>:22.
How does one forward <incoming>:1522 to <host>:22? What am I doing
wrong? Is there an easier way to do this?
reply other threads:[~2018-07-22 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH8yC8mYn_+9TriHg6AQS0K2Rs1gvA4k26a=ifkR+FY0GkPatA@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=development@lists.ipfire.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