WPAD on BLUE (groan)

Networking
1

Hi,
So getting WPAD working on BLUE is killing me.
This is what I have, but the clients just don’t seem to be able to get the config file from http://192.168.2.254:81/wpad.dat
WGET (Windows)/PowerShell Invoke-webrequest just time out on the connection.
The file is there as “wget http://192.168.2.254:81/wpad.dat” on the fw works. So something appears to be blocking the client request, but not seeing anything on the logs.
IPFire Green: 192.168.1.112, Blue: 192.168.2.254
Web proxy

image
image854×241 14.3 KB

image
image724×470 13.2 KB

DHCP
image
image988×610 29 KB

image
image971×273 10.6 KB

image
image942×174 6.85 KB

wpad.conf
image
proxy.pac
image

2

Did you enable the blue access?

3

Yes and it’s providing leases.

image
image966×526 16.6 KB

4

I’ve just checked the proxy log and it appears some clients are getting the wpad.dat.
Should it just be the name, rather than the full URL and also when I hover over the /wpad.dat entry, it shows as ‘https://192.168.1.112:444/wpad.dat’ !

image
image972×549 26.3 KB

6

To troubleshoot I always have a console open to IPFire with tail -f /var/log/messages (ctrl+c to exit) and then I trigger whatever problem I am trying to troubleshoot. In your case, I would try to wget wpad file from blue and see in real time what’s happening with IPFire kernel.

3 Likes
7

Getting IPs via DHCP works even there is no access on BLUE.

2 Likes
8

This is what I see when connecting

image
image1063×176 11.1 KB

9

Drop Input means the device is not allowed to communicate with the network, so you must have missed something: WPAD on BLUE (groan) - #2 by cfusco

10

I want just to clarify something, because it comes up from time to time.
Wireless internet access has three stages ( in IPFire ):

  • establish connection via 802.11 ( “plugin of the wireless cable” )
  • connection to the blue network ( usually per DHCP )
  • routing to WAN ( firewall rules defined with access to blue )
3 Likes