Home » International » Russian » *SOLVED* shaping и veth
Re: shaping и veth [message #16245 is a reply to message #16237] |
Wed, 29 August 2007 15:04 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
![](http://new-forum.openvz.org/images/custom_avatars/1489.gif) |
sa10
Messages: 103 Registered: May 2007 Location: Minsk
|
Senior Member |
|
|
В конфиге стоят такие опции
grep CONFIG_NET_SCH /proc/config.gz
CONFIG_NET_SCHED=y
CONFIG_NET_SCH_CLK_JIFFIES=y
# CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set
# CONFIG_NET_SCH_CLK_CPU is not set
CONFIG_NET_SCH_CBQ=m
CONFIG_NET_SCH_HTB=m
CONFIG_NET_SCH_HFSC=m
CONFIG_NET_SCH_PRIO=m
CONFIG_NET_SCH_RED=m
CONFIG_NET_SCH_SFQ=m
CONFIG_NET_SCH_TEQL=m
CONFIG_NET_SCH_TBF=m
CONFIG_NET_SCH_GRED=m
CONFIG_NET_SCH_DSMARK=m
CONFIG_NET_SCH_NETEM=m
CONFIG_NET_SCH_INGRESS=m
И там стоит CONFIG_NET_SCH_CLK_JIFFIES=y
Можно поставить GETTIMEOFDAY=y для эксперимента, но на несущей машине ведь все работает без замечаний, проблема с управлением потока на виртуальном интерфейсе VE.
Я уже думаю над переносом фаервола на несущую машину, но это идеологически неправильно. Делать шейпинг на несущей машине, а фильтрацию пакетов на виртуальной тоже неразумно.
> 2. я еще не понял из вашего сообщения на каком интерфейсе настроен shaping... плюс какой scheduler?
Используются интерфейсы veth и scheduler HTB
На несущей машине интерфейсы выглядят так примерно (сори за большую портянку):
2: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
4: eth0: <BROADCAST,MULTICAST,SLAVE,UP,10000> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST,SLAVE,UP,10000> mtu 1500 qdisc pfifo_fast master bond0 qlen 1000
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
1: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/void
10: vlan5@bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
12: vlan36@bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
14: vlan111@bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
16: vlan222@bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
18: brdmz: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
20: brext: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
22: brint: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
inet 192.168.5.4/24 brd 192.168.5.255 scope global brint
24: brtorg: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:15:60:ab:61:b4 brd ff:ff:ff:ff:ff:ff
5: veth777.0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:18:51:fb:68:f8 brd ff:ff:ff:ff:ff:ff
7: veth777.1: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:18:51:39:93:e3 brd ff:ff:ff:ff:ff:ff
9: veth777.2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:18:51:73:a8:23 brd ff:ff:ff:ff:ff:ff
11: veth777.3: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:18:51:af:80:0d brd ff:ff:ff:ff:ff:ff
13: veth1001.0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:18:51:dd:be:bf brd ff:ff:ff:ff:ff:ff
15: veth221.0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:18:51:83:cd:79 brd ff:ff:ff:ff:ff:ff
________________________________
bridge name bridge id STP enabled interfaces
brdmz 8000.001560ab61b4 no vlan111
veth221.0
veth777.1
veth1001.0
brext 8000.001560ab61b4 no vlan36
veth777.2
brint 8000.001560ab61b4 no vlan5
veth777.0
brtorg 8000.001560ab61b4 no vlan222
veth777.3
--------------------
|
|
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
*SOLVED* shaping и veth
By: sa10 on Tue, 28 August 2007 12:58
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth
By: dev on Wed, 29 August 2007 13:40
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth
By: sa10 on Wed, 29 August 2007 15:04
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth
By: dev on Wed, 29 August 2007 15:20
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth
By: sa10 on Thu, 30 August 2007 10:03
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth
By: gblond on Thu, 30 August 2007 11:51
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth
By: sa10 on Thu, 30 August 2007 12:13
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth [SOLVED]
By: sa10 on Thu, 06 September 2007 15:19
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth [SOLVED]
By: sa10 on Wed, 12 September 2007 13:39
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth [SOLVED]
By: sa10 on Mon, 01 October 2007 14:22
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth [SOLVED]
By: gblond on Thu, 04 October 2007 06:16
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth [SOLVED]
By: sa10 on Thu, 04 October 2007 13:59
|
![Read Message Read Message](/theme/ovz3/images/read.png) |
|
Re: shaping и veth [SOLVED]
By: gblond on Fri, 05 October 2007 14:43
|
Goto Forum:
Current Time: Sat Aug 17 06:19:00 GMT 2024
Total time taken to generate the page: 0.02868 seconds
|