Elastix on OpenVZ, I cant to do the bridge [message #37869] |
Thu, 29 October 2009 01:49 |
Augustino
Messages: 9 Registered: October 2009
|
Junior Member |
|
|
hello
I want to install elaxtix on openvz, i found many handbooks, I also had internet in my container but currently, I dont have access to internet in the container but I have access in the father machine, the insternet is needed to install the repositories
I dont have internet in the container
I am making this
Wheres is the error?
brctl addbr br0
# ifconfig eth0 0
# brctl addif br0 eth0
# ifconfig br0 192.168.1.125 netmask 255.255.255.0
# ip route add default via 192.168.1.1 dev br0
# ifconfig eth0 192.168.1.105 netmask 255.255.255.0
# ifconfig venet0 192.168.1.125 netmask 255.255.255.0
# vzctl start 777
# vzctl set 777 --netif_add eth0 --save
# vzctl exec 777 ifconfig eth0 192.168.1.105 netmask 255.255.255.0
# brctl addif br0 veth777.0
# vzctl exec 777 ip route add default via 192.168.1.1 dev eth0
RTNETLINK answers: File exists
# vzctl enter 777
entered into VE 777
[root@test /]# ping google.com
ping: unknown host google.com
Best Regards
[Updated on: Thu, 29 October 2009 02:10] Report message to a moderator
|
|
|
|
Re: Elastix on OpenVZ, I cant to do the bridge [message #37903 is a reply to message #37896] |
Sat, 31 October 2009 03:27 |
Augustino
Messages: 9 Registered: October 2009
|
Junior Member |
|
|
Then Should I just do the following?
Install bridge-utils with apt-get
1.Create bridge device
2. Add veth devices to bridge
brctl addif vzbr0 veth777.0
3. Configure bridge device
ifconfig vzbr0 0
echo 1 > /proc/sys/net/ipv4/conf/vzbr0/forwarding
echo 1 > /proc/sys/net/ipv4/conf/vzbr0/proxy_arp
4. The new IP for the container?
ip route add 192.168.1.125 dev vzbr0
Thats all? Should I configure the iptables?
Is needed anymore?
This is needed? or not?
# vzctl set 777 --netif_add eth0 --save
# vzctl exec 777 ifconfig eth0 192.168.1.105 netmask 255.255.255.0
# brctl addif br0 veth777.0
# vzctl exec 777 ip route add default via 192.168.1.1 dev eth0
Best Regards
[Updated on: Sat, 31 October 2009 03:27] Report message to a moderator
|
|
|
|
|
|
|
|
Re: Elastix on OpenVZ, I cant to do the bridge [message #38219 is a reply to message #37869] |
Mon, 30 November 2009 04:20 |
mustardman
Messages: 91 Registered: October 2009
|
Member |
|
|
I have Elastix 1.6 running on an OpenVZ container. You should not have to do anything with networking as anything Elastix does with networking is overridden automatically. Not sure how OpenVZ or the container template do this but that's what happens. There are a few OpenVZ specific packages loaded in container templates and perhaps they are involved.
You can potentially mess up networking temporarily by trying to change networking settings inside the container via Elastix or command line but all you have to do is reboot and the networking changes will be undone by OpenVZ.
In my experience the 2 likely problems that occur with ALL Asterisk distributions are udev and/or iptables.
If you have access to the container command line via a console or through the Host try "iptables -F" which will clear any iptables entries in memory that may be blocking you. These settings will be reloaded next time you reboot but at least it gives you SSH access so you can modify the iptables config file.
You also need to do these 2 things on the Elastix container to fix udev.
nano +346 /etc/rc.d/rc.sysinit
#/sbin/udev
/sbin/MAKEDEV tty
/sbin/MAKEDEV pty
nano +5 /usr/sbin/safe_asterisk
#TTY=9
Here is a detailed procedure installing Asterisk/FreePBX from source where this info comes from.
http://www.powerpbx.org/Asterisk-FreePBX-on-an-OpenVZ-Virtuo zzo-Virtual-Private-Server-v1
This is assuming you have the container set up properly on the node in the first place. If you are in fact having networking problems I am pretty sure it has nothing to do with Elastix or the container and more to do with how how it is set up on the node.
[Updated on: Thu, 03 December 2009 02:02] Report message to a moderator
|
|
|