• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Interface filtering
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interface filtering


  • Subject: Re: Interface filtering
  • From: Justin Walker <email@hidden>
  • Date: Tue, 12 Apr 2005 10:54:21 -0700


On Apr 12, 2005, at 6:26, Carl Smith wrote:


" Since you are using an interface filter, then the packets you get from


a specific interface are either all from a wireless connection, or none
are.  Perhaps I am missing the point of your question."

Well you could have a situation where the machine is both wired, DSL
cable or something, and unwired, having a wireless nic card installed,
so in my case there is a en0 and a en1. So if I only wanted to intercept
the packets from the wireless card, I was wondering if there was some
way I could do that. But it sounds like maybe not.

Each packet will come from its originating interface, and you can distinguish that way. You will have to dig further to find out how to identify wireless interfaces. I'm sure that, if the driver knows and publishes the fact, you can find it out (I just don't know the way to do that).


Regards,

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for General Semantics
--------
It's not whether you win or lose...
It's whether *I* win or lose.
--------

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >RE: Interface filtering (From: "Carl Smith" <email@hidden>)

  • Prev by Date: RE: Interface filtering
  • Next by Date: Kernel stack size
  • Previous by thread: RE: Interface filtering
  • Next by thread: Kernel stack size
  • Index(es):
    • Date
    • Thread