[UCIMC-Tech] Can't access google on IMC's wireless

[Stuart Levy]

On Thu, Dec 11, 2008 at 04:04:42PM -0600, Barry Isralewitz wrote:
> Hi Josh,
>
>
>   Were you ever able to get to the network/firewall  problem in the IMC 
> basement/Bike Project fixed -- glacial access to google-using-sites?
> The last time I checked, I think there were still delays on sites that use 
> google-metrics/google-ads
> We at the Bike Project really need to use our off-site wiki site, but 
> effectively can't because of this problem.
> This is a real problem for us; starting to cause larger and larger 
> organizational problems.

It still wasn't as of last week (I'll bet the new website installation has been
higher priority, which seems like a good choice to me).  But probably
the workaround that Josh has described in the past should work.

I went to the Bike Project a couple months ago and poked around on
the FreeBSD machine in the shop there.   It appeared that the "RFC1323"
workaround hadn't been installed quite right -- it looked plausible but
the boot scripts would likely misparse it.

Here's what I wrote then.  Did anybody try it??  (Obviously I couldn't
change anything on the machine myself.)

|   From slevy Sat Sep 27 15:28:33 2008
|   Date: Sat, 27 Sep 2008 15:28:33 -0500
|   From: Stuart Levy <slevy>
|   To: Stuart Levy <slevy at ncsa.uiuc.edu>
|   Cc: Barry Isralewitz <barryi at ks.uiuc.edu>,
|   	IMC-Tech List <imc-tech at ucimc.org>
|   Subject: Re: [UCIMC-Tech] Re: Google via IMC wired ethernet [was: bikeproject computer]
|   
|   Barry Israeliwitz had written:
|   
|   > > > Details:
|   > > >   Just like with the Bike Project BSD machine,
|   > > > every site worked except for Google sites, and sites that halted waiting
|   > > > for googlesyndication.com and Google metrics.
|   
|   I just had a look at the Bike Project FreeBSD machine.
|   Its net.inet.tcp.rc1323 is set to the default (1),
|   which explains why it can't reach Google.
|   
|   Looking at its /etc/sysctl.conf and at the /etc/rc.d/sysctl
|   which reads that file, a clue:
|   
|     /etc/sysctl.conf mentions:
|   
|   net.inet.tcp.rfc1323 = 0
|   
|   But, from a quick glance, the script that reads this
|   may be expecting no blanks around the "=" sign, as in:
|   
|   net.inet.tcp.rfc1323=0
|   
|   So that's worth a try -- with that change, it might come up correctly
|   after the next reboot.  Meanwhile you'd want to (as root) do something like
|   
|      /sbin/sysctl -w net.inet.tcp.rfc1323=0
|    (with no blanks around the = sign)
|   
|   which might get it working for now.