All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: netlabel: UNLABELED ath9k not denying unlabeled traffic
Date: Tue, 13 Jan 2009 21:18:18 -0800	[thread overview]
Message-ID: <496D759A.7010401@gmail.com> (raw)

When using netlabelctl on a dell laptop
I'm able to define the addresses that I want:

netlabelctl unlbl add interface:wlan0 address:<radiostation> 
label:system_u:object_r:netlabel_peer_t:s0
netlabelctl unlbl add interface:wlan0 address:<myaddress> 
label:system_u:object_r:netlabel_peer_t:s0
netlabelctl  -p unlbl accept off

{the above was from http://paulmoore.livejournal.com/1758.html };
(I'm able to listen to the radio station allowed, then if I choose 
another station; if I haven't defined an address like the above, mplayer 
just sits there.denying the unlabeled packet. that is until I allow the 
address);

The problem I have is when I do the same on my macbook pro ati chipset.
with the ath9k module, I'm able to listen to any station, search the web 
etc..
it seems netlabelctl  -p unlbl accept off makes no difference if it's on 
or off.
 
Is this built into ath9k yet, or is there something I'm missing?

regards;

Justin P. Mattock


             reply	other threads:[~2009-01-14  5:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  5:18 Justin P. Mattock [this message]
2009-01-14 14:57 ` netlabel: UNLABELED ath9k not denying unlabeled traffic Paul Moore
2009-01-14 16:15   ` Justin P. Mattock
2009-01-14 16:15     ` Justin P. Mattock
2009-01-14 17:05     ` Paul Moore
2009-01-14 17:05       ` Paul Moore
2009-01-14 17:24       ` Stephen Smalley
2009-01-14 17:43         ` Paul Moore
2009-01-18 16:17           ` Eric Paris
2009-01-18 19:37             ` Justin P. Mattock
2009-01-14 17:32       ` Justin P. Mattock
2009-01-14 17:32         ` Justin P. Mattock
2009-01-14 20:04         ` Paul Moore
2009-01-14 20:04           ` Paul Moore
2009-01-14 20:08           ` Paul Moore
2009-01-14 20:08             ` Paul Moore
2009-01-14 21:35             ` Justin P. Mattock
2009-01-14 21:35               ` Justin P. Mattock
2009-01-14 22:36               ` Paul Moore
2009-01-14 22:36                 ` Paul Moore
2009-01-15  1:54                 ` Justin P. Mattock
2009-01-15  1:54                   ` Justin P. Mattock
2009-01-15 17:45                   ` Paul Moore
2009-01-15 17:45                     ` Paul Moore
2009-01-15  2:43                 ` Justin P. Mattock
2009-01-15  2:43                   ` Justin P. Mattock
2009-01-15 17:46                   ` Paul Moore
2009-01-15 17:46                     ` Paul Moore
2009-01-15 22:00                     ` Justin Mattock
2009-01-15 22:00                       ` Justin Mattock
2009-01-15 22:52                       ` Paul Moore
2009-01-15 22:52                         ` Paul Moore
2009-01-16  0:44                         ` Justin Mattock
2009-01-16  0:44                           ` Justin Mattock
2009-01-16 16:09                           ` Paul Moore
2009-01-16 16:09                             ` Paul Moore
2009-01-16 17:18                             ` Justin P. Mattock
2009-01-16 17:18                               ` Justin P. Mattock

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=496D759A.7010401@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-kernel@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.