Website Browsing / Proxy Issues

Comments

4 comments

  • Avatar
    Firewalla

    When the problems happen, is it possible to do some basic testing? 

    • ping fire.walla
    • ping 1.1.1.1
    • nslookup firewalla.com

    and see which one fails. This may point to the ISP/cloud issue.

    Also, turn off adblocker and DoH and see if the problems go away. (I assume some part of your symantec cloud also goes local)

     

    0
    Comment actions Permalink
  • Avatar
    parsoli

    cannot ping 'fire.walla' but can ping firewalla which resolves/responds

    can ping 1.1.1.1 successfully

    NSLookups work as expected.

    This may be an issue with a corporate web proxy that hijacks the browser via a .pac file that redirects to an SSL loopback that pushes 80/443 queries to BlueCoat.  Still investigating.

    0
    Comment actions Permalink
  • Avatar
    parsoli

    Just had it occur again.

     

    PS C:\Users\xxxx> ping firewalla

    Pinging firewalla.local [192.168.1.1] with 32 bytes of data:
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

    Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms
    PS C:\Users\xxxx> ping 1.1.1.1

    Pinging 1.1.1.1 with 32 bytes of data:
    Reply from 1.1.1.1: bytes=32 time=15ms TTL=58
    Reply from 1.1.1.1: bytes=32 time=15ms TTL=58

    Ping statistics for 1.1.1.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 15ms, Maximum = 15ms, Average = 15ms
    Control-C
    PS C:\Users\xxxx> nslookup
    Default Server: firewalla.inc.lan
    Address: 192.168.1.1

    > firewalla
    Server: firewalla.inc.lan
    Address: 192.168.1.1

    *** firewalla.inc.lan can't find firewalla: Non-existent domain
    > firewalla
    Server: firewalla.inc.lan
    Address: 192.168.1.1

    *** firewalla.inc.lan can't find firewalla: Non-existent domain
    > firewalla.com
    Server: firewalla.inc.lan
    Address: 192.168.1.1

    Non-authoritative answer:
    Name: firewalla.com
    Address: 23.227.38.32

    0
    Comment actions Permalink
  • Avatar
    Firewalla

    The results are all good ... next time, can you try to change the device having issue to emergency access on? (tap on devices->tap on device->turn on emergency access) see if this solves the issue

    0
    Comment actions Permalink

Please sign in to leave a comment.