Brand new nano-bsd install (2.3.2_1) unable to reach http but https reachable???
-
until the other a week or so ago..everything worked fine (i even had squid & reverse squid setup working just fine with exchange OWA & activesync with ssl) then all of a sudden i was unable to reach http. i had zero problems with https.
so i couldnt figure it out and said screw it and built a new nanobsd watchguard box i had with the same hardware…
i have setup a brand new install (2.3.2_1 version) with zero rules setup other than the 'allow all', configured dns resolution (works), and allowed everything to go through my fios router (i added the pfsense as the dmz host).
yet i am still unable to reach http sites, and i am able to reach https sites just fine. it makes zero sense.
my setup is as follows...
fios router (allow all to dmz host 192.168.1.2 wan interface - zero firewall enabled) -> pfsense (192.168.2.1 lan interface - allow all rules only) -> switch(s)
no modules are installed...
any ideas?
-
here is a neat thing that fios does not tell you…. :'( :o :o
so if for some reason your account is disabled (non-payment, changes made, or something on their end..which is what my case was..the card on file name was changed)
you can actually still access https and other secured connections, but you can not access ANY other connections. makes a hell lot of sense does it not?
screw residential internet access..im going business!
just a little FYI for those who may run across such an issue.