All of lore.kernel.org
 help / color / mirror / Atom feed
From: netfilter_user <netfilter_user@o2.pl>
To: Arnt Karlsen <arnt@c2i.net>
Cc: netfilter@lists.netfilter.org
Subject: Re[4]: access to server
Date: Wed, 30 Apr 2003 15:32:17 +0200	[thread overview]
Message-ID: <211627560.20030430153217@o2.pl> (raw)
In-Reply-To: <20030430044745.621e715a.arnt@c2i.net>

Hello Arnt,

Wednesday, April 30, 2003, 4:47:45 AM, you wrote:

AK> On Wed, 30 Apr 2003 03:38:12 +0200, 
AK> netfilter_user <netfilter_user@o2.pl> wrote in message 
AK> <1246491441.20030430033812@o2.pl>:

>> Hello Arnt,
>> 
>> Wednesday, April 30, 2003, 3:10:30 AM, you wrote:
>> 
>> AK> On Wed, 30 Apr 2003 00:49:31 +0200, 
>> AK> netfilter_user <netfilter_user@o2.pl> wrote in message 
>> AK> <5436369716.20030430004931@o2.pl>:
>> 
>> >> Rule: "iptables -A FORWARD -i eth1 -p udp -m --multioport --dport 
>> AK>                                                      /\
>> AK> ..is " -m --multioport " a valid match in iptables, or a correct 
>> AK> quote of your attempt to write  ' -m --multiport ' ?
>> 
>> damn my wrong...it should looks like this:
>> iptables -A FORWARD -i eth1 -p udp -m --multioport --dport 23073,23083
>> -j ACCEPT                                   /\
AK>                                               ||
AK> ..lets try again: I don't find "-m --multioport" _anywhere_ 
AK> in the docs, so, if you _actually_ try '-m --multioport' in
AK> your rule set, it _should_ fail, then you'll wanna try 
AK> '-m --multiport', without your extra "o".  ;-)

Oh yes, now i got, i was too sleepy yestorday to understand. Actualy
this rule looks like this:

iptables -A FORWARD -i eth1 -p udp -m --multiport --dport 23073,23083 -j ACCEPT

and after run, shows no error msg. Thats mean it works but it wont
helps me to achive this what i want.

I repeat my msg here again:

In my network, Linux machine connect Local net (eth1) with internet
(ppp0). As a default all INCOMING traffic is deny. I made some rules
to access SMTP, HTTP etc. but its not important now.
It is necessery for nodes from local net to access server that is in Internet. The
address of this server is 62.233.202.165 and listen on port 23073 and
23083.

Rule: "iptables -A FORWARD -i eth1 -p udp -m --multiport --dport
23073,23083 -j ACCEPT"
wont helps and i have received msg in log like this:

Apr 30 02:28:41 slack kernel: IPT:UnhandledForward:IN=eth1 OUT=ppp0 SRC=192.168.1.2 DST=62.233.202.165 LEN=36 TOS=0x00 PREC=0x00 TTL=127 ID=23780 PROTO=UDP
SPT=1552 DPT=13073 LEN=16

Im newbe at iptables and cant resolve that problem alone. Maybe anyone
of You have got idea how to force that to work.


-- 
Best regards,
 mailto:netfilter_user@o2.pl



  reply	other threads:[~2003-04-30 13:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 22:49 access to server netfilter_user
2003-04-30  1:10 ` Arnt Karlsen
2003-04-30  1:38   ` Re[2]: " netfilter_user
2003-04-30  2:47     ` Arnt Karlsen
2003-04-30 13:32       ` netfilter_user [this message]
2003-04-30 14:59         ` Re[4]: " Alistair Tonner
2003-04-30 17:00           ` Re[6]: " netfilter_user
2003-04-30 17:48             ` Alistair Tonner

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=211627560.20030430153217@o2.pl \
    --to=netfilter_user@o2.pl \
    --cc=arnt@c2i.net \
    --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 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.