Linux-WPAN Archive on lore.kernel.org
 help / color / Atom feed
From: Alexander Aring <alex.aring@gmail.com>
To: Victhor Foster <victhor.foster@ufpe.br>
Cc: linux-wpan <linux-wpan@vger.kernel.org>
Subject: Re: Interfacing mac802154 stack with userspace applications
Date: Fri, 13 Mar 2020 09:54:23 -0400
Message-ID: <20200313135423.zwimsw5u2o7dnanc@ryzen> (raw)
In-Reply-To: <763926392.1016039.1583799908366.JavaMail.zimbra@ufpe.br>

Hi,

On Mon, Mar 09, 2020 at 09:25:08PM -0300, Victhor Foster wrote:
> I have resumed work on this project, and I decided to implement a few
> changes. I abandoned the socat approach and came up with a different
> implementation, modifying the linux-wpan example programs.
> 

aha, which one?

> I made two programs, one that receives packets from a wpan interface
> and outputs them to a UDP port, while the other program receives
> packets from a UDP port and sends them to a wpan interface. It seems
> to work well enough, but there's a problem with my approach.
> 

You telling me something about UDP to a wpan interface. This makes no
sense except you also building some IP layer in user space.

> I need to get outgoing packets from the wpan interface. Is there a way
> to filter packets coming through a raw socket, such that only outgoing
> packets come out of the socket?
> 

Now you saying something about RAW sockets, what kind of raw sockets?

> Right now, I'm not filtering for outgoing packets, so when packets are
> received through my program and sent to the wpan interface, the same
> packets come out of the interface, as there's no filtering being done,
> causing a loop.
> 
> I tried using the sll_pkttype field in the raw socket structure, but
> all packets received by the socket have the same value, so it's not
> useful, unfortunately.
> 

No, it smells for me you want to do something with traffic control and
egress path.

- Alex

  reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 22:20 Victhor Foster
2019-11-06 14:02 ` Alexander Aring
2019-11-12  9:03   ` Victhor Foster
2020-03-10  0:25     ` Victhor Foster
2020-03-13 13:54       ` Alexander Aring [this message]
2020-03-13 22:21         ` Victhor Foster

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=20200313135423.zwimsw5u2o7dnanc@ryzen \
    --to=alex.aring@gmail.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=victhor.foster@ufpe.br \
    /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

Linux-WPAN Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-wpan/0 linux-wpan/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-wpan linux-wpan/ https://lore.kernel.org/linux-wpan \
		linux-wpan@vger.kernel.org
	public-inbox-index linux-wpan

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-wpan


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git