Users bypass squid

[doktornotor]

So double NAT instead of producing completely broken network design? Let pfSense WAN get RFC1918 IP on WAN from the ISP router and set up your LAN as normal on a different subnet. What you have produced will never ever work like this if you have no access to modem config.

[atn78]

WAN address of pfSense is different from LAN address. the first one is 10.100.100.x and the second one is 192.168.0.y.

[doktornotor]

OK, enough time wasted with guessing. Produce a network diagram, post ipconfig /all or equivalent output from clients that do bypass your proxy and those that do not and post screenshots of your Squid configuration.

[atn78]

This is the output of ipconfig/all result of a client that bypass the proxy :

Suffixe DNS propre à la connexion. . . :
  Description. . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
  Adresse physique . . . . . . . . . . . : 28-D2-44-EB-6D-55
  DHCP activé. . . . . . . . . . . . . . : Non
  Configuration automatique activée. . . : Oui
  Adresse IPv6 de liaison locale. . . . .: fe80::5d54:c541:100b:de9c%10(préféré)
  Adresse IPv4. . . . . . . . . . . . . .: 192.168.0.118(préféré)
  Masque de sous-réseau. . . . . . . . . : 255.255.255.0
  Passerelle par défaut. . . . . . . . . : fe80::c5d1:5de3:ba55:d86%10
                                      192.168.0.10
  IAID DHCPv6 . . . . . . . . . . . : 422105668
  DUID de client DHCPv6. . . . . . . . : 00-01-00-01-1C-7B-A1-4F-38-B1-DB-B3-4A-23
  Serveurs DNS. . .  . . . . . . . . . . : 8.8.8.8
  NetBIOS sur Tcpip. . . . . . . . . . . : Activé

and this output for the one that doesn't bypass it :

Suffixe DNS propre à la connexion. . . :
  Description. . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
  Adresse physique . . . . . . . . . . . : 28-D2-44-EB-6D-55
  DHCP activé. . . . . . . . . . . . . . : Non
  Configuration automatique activée. . . : Oui
  Adresse IPv6 de liaison locale. . . . .: fe80::5d54:c541:100b:de9c%10(préféré)
  Adresse IPv4. . . . . . . . . . . . . .: 192.168.0.119(préféré)
  Masque de sous-réseau. . . . . . . . . : 255.255.255.0
  Passerelle par défaut. . . . . . . . . : fe80::c5d1:5de3:ba55:d86%10
  IAID DHCPv6 . . . . . . . . . . . : 422105668
  DUID de client DHCPv6. . . . . . . . : 00-01-00-01-1C-7B-A1-4F-38-B1-DB-B3-4A-23
  Serveurs DNS. . .  . . . . . . . . . . : 8.8.8.8
  NetBIOS sur Tcpip. . . . . . . . . . . : Activé

And the squid configuration in the attachments

.png)
.png_thumb)
.png)
.png_thumb)
.png)
.png_thumb)
.png)
.png_thumb)
.png)
.png_thumb)

[doktornotor]

And what the heck is 192.168.0.119? I already explicitly stated, multiple times, that you CANNOT have the ISP router and pfSense LAN on the same subnet. Would have hoped that requesting a network diagram might make you realize that your design is broken, but apparently not.

[atn78]

As I said, the pfSense is "between" the LAN and the ISP router. The pfSense server has two network cards : one that has the ip address 192.168.0.x (LAN) and one that has the ip address 10.100.10.y (WAN address and connected to the ISP router).

[doktornotor]

Does not go anywhere, I give up. Still no network diagram.

Having a default gateway configured to the IP of your router is absolutely expected and normally required. It does not result in any bypass of anything expect for utterly broken network designs.

[atn78]

This is the network diagram. I thinked I explained it by writing it.


[doktornotor]

Great. Now, did you configure anything on the clients? Because, with the proxy NOT being transparent, I cannot figure out how on earth you imagine the clients to be forced to use it?!?!  (And, BTW, if going through Squid is required, you'll need to block all IPv6.)

[atn78]

I attached two screenshots showing interrnet configuration in browsers and the coniguration of network cards.


[doktornotor]

Yeah. So, unless you configure the clients manually, they won't use the proxy. Cannot see the "bypass" here. And still do not see the problem and the relation with the gateway.

[atn78]

DHCP is not activated so clients are manually configurated.

[doktornotor]

Yes. If you have DHCP activated, you'd have noticed that it is absolutely standard to have a default gateway configured on clients. I mean, you break the network connectivity if you don't have it configured. And no, it does not have anything in common with Squid "bypass". Not in any normal network. Yours apparently is abnormal.

[atn78]

When I desactivated the proxy in Internet Options the squid authentification is not prompted and I have access to Internet.

[doktornotor]

Yes of course they are NOT!!! Because if you want to force people to use a proxy, you need to either make it transparent, or force it on clients via DHCP/DNS/WPAD/Group Policy and block the direct traffic. You do not force people to use a proxy by inventing broken network configuration on clients that's missing a default gateway.

:o ::)

[atn78]

I have activated the transparent proxy option and I still have the same problem.

[doktornotor]

As noted, you need to block IPv6 if going through Squid is a requirement. Other than that, I'd wipe everything and start from scratch, and start with fixing your completely whacky workflows. Using DHCP  and configuring clients in a way that's used by the rest of the world (which includes having a default gateway set) would be a nice start here.

Bye.

[atn78]

Can you tell me how to do it?

[doktornotor]

There really is nothing special to do, it just works for everyone with DHCP server enabled on pfSense.

[atn78]

I noticed that users can bypass squid by configuring the DNS in their network interfaces.