Too liberal an Incoming Firewall Rule?

[smice-byte (Ken Pollock)]

Continuing the discussion from Web Proxy does not start:

I am continually playing with combinations. From Firewall Options Forward/Outgoing are Blocked. And Firewall Rules Incoming only allows TCP any/any HTTPS. Is that too liberal an Incoming Firewall Rule?

[hvacguy (Shaun HVAC)]

@bonnietwin

want it to be opened you have to create a firewall rule / port forward rule to do that. Generally this would only be needed if you had a web server or a mail server or something similar in your network that required to be accessed from the internet.

You do not need open incoming ports

[smice-byte (Ken Pollock)]

Following that reasoning, the Firewall InComing and OutGoing are Blocked and Blank/Empty. The Firewall functions. The Firewall Rules direct TCP to the Proxy Ports 800 and 3128. And DHCP UDP Source 68 and Destinatikon 67. But what is the DHCP Server under Network reporting:

[hvacguy (Shaun HVAC)]

the Fixed ip 192,168.5.3
is in your dynamic ip range

my fixed ip addresses would be 1-99

[smice-byte (Ken Pollock)]

Of course. I didn’t think that. I saw Red and said Bad. Why then is the Proxy Report only showing Errors?

[bbitsch (Bernhard Bitsch)]

Your Proxy Report shows all your requests ( from 192.168.5.3 ? ) are denied.
Have allowed internet ( web ) access for this device?
BTW: As mentioned many times in community threads ( and in the wiki also ) you should separate your subnets in green.

[smice-byte (Ken Pollock)]

I thought the Firewall Rules acknowledging Proxy Ports did just that. These are the Firewall Rules:

[bbitsch (Bernhard Bitsch)]

These are just the firewall rules. The proxy has its own rules/access lists.

[smice-byte (Ken Pollock)]

Can not find any specific short coming with the Proxy Rules:

[hvacguy (Shaun HVAC)]

I’m pretty sure these are your proxy ports.
they are found here.

[smice-byte (Ken Pollock)]

Opened 80. Can not image why the other ports should receive input. Only OSCP missives are recorded: