virtualbricks connect switch to local network
Posted 11-06-2012 at 01:29 AM by zhjim
Another post for me myself and eye so I don't forget how I did it.
Here are the steps to get a virtualbricks setup with a vde_switch to connect through your local computer to the lan/wan/inet. All under Debian wheezy while in late testing.
We need a "master switch", a tap device, a local nic with access to the wide world. Have all your other switches or vserver (within virtualbricks) connect to the "master switch".
Configure your tap device to have a routable ip (i did so to circumvine any problems that might arose from using unroutable ip's). I choose 1.0.0.1. Also have the tap device connect to the "master switch". After starting the tap device in virtualbricks you have to provide the root password. In my case the tap device did not get an ip during first start. Either just stop and start the device or use the cli (ip addr 1.0.0.1/24 dev tun_name).
Now get a root shell and setup the routing and natting.
That got me going.
One can also fiddle with the events in virtualbricks but I did not get a su command to go through. Got to go deeper here.
Here are the steps to get a virtualbricks setup with a vde_switch to connect through your local computer to the lan/wan/inet. All under Debian wheezy while in late testing.
We need a "master switch", a tap device, a local nic with access to the wide world. Have all your other switches or vserver (within virtualbricks) connect to the "master switch".
Configure your tap device to have a routable ip (i did so to circumvine any problems that might arose from using unroutable ip's). I choose 1.0.0.1. Also have the tap device connect to the "master switch". After starting the tap device in virtualbricks you have to provide the root password. In my case the tap device did not get an ip during first start. Either just stop and start the device or use the cli (ip addr 1.0.0.1/24 dev tun_name).
Now get a root shell and setup the routing and natting.
Code:
echo 1 > /proc/sys/net/ipv4/ip_forward iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
One can also fiddle with the events in virtualbricks but I did not get a su command to go through. Got to go deeper here.
Total Comments 0