On Tue, 4 Apr 2006, Adam M. Towarnyckyj wrote:
I recently read on a prior post as well as the FAQ that
packets can be limited by mac address using the u32 filter. I attempted
this and, while all the commands went through with no errors, it is not
limiting at all. I'm attempting to li
On Tue, 24 Jan 2006, Carl Brewer wrote:
Alexey Toptygin wrote:
On Mon, 23 Jan 2006, Carl Brewer wrote:
hi maybe I am missign something but can't your just use this
ip r a default via 192.168.239.1 src 72.3.205.160
plus you might need this as well
ip r a 192.168.239.0/24 src 192.168.
On Mon, 23 Jan 2006, Carl Brewer wrote:
hi
maybe I am missign something but can't your just use this
ip r a default via 192.168.239.1 src 72.3.205.160
plus you might need this as well
ip r a 192.168.239.0/24 src 192.168.239.2
I just needed the first one, thankyou. That worked a treat.
Out
On Mon, 16 Jan 2006, Flemming Frandsen wrote:
Currently (pre-2.6.16) you can only attach a real traffic shaper to the
the output of a device, but why not allow a traffic shaper to be attached
to the input of a device, without any of the IMQ/IFB nonsense?
I think the problem is that attaching th
On Wed, 5 Oct 2005, Carl-Daniel Hailfinger wrote:
"secondary --- this address is not used when selecting the default source
address for outgoing packets. An IP address becomes secondary if another
address within the same prefix (network) already exists. The first address
within the prefix is p
On Tue, 4 Oct 2005, Carl-Daniel Hailfinger wrote:
OK, I found out that this is documented behaviour, although the hint is not
in the man page.
If it's not in the man page, then where is the below quote from?
"secondary --- this address is not used when selecting the default source
address fo
On Fri, 1 Jul 2005, Stephen Hemminger wrote:
LAN__
|
| eth0 (no IP)
_|
| | Linux Box (PC)|
| |_
On Wed, 25 May 2005, Robert Siemer wrote:
Second a "tc filter add" can get translated to a bunch of "low level"
filter rules. E.g. a human readable u32 filter ends up as 3 rules
forming a little hash table network.
Where is this documented? How should one interpret the multiple "low
level" en
The following (occuring on debian/testing with kernel-image-2.6.8-2-386 version
2.6.8-13 and iproute version 20041019-3) confuses me:
# tc qdisc add dev eth0 root handle 1: prio
# tc filter add dev eth0 parent 1: proto ip pref 1 handle 1 fw classid 1:2
# tc filter ls dev eth0
filter parent 1:
