OpenVZ Forum: Support » netdev_add kills wanpipe ??

Home » General » Support » netdev_add kills wanpipe ?? (cannot add sangoma wanpipe interface to CT)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

netdev_add kills wanpipe ?? [message #38220]

Mon, 30 November 2009 07:32

geejay
Messages: 11
Registered: May 2008

Junior Member

Hello,

I am trying to use a Sangoma A104D E1 port in a container giving the container exclusive access to the port. However when doing
vzctl set 220 --netdev_add w1g1 --save
vzctl set 220 --netdev_add w1g2 --save
the device is killed.

Before adding them with netdev the devices look as following:

w1g1 Link encap:Point-to-Point Protocol
UP POINTOPOINT NOARP MTU:4112 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:18 Memory:f8f20000-f8f21fff

w1g2 Link encap:Point-to-Point Protocol
UP POINTOPOINT NOARP MTU:1216 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:18 Memory:f8f20000-f8f21fff

The Sangoma API uses raw sockets. So I suppose this should work in OpenVZ similar to TUN/TAP devices. But I cant figure out how to do it.

Just to see whether it helps I added capabilities to the container
CAPABILITY="NET_ADMIN:on NET_RAW:on SYS_MODULE:on SYS_RAWIO:on "
unfortunately it doesnt.

Anyone any hints ?

I can give openvz developers access to the machine in case someone needs this.

Thank you for your help.

Geejay

Report message to a moderator

Re: netdev_add kills wanpipe ?? [message #38302 is a reply to message #38220]

Fri, 04 December 2009 17:36

maratrus
Messages: 1495
Registered: August 2007
Location: Moscow

Senior Member

Hello,

could you please specify what the phrase "the device is killed" means?
Was the device actually moved into the container?

Report message to a moderator

Re: netdev_add kills wanpipe ?? [message #38321 is a reply to message #38302]

Sun, 06 December 2009 11:15

geejay
Messages: 11
Registered: May 2008

Junior Member

"Killed" means: Before adding it to the container it is visible with ifconfig as a network interface and after adding it is is gone.

As far as I can see the task I envisaged is not possible because the device is accessed on the API level to the driver.

Of course I would love to be wrong on this.

Geejay

Report message to a moderator

Re: netdev_add kills wanpipe ?? [message #38419 is a reply to message #38321]

Fri, 18 December 2009 12:25

maratrus
Messages: 1495
Registered: August 2007
Location: Moscow

Senior Member

Hello,

sorry for delay

Quote:

"Killed" means: Before adding it to the container it is visible with ifconfig as a network interface and after adding it is is gone.

But this is exactly what netdev_dev is intended to do.
(man vzctl).

It is possible to create two types of network devices inside VE: venet and veth. The latter is created with help of "--netif_add" option. Moving network devices is also possible with help of "-netdev_add" option. Moving network device means moving it from the HN to VE.
http://wiki.openvz.org/Veth

Report message to a moderator

Previous Topic:	speed up container start with too many IPs
Next Topic:	Zimbra on OpenVz

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Feb 06 13:08:39 GMT 2026

Total time taken to generate the page: 1.15374 seconds