From: "John Guntenaar" <john@guntenaar.nl>
To: 'Joel Newkirk' <netfilter@newkirk.us>
Cc: netfilter@lists.netfilter.org
Subject: RE: per user IP adresses
Date: Tue, 6 May 2003 10:37:23 +0200 [thread overview]
Message-ID: <000201c313aa$bb09b710$0200a8c0@WKSJOHN> (raw)
In-Reply-To: <1052178384.32510.67.camel@alpha.newkirk.us>
Hi Joel,
Your LAN construction is exactly what I want, but I want that 1 of the 4
IPs can only bind to the 4th IP, but when I try any of your rules I get
errors :(
(And yes, I changed the real IP in 123.123.123.123 in here ;-))
jimbo:/var/www# iptables -A OUTPUT -p tcp -s 123.123.123.123/32 -m owner
! --uid-owner 1000 -j REJECT --reject-with tcp-reset
iptables: Invalid argument
jimbo:/var/www# iptables -A OUTPUT -p tcp --dport 6667 -m owner !
--uid-owner 1000 -j REJECT --reject-with tcp-reset
iptables: Invalid argument
jimbo:/var/www# iptables -A OUTPUT -p tcp --dport 194 -m owner !
--uid-owner \ 1235 -j REJECT --reject-with tcp-reset
iptables: Invalid argument
So what could be wrong?
Thanks,
John
-----Oorspronkelijk bericht-----
Van: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] Namens Joel Newkirk
Verzonden: dinsdag 6 mei 2003 1:46
Aan: john@guntenaar.nl
CC: netfilter@lists.netfilter.org
Onderwerp: Re: per user IP adresses
On Sun, 2003-05-04 at 14:38, John Guntenaar wrote:
I missed the start of this thread, so I backed up and reread it. :^)
> Hello,
>
> I have a linux machine with 4 IP addresses, I have a couple of friends
> on that machine and I don't allow them to use IRC, so I simply blocked
> the IRC ports, but I want to use IRC from the 4th IP without the other
> users being able to use it. I think I can reach that goal by using the
> owner match facility of iptables, though I can't find any good
examples
> with google, is it correct and can somebody post an example?
>
> Thanks in advantage,
>
> John
You need something constructed like this:
iptables -A OUTPUT -p tcp --dport 194 -m owner ! --uid-owner \ 1235 -j
REJECT --reject-with tcp-reset
or:
iptables -A OUTPUT -p tcp --dport 194 -m owner --uid-owner \ 1235 -j
ACCEPT
I use a similar rule to prevent any user except root from being able to
connect to my LAN computers from my server. You can add an additional
match to either rule to match outgoing interface or sourceIP if needed.
Is it really necessary to restrict IRC to only that single IP?
j
next prev parent reply other threads:[~2003-05-06 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 18:38 per user IP adresses John Guntenaar
2003-05-04 19:19 ` SaVaGE
2003-05-04 19:18 ` John Guntenaar
2003-05-06 9:48 ` Chris Wilson
2003-05-05 23:46 ` Joel Newkirk
2003-05-06 8:37 ` John Guntenaar [this message]
2003-05-06 13:16 ` Joel Newkirk
-- strict thread matches above, loose matches on Subject: below --
2003-05-05 0:09 Khanh Tran
2003-05-05 8:30 ` John Guntenaar
2003-05-05 12:09 ` Arnt Karlsen
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='000201c313aa$bb09b710$0200a8c0@WKSJOHN' \
--to=john@guntenaar.nl \
--cc=netfilter@lists.netfilter.org \
--cc=netfilter@newkirk.us \
/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