untangle for windows 6.2.1 alpha!

[sky-knight]

So what purpose that that chunk of code serve? Is it trying to find the network adapter that was created by virtual box? If so... which one? I don't see how knowing how many network adapters is on a system matters for this process.

Because, I don't get the process. But whatever the process is, linking it to a bit of text that is VERY COMMONLY changed by the user is simply bad form.

[dmorris]

Its trying to find an eligible network card to do the re-routing.

webfool, did it work for you after you changed that and installed?

[sky-knight]

Ok so it isn't looking for the virtual NIC, it's looking for the live lan interface for the host?

[dmorris]

yes.

[WebFooL]

After that i renamed one of mine interfaces the setup work fine.

Do you wish me to continue with the nsis script or is it a waste of time?

[sky-knight]

yes.

Ouch...

I think I'm with WebFool on this one, you need to allow the user to select the interface.

All it's going to take is one person to have a bluetooth or firewire adapter installed that happened to be "first".

This machine I'm talking to you on... if you grab the first adapter called "Local Area Network Connection"

That's the Firewire adapter... and it aint gonna work.

[WebFooL]

Here is a video on how i did it..
http://www.fakenews.se/untangle/rename.swf.html

I can think of two solutions.

One:
Change the setup script to List all posible choices and make the enduser choose.

Two: Insted of the "unable to detect an eligible network card." Have a message that say
"Can't find any "Local Area Connnection", If have rename or is running a non English version of xp pls rename your interface. And run the installera again."

[engine411]

*Host computer is not protected by Untangle running on it; only peer computers.

Is this just a temporary deficiency that will be changed in later, more mature alphas/betas, or will the host computer never be protected in any release of U4W 6.2?

[WebFooL]

Installation 2:

So today i moved my installation from my workstation to another host.
Here another problem came up.

Renameing the interface to "Local Area Connnection" workt and the installation whent thru. But when starting the Untangle i got some virtualboxheader.exe errors.
after some testing with newer virtualbox software and looking thru some error codes.
After a time i figured out that it is hard coded to use a usernamed "Administrator". (you give the password during the setup to this account) In my case the the default admin account is "Administratör" so after renaming it on this box and reinstallig it workt.

So to conclude.
Rename Interface to "Local Area Connnection"
Rename or create a user with name "Adminstrator" (has to be member of the admingroup)

[dmorris]

So to conclude.
Rename Interface to "Local Area Connnection"
Rename or create a user with name "Adminstrator" (has to be member of the admingroup)

Cool - thanks.

did it filter the network fine after this? (You can test by going to playboy.com after a few minutes if you installed web filter) - beware it only filters other machines.