Page 6 of 8 FirstFirst ... 45678 LastLast
Results 51 to 60 of 77
  1. #51
    Untanglit bacquaviva's Avatar
    Join Date
    Sep 2009
    Location
    California
    Posts
    19

    Default

    I have this problem too. At first i thought it was only on fresh v14 installs, but can confirm 13->14 upgrades also have the problem.
    pntz likes this.

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

    Default

    Open a support case as we have yet to find an issue with v14.
    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. #53
    Untanglit bacquaviva's Avatar
    Join Date
    Sep 2009
    Location
    California
    Posts
    19

    Default

    I did yesterday and built a duplicate testing network so that support can look at it without impacting any of my clients.
    pntz likes this.

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

    Default

    Awesome, thanks for getting the environment setup.
    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
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    Quote Originally Posted by bacquaviva View Post
    I did yesterday and built a duplicate testing network so that support can look at it without impacting any of my clients.
    Thanks.

    Responding here so we can shortcut the support queue.

    #1, can you start a ping 4.2.2.1 (or something) from behind vlan 10 internal so we can see traffic trying to reach the internet?
    #2, vlan 10 internal is bridge to vlan 10 external, and there is a source route in wan balancer which is correct. However, the gateway for vlan 10 external is 10.1.1.1 does not respond, so that "WAN" is offline. You need to figure out why 10.1.1.1 is not responding to ARP requests. They are being sent.

    on the wire (with the propert 802.1q tag)

    [root @ untangle] ~ # tcpdump -e -i eth0 -n "arp"
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
    10:36:36.077730 0c:c4:7a:48:5b:71 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:37.110834 0c:c4:7a:48:5b:71 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:38.134861 0c:c4:7a:48:5b:71 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:39.159024 0c:c4:7a:48:5b:71 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:40.182833 0c:c4:7a:48:5b:71 > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 46: vlan 10, p 0, ethertype ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    from eth0.10 interface itself:

    [root @ untangle] ~ # tcpdump -e -i eth0 -n "arp"
    [root @ untangle] ~ # tcpdump -i eth0.10 -n "arp"
    tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
    listening on eth0.10, link-type EN10MB (Ethernet), capture size 262144 bytes
    10:36:18.101660 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:19.126827 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:20.150828 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:21.175000 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:22.198832 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    10:36:23.222851 ARP, Request who-has 10.1.1.1 tell 10.1.1.2, length 28
    Until the gateway is reachable that WAN is going to be offline...
    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 bacquaviva's Avatar
    Join Date
    Sep 2009
    Location
    California
    Posts
    19

    Default

    Apologies, I did not have the 10.1.1.1/vlan10 interface on the SonicWALL setup as pingable. It was late when I set it up.

    Beyond that, I have my laptop doing a persistent ping to 8.8.8.8 and 10.1.1.1. Everything is 100% rock solid if the SonicWALL is plugged directly into the switch. The second I put Untangle between them, is when vlan traffic dies. Likewise, the client I upgraded this weekend to 14 had been running as a vlan network since v10 without issue. Died the second 14 booted after upgrading.

    When I first ran into this, I assumed it was something broken in 14 because of the transparent bridge setting being ignored during setup (it would assign an ip and not bridge the internal network).

  7. #57
    Untanglit tizigman's Avatar
    Join Date
    Dec 2010
    Location
    Santa Barbara
    Posts
    19

    Default

    Support is still working on this. They have remote access and have been working on it for a week and no solution found yet.

  8. #58
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    Quote Originally Posted by bacquaviva View Post
    Apologies, I did not have the 10.1.1.1/vlan10 interface on the SonicWALL setup as pingable. It was late when I set it up.

    Beyond that, I have my laptop doing a persistent ping to 8.8.8.8 and 10.1.1.1. Everything is 100% rock solid if the SonicWALL is plugged directly into the switch. The second I put Untangle between them, is when vlan traffic dies. Likewise, the client I upgraded this weekend to 14 had been running as a vlan network since v10 without issue. Died the second 14 booted after upgrading.

    When I first ran into this, I assumed it was something broken in 14 because of the transparent bridge setting being ignored during setup (it would assign an ip and not bridge the internal network).
    Its not that it isn't answering ping, its that it isn't answering ARP. ping is a good test though because if ping works, that means ARP is also working. Have you configured your switch such that Untangle (10.1.1.2) can ping (10.1.1.1) ?

    edit: Its still not getting ARP replies. Untangle must be able to reach the gateway...
    Last edited by dmorris; 08-14-2018 at 06:44 PM.
    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
    Untanglit
    Join Date
    Feb 2018
    Posts
    21

    Default

    Quote Originally Posted by tizigman View Post
    Support is still working on this. They have remote access and have been working on it for a week and no solution found yet.
    JCoffin stated earlier that Untangle support had no open cases on the VLAN issue in v14 (transparent bridged mode). It seems quite a few of us have been patiently awaiting a fix that support is supposedly working on with tizigman. V14 did in fact break the 802.1q VLANs that worked perfectly fine in v13.2.1. The v14 push clearly seems to be the culprit.

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

    Default

    No, he said we don't have any cases that we have found an issue with v14. And further he said we haven't been able to replicate anything, which we havent. In other words, we haven't found a test case that does not behave as expected.

    If you have an issue, contact us.
    Until we find a setup that is not working as expected then there isn't anything to resolve.
    All cases thus far are not working for very real configuration reasons.

    (One guy didn't have WAN Balancer, another doesn't have a reachable gateway, another guy uninstalled)

    If you can't contact us, don't worry. If the issue is real someone will contact us eventually and we can troubleshoot the issue and figure out whats going on.
    Last edited by dmorris; 08-14-2018 at 08:21 PM.
    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 8 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