All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: John Clark via Bridge <bridge@lists.linux-foundation.org>
Cc: John Clark <jeclark2006@aim.com>
Subject: Re: [Bridge] Split path for packets, and bridge configuration problem.
Date: Mon, 5 Aug 2019 08:32:32 -0700	[thread overview]
Message-ID: <20190805083232.202d0d47@hermes.lan> (raw)
In-Reply-To: <A23F6E83-0634-4BFA-AE82-DA947D3544CF@aim.com>

On Wed, 31 Jul 2019 11:55:37 -0700
John Clark via Bridge <bridge@lists.linux-foundation.org> wrote:

> I’m trying to configure a Linux system to bridge an ethernet link for packet ingress from a local network and combine that with a radio link for the reply packet egress.
> 
> I vaguely recall something like this use to be used for Satellite links, where the incoming packets from the outside world were via the Sat link, but outgoing packets were via a terrestrial link, phone modem or DSL, depending.
> 
> What I have working is the packet entering the bridge on the ethernet link, then I see the MAC address of the node from the in the ‘bridge show’ output, but even if I assign the MAC address to the ‘radio’ tap interface, I see both the ‘ethernet’ port as ‘master’, and the tap device as ‘self’, but no packets are sent to the tap device.
> 
> In the past I’ve just written user apps that basically implement tunnels and using collection of such apps and taps, gotten packets to where I need them to be.
> 
> I was trying to use more standard tools, and not write more custom code.
> 
> Thanks for any assistance.
> John Clark.
> 

Hacks like this are best done with netfilter.

      reply	other threads:[~2019-08-05 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-31 18:55 [Bridge] Split path for packets, and bridge configuration problem John Clark
2019-08-05 15:32 ` Stephen Hemminger [this message]

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=20190805083232.202d0d47@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=bridge@lists.linux-foundation.org \
    --cc=jeclark2006@aim.com \
    /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.