Results 1 to 7 of 7

Thread: NIC problems

  1. #1
    Newbie
    Join Date
    May 2015
    Posts
    4

    Default NIC problems

    I have been trying to get Untangle working at one of our sites for 3 days now. My environment is VMware 5.1, and I started with the .ova VMware appliance v9.40 of Untangle. This was on day1. It was went great, until I ran patches from the console. This act killed the NIC drivers and it would not boot any longer.

    I started from scratch, this time with 11.10 .iso, built another vm with that. It has yet to work with the exteneral NIC (I learned on both, to just get through the wizard and mess with setting from "Config" tab).

    Since this is a rush job, my boss said to just get the unstable 9.40 working, and don't update it. We can circle back later.

    That all went well today, and I had shut it off yesterday before leaving work, fired it up this morning, and my test win7 box is still using it good as a gateway (bridge mode).

    However, after adding a static route today, and taking it down to make a backup of my work, the thing would _not_ get both NICs to work until I restarted it 6 times. With each restart, external NIC worked/internal not and vice versa until about the time I made an account here, it did get both NICs talking on the network.

    Also, I have installed both the appliance and .iso at least 3 times each. Due to the size of this post, I'll not get into all of the issues, but suffice it to say, I could never replicate the bridged mode in 11.10 that worked good in 9.40.

    My boss will most likely lose patience and has already told me to try another product yesterday.

    I cannot deploy this unstable server for our users.

    Specs:
    VMware 5.1
    E1000 NICs
    Cisco network
    Gave each box 8GB RAM and 2 CPUs. (they run great).

  2. #2
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,650

    Default

    I would start with the 10.0 .ova file and upgrade from there to 11.1.

    http://sourceforge.net/projects/unta...20%28Focus%29/
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  3. #3
    Newbie
    Join Date
    May 2015
    Posts
    4

    Default

    I did see the v10.0 .ova after I had already installed the v9.40. However, the problem I had when I did have 11.10 working properly on both NICs is that I could not replicate bridging the internal to the external as I have successfully done with the 9.40.

    All of that aside, today I simply cannot get 11.10 to work with the Vmware E1000 NIC.

  4. #4
    Untangle Ninja Jim.Alles's Avatar
    Join Date
    Jul 2008
    Location
    Central PA
    Posts
    2,469

    Default

    There were major re-writes behind the scenes from UT v9.4 of the networking framework. Don't start there. It bears repeating:

    I would start with the 10.0 .ova file and upgrade from there to 11.1.
    And, please don't take this as a criticism of your environment, and certainly not knocking NGFW, but a virtual environment probably is not optimal for it. The third party individuals who make it work and put those .ova packages together did so with a deep understanding of the NGFW package to begin with. A VM is not plug & play like the standard install. If you were able to dedicate hardware to NGFW, I think you would find the first install to be a much better experience and a quick & painless deployment. VM is not officially supported by Untangle.

    -- the perspective of a non-professional.

    P.S. search these forums for something like "virtual", you will find posts like this:
    http://forums.untangle.com/installation
    Last edited by Jim.Alles; 05-01-2015 at 11:20 AM.
    If you think I got Grumpy

  5. #5
    Newbie
    Join Date
    May 2015
    Posts
    4

    Default

    The very next thing I did after the .ova install barfed on updates, was to download and try the .iso of v11.10 to find that it, too, has issues with VMware NICs. The issue is a very basic one. The untangle distro has issues with broadly supported Vmware NICs and/or E1000. I run plenty of VM's --hundreds -- and many of them are Linux-based. I've never had issues with the NICs like this.

    We will not be provisioning real hardware for this single server.

    Forgetting all about the .ova, is there anyone out there successfully running the latest version of entangle with Vmware family 5?

  6. #6
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,650

    Default

    We do our nightly testing on an instance using VMware Server 5. At this point it might be best to open a support ticket so we can see the details of the VMware deployment.
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  7. #7
    Newbie
    Join Date
    May 2015
    Posts
    4

    Default

    **SOLVED**

    I have good news and hopefully helpful information for those who might also struggle with Untangle and VMware. First, let me state that it isn't just Untangle and its .iso. I experienced the same problem with pfSense .iso, latest version (2.2.2).

    The issue is indeed VMware and/or these 2 products (Untangle and pfSense). I got derailed into thinking it was driver based, and unfixable and on the .iso install. Once I started troubleshooting from the VMware side (after finding pfSense did the same thing) I was able to resolve in almost a stupidly simple way:

    When I lose network connectivity (and both installs would randomly lose ext/int NIC connectivity on boot, either just 1 NIC or both), I go to the VMware WUI (this is 5.5 VMware) and disconnect the NICs, "OK" that, then reconnect, "OK" that, and it works!

    The vm is left powered on, and goes from not being able to access the network, to suddenly working. I have repeated this fix.

    I only lost network on a power off/power on. Once the NICs are working I have not lost connection during that uptime.

    Also, I found that I had to do this from the VMware 5.5 WUI, since I would lose ability to disconnect/reconnect the NICs in the VMware thick client.

    So, I have Untangle working, in a VMware vm, blocking porn sites, and boss is happy!

    I also want to add that I've been using VMware for years, many iterations, and I have never experienced this problem before or this fix.

    tl;dr: just disconnect/reconnect the NICs when network connectivity gets lots on boot and make sure the vm is up when doing so.

    Environment:
    VMware 5.5 (at corporate office)
    VMware 5.1 (at the branch office where I needed to install a web content filter).
    Untangle: 11.1.0 from .iso

    **SOLVED**
    Last edited by morethanyogurt; 05-15-2015 at 09:10 AM.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2