Search squid archive

Re: Squid via Network Wireless Router & Wireless Clients

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7/07/2012 6:10 p.m., Adrian Miller wrote:
Squid via Network Wireless Router & Wireless Clients

Hopefully this is a simple question, with an equally quick answer.

I have set up traditional squid setups before, with the 2 NIC setup.

This time though i have only a wireless router connected via ethernet
to the squid box (1 NIC only).

All clients will connect to the squid box via the wireless router.

i.e.
Code:

Wireless Client Laptops
  |
\/
Wireless Router/ADSL2 Modem ---- > Interwebs
  |    /\
\/    |
Squid

So my question (and im probably looking for reinforcement/outright
ridicule for my own thoughts) is

"Whats the best way to implement this?"

Is it as simple as forwarding all traffic from the router port 80 to
the squid box port 3128 in the router config and running the squid box
in transparent mode.

Yes it can be that simple. The only issue is whether your wireless+router+adsl+modem combo box supports it. The usual "port forwarding" supplied by CPE boxes with off the shelf commercial software does not work well. OpenWRT and such which allow much deeper admin control can be configured fairly easily using the Squid wiki configs like any router.


Or

The above but conventional with proxy set manually on each client

That is better. But manual configuration can be a hassle on any type of large or dynamic network. Interception pushing clients at the squid ERR_CONFIG_* pages help clients to do it themselves, but can still be trouble.


Or neither, and you have a more sane approach

Slightly more sane is to setup WPAD on the network. Then push clients to setup "auto-detect". That lets you hide any and all proxy changes behind a PAC file. Including proxy bypasses etc for the occasional broken websites.


It is much easer to configure with separated wireless, router, and modem boxes.

My favourite for this type of installation is:
clients -> portal (wireless AP -> Squid router -> ADSL modem) -> Intarwebs.

With an off the shelf Linux box running Squid and all the regular tools needed for routing whatever the installation needs its easily extended or changed. As the AP/modem components burn out or age they can be replaced without affecting the whole setup.

Amos


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux