Thank you for all the suggestions.  I will look at the logs, network and other aspects
of the setup and will post anything that will help the next person with Tivo issues.
It just does not make alot of sense the issue I am having

Are you sure it really is? Try running 'top -aSH' so you can see the idle processes.
Are you running powerd? Is the CPU running down clocked?
Have you left the webgui dashboard open anywhere, I've been fooled by that before?

Steve

My experience with comcast ipv6 and pfsense has been less than perfect that is for sure - but my tunnel with HE is stable, never any issues and never have to worry about it changing, etc.

You can get a /48 from them if you need more than one /64 on your local stuff.  You can even setup PTR for your ipv6 you get from HE - comcast doesn't provide that, etc. ;)

Yes - Now this I can agree with, but thats a user issue.
I think trying it a couple days with a clean install of whatever OS he likes is probably a good idea.
If malware is the problem, don't need to be bouncing his pfsense box all the time.  Needs to get rid of the malware.

Yes.  Add VIP with type "IP Alias", which shows up as type "IfAlias"

"I can;t resolve any IP on the network or on pfsense"

How would 8.8.8.8 know about your IPs?  if your using windows for dns, why would pfsense know about your network?

Need more info.

What are you clients using for dns?  What are you trying to resolve?

I think the problem is that /etc/rc.openvpn didn't end.

I have them multiple times and didn't see why they didn't terminate.

Hmm Very odd - did a factory resetand then rebuilt it and all is now well - Not sure what was happening there have been messing around fairly heavily adding and deleting interfaces so I guess something got messed up.

thanks

@stephenw10:

That's what I thought you'd say.  :D

You could look at the various sections on the status.php page. The information you want will be there but not necessarily how you want it. It's not linked to from anywhere in the GUI just enter it manually: <pfsense ip="">/status.php

What are you wanting the report for?

Steve</pfsense>

Nice, was not aware of that page.

I just want something to show all Vips, carps, Alias, rules.

The Nano variant uses md(4) rather than tmpfs as a ram drive. You could use that.

[2.2-RC][root@xtm5.localdomain]/root: mount -p /dev/ufs/pfsense0 / ufs ro,sync,noatime 1 1 devfs /dev devfs rw 0 0 /dev/ufs/cf /cf ufs ro,sync,noatime 1 1 /dev/md0 /tmp ufs rw 2 2 /dev/md1 /var ufs rw 2 2 devfs /var/dhcpd/dev devfs rw 0 0

You can move /tmp onto a ram disk on a full install using the options in System: Advanced: Miscellaneous:

Edit: Although..https://forums.freebsd.org/threads/tmpfs-dev-shm-md-questions.45210/#post-256239

Steve

I may question how the 8 hour graph can get results like 0.12% in a 1min average,  but when I ran a ping myself and upped the sampling rate, I would get similar numbers. I wonder if it does some kind of weighted sliding window for the average percentage.

The main thing is the numbers seem trustworthy, so I'm happy. Maybe I just to look at the code. I've never done that before.

Leave it unchecked to kill the states.
That's almost certainly the behaviour you want.

Steve

Hi,

Did you ever get an answer to this? FYI, I had the same question … all when green when you actually add the Pool to a Virtual Server (until then, no checks it seems -> stays red).

If all the internet traffic is going through one device I can't see it making much of a difference.  The only reason I'd run it at each branch is to protect them from each other.  I'd rather maintain just the one at the WAN if possible.

No official releases are affected. It would affect the 2.2-RC snapshots but the fix is already in current snapshots (note they report 10.1-RELEASE-p1 now).

Ah ha! That makes sense.  I always wondered why it sometimes seems to work as expected and other times not.  Thanks for that!

Thanks for the reply. A reboot of the box brought things back to normal. The polling option was already disabled in the UI after the reboot. Maybe the system locked up before the change was saved to the config file?

That is highly unlikely to work as they are compiled for very different versions of FreeBSD.

In theory someone could compile apinger on a builder made to create pfSense 2.1.x images (FreeBSD 8.3 base) and then copy that over, but we have not tested that.