At my testing server - now works fine also ebox-networking. So its possible to get ebox work with one command: sudo apt-get install ebox-all
But I have suggestions - I dont know is this network or firewall module problems. Maybe both. I am using separated PC for testing, what is connected with KVM switch. Mostly I am setting up test distribution and the I operate with SSH. What I find ( I test that three times - every time fresh installation). When I give drought SSH command sudo apt-get install ebox-all, then after setting up ebox-network and ebox-firewall - I am loosing connection. And I am not able to connect any more. Here ist stops: Adding new user `ebox' (UID 105) with group `ebox' ... The home directory `/var/lib/ebox/' already exists. Not copying from `/etc/skel'. adduser: Warning: that home directory does not belong to the user you are currently creating. Adding user `ebox' to group `adm' ... Done. Creating the eboxlogs database EBox: start sysinfo: [ OK ] EBox: start global: [ OK ] EBox: start logs: [ OK ] Setting up ebox-objects (0.9.3-0ubuntu4) ... EBox: restart objects: [ OK ] Setting up vlan (1.9-2build1) ... Setting up libnet-arp-perl (1.0-1) ... Setting up ebox-network (0.9.3-0ubuntu3) ... Use of uninitialized value in numeric ne (!=) at /usr/share/perl5/EBox/Network.pm line 805. EBox: restart network: [ OK ] Setting up ebox-firewall (0.9.3-0ubuntu3) ... Also is impossible to use any more apt-get ( its not finding servers). Its seems, like firewall has open only HTTPS port and there is no possibility to connect with SSH and also use other functions. I think that this is wrong, that after installing ebox is not possible to use apt-get and its not possible to use after that SSH. -- ebox-network fails to configure https://bugs.launchpad.net/bugs/127745 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
