For some reason recently, I've noticed that pfSense will arbitrarily
block some IP's for no good reason and I can't figure out why. For the
longest time it was blocking 4.2.2.1, but that was solved today by a reboot
(I bumped the plug.) That inadvertent reboot also corrected pfSense blocking
access to my VPS for some reason. After the reboot, things worked fine for a
few hours. I had to leave and when I came back several hours later to resume
my work on the VPS, I found that I again could not connect to it, I can get
name resolution on a domain pointing to that machine (served by it's own
PowerDNS Server.) So I am quite stumped as to why I cannot connect to this
machine. At first I thought it was my ISP, but now I'm not so sure and
learning on it being my Netgate Appliance running PfSense.

So details and diagnostics below (all preformed from the router:

[2.0.1-RELEASE][[email protected]]/root(15): uname -a
FreeBSD router.xaerolimit.net 8.1-RELEASE-p6 FreeBSD 8.1-RELEASE-p6 #0: Mon
Dec 12 18:59:41 EST 2011
root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
 i386
[2.0.1-RELEASE][[email protected]]/root(16): ping -c 5
xaerolimit.net
PING xaerolimit.net (184.95.52.211): 56 data bytes

--- xaerolimit.net ping statistics ---
5 packets transmitted, 0 packets received, 100.0% packet loss
[2.0.1-RELEASE][[email protected]]/root(21): traceroute
xaerolimit.net
traceroute to xaerolimit.net (184.95.52.211), 64 hops max, 40 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
[2.0.1-RELEASE][[email protected]]/root(15):

The reason I know the VPS is up and responsive, is because I am vnc'd
into the host and from the VNC console, I can run a traceroute to my
ISP's IP assigned to my Cable Modem and it will run it's course into
my city and then I just get stars for responses.

So I am quite stumped. Oh and freenode/#pfSense suggsted I look in
/var/log for anything about a "DNS re-bind attack" for which I found
nothing.

> --
> Chris Brennan
> A: Yes.
> >Q: Are you sure?
> >>A: Because it reverses the logical flow of conversation.
> >>>Q: Why is top posting frowned upon?
> http://xkcd.com/84/ | http://xkcd.com/149/ | http://xkcd.com/549/
> GPG: D5B20C0C (6741 8EE4 6C7D 11FB 8DA8  9E4A EECD 9A84 D5B2 0C0C)
------------------------------------------------------------------------
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to