From: 0ndrej <0@amu.cz>
To: netfilter@lists.netfilter.org
Subject: rule to match next-hop
Date: Tue, 24 Dec 2002 10:50:43 +0100 [thread overview]
Message-ID: <3E082DF3.9050007@amu.cz> (raw)
Dear NetFilter Wizards,
We are building a volunteer network in Prague based on wireless
broadband technology (WiFi and our cheep FSO deviced - see
http://ronja.jikos.cz) - http://www.czfree.net and we would like to
limit bandwith between our routers, as the 'broadband' is not that broad
concerning WiFi....
Is there a way to match/clasify packets going via our meshed network to
a certain nex-hop router?
example
wlan0 wlan0 wlan1 wlan0 wlan1
<box a> --------- <box b> -------- <box c> --- ...
\------- <box d> --- ...
\------ <box e> --- ...
At <box b> we would like to mark packets going through interface wlan1
via boxes c,d,e with different marks, such that we could make fair
sharing of the available bandwith (QoS / HTB)
This means classifying packets based on their next-hop, but I couldnt
find any way how to do it. I hope I'm just stupid and it is possible, so
if anyone knows, please tell me :)
thanks, enjoy Xmass
0.
reply other threads:[~2002-12-24 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E082DF3.9050007@amu.cz \
--to=0@amu.cz \
--cc=netfilter@lists.netfilter.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.