Displaying 5 results from an estimated 5 matches for "8b0b".
Did you mean:
880b
2007 Aug 03
1
filter hashkey without match
Hi,
I need to set filter-hash and use source-port as hashkey. It seems that
I can''t use "hashkey" without using "match".
I am using following commands:
tc qdisc add ... root handle 1:0 htb
# Loop to add 1000 classes (i = 1 to 1000)
tc class add ... parent 1:0 classid 1:$i
#set filters
tc filter add ... protocol ip parent 1:0 u32
tc filter add ...
2007 Jun 26
3
network simulator
I want to build a "network simulator", to create scenarios such as
delayed packets, lost packets, low bandwidth, or combinations of such.
This document has been helpful for everything except the bandwidth:
http://linux-net.osdl.org/index.php/Netem
There is some documentation here regarding bandwidth:
http://luxik.cdi.cz/~devik/qos/htb/
What''s the best documentation to read
2007 Jun 19
4
Why does this script noet work (bandwidth, tc en u32)
Hi,
Can anyone point me out where the script below is wrong?
All I want is that host 172.31.1.1 can only use 10 megabit. If I run
this script on the in-between router nothing happens (the host uses
still the full 100 mbit, tested with iperf) , so i assume that something
must be wrong....
#!/bin/sh
# LAN1 NIC
tc qdisc del dev eth0 root
tc qdisc add dev eth0 root handle 1: htb
tc class add dev
2015 Apr 26
2
Route traffic through private IP for only certain hosts
...fe15:8b01/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000
link/ether 00:0c:29:15:8b:0b brd ff:ff:ff:ff:ff:ff
inet 10.0.64.150/24 brd 10.0.64.255 scope global eth1
inet6 fe80::20c:29ff:fe15:8b0b/64 scope link
valid_lft forever preferred_lft forever
</pre>
Here is an *ip route*
<pre>
# ip route
8.8.8.8 via 10.0.64.10 dev eth1
y.y.y.z/29 dev eth0 proto kernel scope link src y.y.y.y
10.0.64.0/24 dev eth1 proto kernel scope link src 10.0.64.150
default via y.y.y.a dev...
2007 Jul 02
8
Kernel Packet Traveling Diagram
Hi,
I find this diagram which details the kernel packet traveling :
http://www.docum.org/docum.org/kptd/
Is it up to date ?
I made some test and I put a DNAT rules in the PREROUTING table of an
interface and I attach it a ingress policy, the dst IP wasn''t changed. the
DNAT it isn''t yet make.
I''ve another question (I''m not sure is it the good mailing list), for