On 3/25/12 12:14 PM, "Johannes Graumann" <[email protected]> wrote:
>Hello, > >I'm migrating my laptop setup to a shiny new ThnikPad W520 and in the >process am getting rid of VirtualBox (marked by kernel maintainers as >"unsupportable crap" or some such) and shifting to virt-manager/kvm. > >As with the old setup I am running shorewall-init exactly as the great >online documentation lays it out. BUT: with VBox it was enough to add >> net vboxnet0 detect >>dhcp,tcpflags,nosmurfs,logmartians >to shorewall/interfaces and everything seemed to work. >Not so easy with the vit-man/kvm setup, where >> net virbr0 detect >>dhcp,tcpflags,nosmurfs,logmartians >does not seem to lead to a network-setup that works out - no network >connection from the (migrated) virtual machine. > >Any pointers on how to marry network-manager managed optional eth0 and >wlan0 >to a NATing virbr0 setup? > >Thanks for any help. Not sending conf files as I am truly following th >online doc (on debian testing). Unfortunatelyn for you, I've adopted LXC as my virtualization solution. And that runs on a system that gets rebooted 3 or 4 times a year, and does not run Shorewall-init. -Tom You do not need a parachute to skydive. You only need a parachute to skydive twice. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
