All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Feldmann <feldmann_markus@gmx.de>
To: netfilter@vger.kernel.org
Subject: Bad Argument `lo'
Date: Thu, 04 Oct 2012 21:14:29 +0200	[thread overview]
Message-ID: <506DE015.2090606@gmx.de> (raw)

Hi All,

i using iptables (version 1.4.14) on a LMDE(Debian like) with kernel 
3.5.3. Some days before i watched my logs after several weeks again. :-) 
And i spotted the error message:

Bad argument `lo'

So i searched at google to get a solution and i got one. Some user told 
to put the <lo> into ticks, like this

'!lo'

My iptables-rules regarding on this problem were looking so,

...
iptables -A INPUT -i ! lo -s 127.0.0.1 -j DROP
...

and i changed this line to,

...
iptables -A INPUT -i '!lo' -s 127.0.0.1 -j DROP
...

Now i am not sure, if this works correctly. <iptables -L> shows me the 
device "!lo",

######################################################################
Chain INPUT (policy DROP 0 packets, 0 bytes)
  pkts bytes target     prot opt in     out     source destination
     0     0 LOG        all  --  !lo    any     localhost anywhere 
        limit: avg 3/sec burst 5 LOG level warning prefix "Loopback 
gespooft: "
     0     0 DROP       all  --  !lo    any     localhost anywhere
######################################################################

but i am not sure if this works correctly. Does somebody knows if this 
trick works correctly?

regards Markus

             reply	other threads:[~2012-10-04 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 19:14 Markus Feldmann [this message]
2012-10-04 19:23 ` Bad Argument `lo' Eric Leblond
  -- strict thread matches above, loose matches on Subject: below --
2012-10-03 20:16 Markus Feldmann

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=506DE015.2090606@gmx.de \
    --to=feldmann_markus@gmx.de \
    --cc=netfilter@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.