Looks like this is probably Snort associated. Same symptom on another site
just now traffic from Akamai. I'll figure it out. Thanks for reading.
Apr 2 19:53:43 snort[99649]: [120:10:1] (http_inspect) JAVASCRIPT
WHITESPACES EXCEEDS MAX ALLOWED [Classification: Unknown Traffic] [Priority:
3] {TCP} 72.247.27.126:80 -> 192.168.0.20:52292
Apr 2 19:53:43 snort[99649]: [120:10:1] (http_inspect) JAVASCRIPT
WHITESPACES EXCEEDS MAX ALLOWED [Classification: Unknown Traffic] [Priority:
3] {TCP} 72.247.27.126:80 -> 192.168.0.20:52292
-----Original Message-----
From: List [mailto:[email protected]] On Behalf Of Peder
Rovelstad
Sent: Thursday, April 02, 2015 6:29 PM
To: 'pfSense Support and Discussion Mailing List'
Subject: [pfSense] Odd problem with the Bing website
Hello, all. The past several days I have had a repeating problem with Bing.
At times, Bing's pages will simply stop loading, and the www is no longer
pingable. I run a trace route to www.bing.com and my workstation cannot
even find the pfSense gateway. If I trace to Google (and other sites), it
finds the gateway without issue and completes normally. If I reboot
pfSense, Bing's www is then pingable and traceable.
The problem occurs simultaneously on other workstations on the internal net.
pfSense is 2.1.5/x86 on a VIA C7 platform with Realtek NICs. Clients are
Win 7 and Server 2008R2. My WAN IP is on a 71.201.x.x net, so it's not a
miss configured subnet mask on the far end (which I've run across in the
past). Is it possible something from Bing could be altering my routing
table?
Just a puzzle, if anyone likes puzzles...
tracert www.bing.com
Tracing route to any.edge.bing.com [204.79.197.200] over a maximum of 30
hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
<etc., fails>
tracert www.bing.com
Tracing route to any.edge.bing.com [204.79.197.200] over a maximum of 30
hops:
1 <1 ms 1 ms <1 ms fw.home.org [192.168.0.1]
2 9 ms 10 ms 9 ms c-71-201-92-1.hsd1.il.comcast.net
[71.201.92.1]
3 10 ms 9 ms 9 ms
te-0-2-0-8-sur03.algonquin.il.chicago.comcast.net [68.86.117.165]
4 12 ms 11 ms 11 ms
te-2-7-0-8-ar01.elmhurst.il.chicago.comcast.net[68.86.196.133]
<etc., completes>
Thanks for reading.
Peder
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
