Stories
Slash Boxes
Comments

Dev.SN ♥ developers

This discussion has been archived. No new comments can be posted.
Should we have an IRC network of our own? | Log In/Create an Account | Top | 1000 moderator points   | 91 comments | Search Discussion
Display Options Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 1) by bryan on Tuesday March 11 2014, @07:07PM

    by bryan (29) <bryan@pipedot.org> on Tuesday March 11 2014, @07:07PM (#14927) Homepage Journal

    Also, the fortigate at work is blocking pipedot.org

    Both sites are using Linode; odd that any access would be different. Maybe try HTTPS instead of HTTP?

  • (Score: 3, Insightful) by Jaruzel on Wednesday March 12 2014, @05:00AM

    by Jaruzel (812) on Wednesday March 12 2014, @05:00AM (#15117) Homepage Journal

    Corporate proxys/firewalls such as Fortigate tend to block based on blacklists either provided by the supplier and/or maintained internally. As pipedot.org (and SN.org) is a tech news site, you should be able to ask your IT people to unblock it. It's possible that pipedot.org hasn't be classified yet, so is blocked by default (some places do that).

    -Jar

    --
    Wash at 40°C, and hand dry only. My MUD Engine [jaruzel.com]

    • (Score: 2, Informative) by francois on Wednesday March 12 2014, @02:26PM

      by francois (3010) on Wednesday March 12 2014, @02:26PM (#15429)

      Having your own IRC service is absolutely not a guarantee that it won't be blocked by corporate filtering.

      Today, dev.soylentnews.org is seen as Information Technology so will probably never be blocked by most filtering policies.
      The web chat (chat.sylnt.org) is uncategorized. Most companies (if not all, in some regions) tend to BLOCK when it's uncategorized.
      CISO feels safer, as users will not go to the uncategorized Internet. Support/admins cry, as they have to micro manage all the exceptions for the end users.

      Of course, asking your BOFH to open a site for you might not be a good idea so the best way to make sure it's not blocked is to ask to the vendors. Most of them allow this, either via a web page or through an email.
      Fortinet : http://docs-legacy.fortinet.com/cb/html/index.html #page/FOS_Cookbook/UTM/cb_utm_wf_url_check.html [fortinet.com]
      Websense : http://csi.websense.com/ [websense.com]
      ZScaler : http://zulu.zscaler.com/ [zscaler.com]
      Bluecoat : https://sitereview.bluecoat.com/sitereview.jsp [bluecoat.com]
      (etc...)

      HTH !

      --
      Francois.

      • (Score: 2) by Jaruzel on Thursday March 13 2014, @05:41AM

        by Jaruzel (812) on Thursday March 13 2014, @05:41AM (#15774) Homepage Journal

        Actually that does help me - thanks very much. It's quite hard digging up all those classification URLs for the different services, so I've bookmarked the above, Cheers.
        (I'm having a classification issue with one of my own domains).

        -Jar

        --
        Wash at 40°C, and hand dry only. My MUD Engine [jaruzel.com]