In order to change from a appliance machine to a gateway machine, the playbook and ansible will need to rewrite the iptables, and get the ports right so that dansguardian properly filters content that comes from the internet.
I doubt very much that all this would work, without running "./runansible" again. When I was loading 0.5 on a x86-64, the adapters were not discovered properly. The quickest way to discover this, for me, is to type iptables-save in a root terminal. Look at the masquerade line. The output -o needs to be the wan adapter, and the -i the lan. I'm not understanding why you would want to change appliance -> gateway without running ansible? On Mon, Dec 30, 2013 at 8:18 PM, Curt Thompson <curtathomp...@gmail.com>wrote: > Just to recap for server-devel@lists.laptop.org, > > In virtualbox using XFCE and installing XSCE 0.5, a problem appeared with > idmgr when doing ./runansible > ->the solution was to first run "yum -y update audit" and then rerun > ./runansible. After this, XSCE seemed to be working normally with the > exception of the IIAB link being active despite no IIAB device attached. > > New Info: > Setting the network adapter in Virtualbox to "bridged" made XSCE > accessible from other devices on the LAN. Rerunning ./runansible was not > necessary (previously the adapter was in "NAT"mode). "Appliance mode' > seems to work quite smoothly and is easy to set up, in VirtualBox at least > (will try on physical hardware later tonight). > > I had previously disabled SELinux, reenabled it to see if disabling it was > necessary. Many errors pop up when SELinux is enabled. Set it back to > "disabled" > > I enabled a second network adapter and booted up to see what would > happen. Everything seems to work locally, portal is still accessible from > other machines on the host's network. > > Next question: > However, XSCE does not seem to be acting as a server/gateway. Would the > best solution be to rerun ./runansible now that two network adapters are > connected? My understanding is that ./runansible will detect that there > are two available adapters, one of which is an internet gateway, and set > itself up in gateway mode. Is that about right? Would it be easy enough > to do without rerunning ./runansible? (Just get dhcpd going, for example?) > > ((I'm sort of imagining a real-world scenario where we got XSCE installed > with one network adapter, then internet was cut off, then someone came > through with a second USB network adapter - some scenario like that. Could > we get it going so that the machien would work as a router/gateway when > internet came back... easily?)) > > > > > > On 12/30/2013 4:29 PM, Anna wrote: > > As far as accessing it from other machines on your LAN, I've had success > with configuring the VM's network for Bridged mode and specifying the host > machine's adapter. Can't remember if I needed to rerun ./runansible, but > it seems like I didn't have to (though it wouldn't hurt anything). > > I also can't remember if I needed to disable SELinux on the host machine > or not. Sorry, I just got back home after a week with the family and my > head's not quite back in the game yet. > > > On Mon, Dec 30, 2013 at 6:20 PM, Adam Holt <h...@laptop.org> wrote: > >> Curt, >> >> Can you share your conclusions more publicly on >> server-devel@lists.laptop.org or >> http://wiki.laptop.org/go/XS_Community_Edition or similar? >> >> >> On Mon, Dec 30, 2013 at 7:11 PM, Curt Thompson >> <curtathomp...@gmail.com>wrote: >> >>> Anna, George, Tim, Braddock, >>> >>> Thank you, ansible finished without issue after "yum update audit", >>> rebooted, and I seem to have XSCE 0.5 running in appliance mode - quite >>> easy. >>> >>> URLs "schoolserver" and local IP "10.0.2.15" bring up portal as expected. >>> >>> semi-bug? >>> Internet In A Box link appears active and is clickable though no IIAB >>> device is attached. >>> >>> Next: >>> What would I need to do to convert this into a Gateway-style install of >>> XSCE? I could enable another adapter in VirtualBox and rerun ansible, but >>> the install documentation seems to hint that rerunning ansible may not be >>> necessary. >>> >>> >>> >>> On 12/30/2013 3:28 PM, Anna wrote: >>> > Oh, you're right, Braddock, Miguel resolved that with pr/103: >>> https://github.com/XSCE/xsce/pull/103 >>> > >>> > So updating the audit package on FC18 should be the only workaround >>> for a successful install, now. >>> > >>> > >>> > On Mon, Dec 30, 2013 at 5:22 PM, Braddock <bradd...@braddock.com >>> <mailto:bradd...@braddock.com> <bradd...@braddock.com>> wrote: >>> > >>> >>> On 12/30/2013 03:20 PM, Anna wrote: >>> > I've used that ISO and for idmgr had to do: >>> >>> > yum update audit >>> >>> > Then there's a conflict with IIAB (which is currently being >>> > addressed, I believe) but in the meantime, the workaround is: >>> >>> What is the conflict, and am I the one addressing it? I don't recall >>> it off hand. >>> >>> -braddock >>> >>> > On Mon, Dec 30, 2013 at 5:11 PM, Curt Thompson >>> > <curtathomp...@gmail.com >>> <mailto:curtathomp...@gmail.com><curtathomp...@gmail.com>< >>> mailto:curtathomp...@gmail.com <curtathomp...@gmail.com> >>> <mailto:curtathomp...@gmail.com> <curtathomp...@gmail.com>>> wrote: >>> >>> > I started with XFCE, the ISO file is named: >>> > Fedora-18-x86_64-Live-XFCE.iso >>> >>> > Installed through the GUI without customization except what the >>> > installer asks for (location, username, pass, etc). >>> >>> > On 12/30/2013 3:07 PM, Tim Moody wrote: >>> >> what do you start with as a blank FC18 before installing xsce? >>> >> I start with a minimal install. >>> >> >>> >> Tim -----Original Message----- From: Curt Thompson Sent: Monday, >>> >> December 30, 2013 5:52 PM To: xsce-de...@googlegroups.com >>> <mailto:xsce-de...@googlegroups.com> <xsce-de...@googlegroups.com> >>> >> <mailto:xsce-de...@googlegroups.com <xsce-de...@googlegroups.com> >>> <mailto:xsce-de...@googlegroups.com> <xsce-de...@googlegroups.com>> >>> Subject: [XSCE] XSCE 0.5 >>> >>> >> >>> >> Hi everyone, >>> >> >>> >> I've been trying to get XSCE 0.5 running in a VirtualBox VM for a >>> >> few days now, but without much success. Since there don't seem >>> >> to be instructions for x86_64 machines yet, I just followed the >>> >> instructions for XOs and hoped to fix whatever problems arise. >>> >> Perhaps we should start with this: >>> >> >>> >> TASK: [idmgr | Install idmgr packages] fails. Summarized as: >>> >> "file /usr/lib64/audit from install of glibc-2.16-34.fc18x86_64 >>> >> conflicts with file from package audit-2.2.1-2.fc18.x86_64" >>> >> >>> >> Under PLAY RECAP, I see ok-67, changed=10, unreachable=0, >>> >> failed=1 >>> >> >>> >> This VM has one network adapter, ideally I'd be installing it as >>> >> an appliance first to test out, then either changing the current >>> >> installation to the gateway install or reinstalling from scratch >>> >> with XSCE 0.5 in gateway mode (former method preferable) >>> >> >>> >> I did try to reboot to see if XSCE would work, the VM just grabs >>> >> the same DHCP address from the gateway here (10.0.2.15). Typing >>> >> "schoolserver" or <local ip address> brings me to Fedora/Apache >>> >> Test Page. >>> >> >>> >> I have some familiarity with linux, but I'm no superstar. If >>> >> anybody would like to help me get this XSCE 0.5 VM going please >>> >> let me know, send me some advice, or point me to some >>> >> documentation if I've >>> > missed it. >>> >> >>> >> Thanks Curt >>> >>> >>> >>> > >>> > >>> >>> -- >>> Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! >>> >> > >
_______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel