Page 6 of 13 FirstFirst ... 45678 ... LastLast
Results 51 to 60 of 130
  1. #51
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,655

    Default

    Select the 3.16 kernel at boot as that is the same kernel as 13.2.1. I would start by diagnosing the DNS on the WAN. Can you ping the DNS server used in the WAN settings?

    Is this custom hardware? If so can you describe it?
    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

  2. #52
    Untanglit
    Join Date
    Dec 2016
    Posts
    15

    Default

    Quote Originally Posted by jcoffin View Post
    Select the 3.16 kernel at boot as that is the same kernel as 13.2.1. I would start by diagnosing the DNS on the WAN. Can you ping the DNS server used in the WAN settings?

    Is this custom hardware? If so can you describe it?
    Thx.

    If I boot into 3.16, I get this line "Linux untangle.xx.com 3.16.0-4-untangle-amd64 #1 SMP Debian 3.16.7-2untangle7 and eventually the Untangle admin screen. Network devices don't work (as described above).

    From recovery tools, I can ping the DNS server 208.67.220.220 and IPs on the LAN.

    From the GUI, I get errors that say the DNS server (208.67.220.220) fails to resolve

    The hardware is:

    Code:
     QOTOM Q190G4-S02
    
    Intel Celeron Processor J1900 (Quad-Core 2M Cache ,2 GHz, up to 2.41 GHz)
    4 Intel Gigabit LAN, VGA, 3x USB 2.0 ports, 1x USB 3.0 port
    Samsung 850 EVO - 250GB - mSATA Internal SSD (MZ-M5E250BW)
    Crucial 8GB Single DDR3L 1600 MT/s (PC3L-12800) SODIMM 204-Pin Laptop Memory (CT102464BF160B)
    Since I can ping WAN & LAN from recovery tools, but GUI can't access, it feels like something's up with the bridge in 14?

    I rebooted to the newer kernel and let it sit for several minutes and the untangle screen eventually came up. I configured a client to connect manually and it was able to connect to https://10.0.0.1 it is also able to ping 8.8.8.8, 1.1.1.1 and 208.67.220.220 so perhaps it's as simple as DNS/DHCP services not being available on the NGFW server?
    Last edited by Bollar; 06-19-2018 at 09:23 AM. Reason: More info...

  3. #53
    Untanglit
    Join Date
    Dec 2016
    Posts
    15

    Default

    SOLUTION:

    I have the following dnsmasq code
    Code:
    # NTP Server
    dhcp-option=42,10.30,0,10
    Removing it allows NGFW to function properly, but I'm unsure why this entry causes a problem in 14 and not 13.2.1. Any ideas?

  4. #54
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,655

    Default

    Probably changes in Debian 9 and systemd. I'll look into it. Thanks for the update.
    Bollar likes this.
    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

  5. #55
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,655

    Default

    dhcp-option=42,10.30,0,10 does not look valid since an IP address is expected after the 42 option.. Do you mean dhcp-option=42,10.30.0.10 ?
    Bollar likes this.
    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

  6. #56
    Untanglit
    Join Date
    Dec 2016
    Posts
    15

    Default

    Quote Originally Posted by jcoffin View Post
    dhcp-option=42,10.30,0,10 does not look valid since an IP address is expected after the 42 option.. Do you mean dhcp-option=42,10.30.0.10 ?
    That was a cut and paste from what was in the box. Either it's been wrong all along and didn't matter in 13.2.1, or it got corrupted at the upgrade. I suppose an older backup would answer the question?

  7. #57
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,655

    Default

    It could be that older dnsmasq ignores invalid syntax. Either way, it's not valid.

    Main reason for the warning in that window.
    Warning: Invalid syntax will halt all DHCP & DNS services
    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

  8. #58
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Lake Tahoe
    Posts
    9,655

    Default

    Looks like it was invalid before the upgrade. The reboot during the upgrade re-validated the DNSMasq options. If your original format was used, the same issue happens if 13.2 reboots.
    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

  9. #59
    Master Untangler
    Join Date
    Dec 2010
    Location
    Southfield, MI
    Posts
    181

    Default

    The 32-bit ISO doesn't fit on a CD (it's 729MB) but the 64-bit one does.

    Is it deliberate that the 32-bit version isn't offered on the home page anymore?

  10. #60
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,486

    Default

    Quote Originally Posted by yotefn View Post
    Is it deliberate that the 32-bit version isn't offered on the home page anymore?
    Yes, i386 support will be dropped upstream in the future.
    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

Page 6 of 13 FirstFirst ... 45678 ... LastLast

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