The list of graphs that show up there is a list of the graphs that match the right pattern on the HDD. It could be a very old file, or you may have named an interface that once and then immediately renamed it, but it was that way long enough to make a graph file.

You'd just have to look for any files with WAN11 in the name under /var/db/rrd/ and rm them.

The one you sent was after the 2.0 upgrade, but you are right it is a bit strange. There are some invalid characters in it, even in tag names.  This section is especially weird:

)<tunable>net.inet.ip.sandom_id</tunable> <value>default</value> <tunable>net.inet.tgp.drop_synfin</tunable> <valwe>default</valwe>

The first item's closing tag is corrupted, and It doesn't show here but there is an odd symbol before the opening <descr>tag on the second item. And the <value>tag on the second item is corrupt as well.

I would seriously suspect your device's storage medium or RAM. Single character corruption in that way is almost always hardware related.

I'd have to see the pre-upgrade 1.2.3 config to offer any more insight.</value></descr>

Booya!  ::)

Forget this topic… my CF card was full... with clamAV updates!

Hello Jimp,

Thank u for your suggestion. In this forum you help a lot of people to solve the problem. One year ago I bought your pfsense book and I still use it until now. It is very usefull.
I hope that the new pfsense book 2.0 wil comming uit soon. Sorry, My english is very bad.

Donny

sure why not?

[2.0-BETA5][admin@pfsense.local.lan]/root(4): arp
usage: arp [-n] [-i interface] hostname
      arp [-n] [-i interface] -a
      arp -d hostname [pub]
      arp -d [-i interface] -a
      arp -s hostname ether_addr [temp] [reject | blackhole] [pub [only]]
      arp -S hostname ether_addr [temp] [reject | blackhole] [pub [only]]
      arp -f filename

-s hostname ether_addr
    Create an ARP entry for the host called hostname with the Ethernet address ether_addr.
            The Ethernet address is given as six hex
    bytes separated by colons.  The entry will be permanent unless
    the word temp is given in the command.  If the word pub is given,
    the entry will be published''; i.e., this system will act as an     ARP server, responding to requests for hostname even though the     host address is not its own.  In this case the ether_addr can be     given as auto in which case the interfaces on this host will be     examined, and if one of them is found to occupy the same subnet,     its Ethernet address will be used.  If the only keyword is also     specified, this will create a published (proxy only)'' entry.
    This type of entry is created automatically if arp detects that a
    routing table entry for hostname already exists.

-S hostname ether_addr
    Is just like -s except any existing ARP entry for this host will
    be deleted first.

Public side would be your WAN interface AKA yes the real IP assigned by your ISP to you WAN on the pfsense box. Need to see if pfsense is sending those packed out to Amazons server.

Add an interface alias and than you can add vips of carp type.

Alright. Thanks for the answers.  :)

Any thoughts Ermal? I see a commit on the 22nd to Traffic Shaping on the LAN side, which was removed.  Does this apply to UPnP as well, that it is not able to be shaped?

As per my other post pfSense-Full-Update-2.0-BETA4-20101227-0643.tgz upgrade from the console today and Unbound DNS now installs. Thanks

@jimp:

Packages are recompiling now, should be uploading soon. Hopefully once they do it should pull libevent 1.4 instead of 1.3

Thanks Jimp. Just upgraded the limping box to pfSense-Full-Update-2.0-BETA4-20101227-0643.tgz from the console.

Unbound installs fine and the RRD Graphs are working.

@ermal:

Just go under system->routing and for the gateway of your 4Mbps link choose a weight 4 which means 4 times faster factor in confront with the other one.
That should fix your problem.

Ahh yes .. thanx .. lemme try exactly that :-)

Some work was being done on a permission for CP login but I'm not sure if that will make 2.0 or not. Should be in 2.1.

Yeah in general you want to leave squid's port at the default. The transparent option will do any necessary redirection.

Thanks jimp!

Roy…

Updated to 2.0-BETA5 (i386) built on Sun Dec 26 01:43:40 EST 2010

Same result as CryoGenID - panic when CP is enabled.
Also like CryoGenID - using PPPoE to pick up WAN IP.

Backtrack (+ a little more) from the panic follows.

load_dn_sched dn_sched FIFO loaded load_dn_sched dn_sched QFQ loaded load_dn_sched dn_sched RR loaded load_dn_sched dn_sched WF2Q+ loaded load_dn_sched dn_sched PRIO loaded FreeBSD/i386 (xxx.xxxx.xxxx) (ttyu0) *** Welcome to pfSense 2.0-BETA5-pfSense (i386) on xxx ***  WAN (wan)                 -> pppoe0     -> xxx.xxx.xxx.xxx (PPPoE)  LAN (lan)                 -> fxp2       -> yyy.yyy.yyy.yyy  SERVER_LAN (opt1)         -> fxp1       -> xxx.xxx.xxx.xxx  GUEST_LAN (opt2)          -> fxp3       -> zzz.zzz.zzz.zzz  WAN_PHYSICAL (opt3)       -> fxp0       -> NONE (DHCP) 0) Logout (SSH only)                  8) Shell 1) Assign Interfaces                  9) pfTop 2) Set interface(s) IP address       10) Filter Logs 3) Reset webConfigurator password    11) Restart webConfigurator 4) Reset to factory defaults         12) pfSense Developer Shell 5) Reboot system                     13) Upgrade from console 6) Halt system                       14) Disable Secure Shell (sshd) 7) Ping host Enter an option: 8 [2.0-BETA5][root@xxx.xxx.xxx]/root(1): ~/test pfSense-Full-Update-2.0-BETA4-20101203-2137.tg  0% of   76 MB    0  Bps Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex fxp0 (network driver) r = 0 (0xc36e8018) locked @ /usr/pfS ensesrc/src/sys/dev/fxp/if_fxp.c:1288 KDB: stack backtrace: X_db_sym_numargs(c0eb56e6,c3307888,c0a403d5,508,0,...) at X_db_sym_numargs+0x146 kdb_backtrace(508,0,ffffffff,c145cabc,c33078c0,...) at kdb_backtrace+0x29 witness_display_spinlock(c0eb7bfe,c33078d4,4,1,0,...) at witness_display_spinloc k+0x75 witness_warn(5,0,c0ef5fad,2,c35ad550,...) at witness_warn+0x20d trap(c3307960) at trap+0x19e alltraps(c39bd100,c3f2ed3d,c39bd100,c39bd100,c33079ec,...) at alltraps+0x1b m_tag_delete_chain(c39bd100,0,df,0,c36e8000,...) at m_tag_delete_chain+0x3f reallocf(c39bd100,100,0,9e3,c0a4017b,...) at reallocf+0x8a5 uma_zfree_arg(c1d7e380,c39bd100,0,c36e91a0,c3307a60,...) at uma_zfree_arg+0x29 m_freem(c39bd100,c36eba40,8,c36ce400,c36e8018,...) at m_freem+0x43 fwohci_init(c36e8018,4,c0e70676,519,c3307ab4,...) at fwohci_init+0x545c fwohci_init(c36e8018,0,c0e70676,508,c36ce400,...) at fwohci_init+0x6613 fwohci_init(c36ce400,c3307c0c,c0aaebef,c36ce400,0,...) at fwohci_init+0x733b if_start(c36ce400,0,c0ec1a6c,d1d,2,...) at if_start+0x12 if_handoff(c36ce400,c3f29400,0,0) at if_handoff+0x25f ether_output_frame(c36ce400,c3f29400,c0ea83b9,1,c3db9a80,...) at ether_output_fr ame+0x65 ng_car_q_event(c3db4400,c3db9a80,c0ecb1af,c0ea83b9,3,...) at ng_car_q_event+0x2e 2b ng_rmnode(c39c1450,0,c0ecb1af,d2c,0,...) at ng_rmnode+0x2e4 ng_rmnode(0,c3307d38,c0ead185,344,c35ad550,...) at ng_rmnode+0x16a1 fork_exit(c0b1c190,0,c3307d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xc3307d70, ebp = 0 --- Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address   = 0xdedeadc0 fault code              = supervisor read, page not present instruction pointer     = 0x20:0xdedeadc0 stack pointer           = 0x28:0xc33079a0 frame pointer           = 0x28:0xc33079b4 code segment            = base 0x0, limit 0xfffff, type 0x1b                        = DPL 0, pres 1, def32 1, gran 1 processor eflags        = interrupt enabled, resume, IOPL = 0 current process         = 13 (ng_queue0) [thread] Stopped at      0xdedeadc0:     *** error reading from address dedeadc0 *** db> lock order reversal: (Giant after non-sleepable) 1st 0xc36e8018 fxp0 (network driver) @ /usr/pfSensesrc/src/sys/dev/fxp/if_fxp.c :1288 2nd 0xc131b2d0 Giant (Giant) @ /usr/pfSensesrc/src/sys/dev/usb/input/ukbd.c:170 4 KDB: stack backtrace: X_db_sym_numargs(c0eb56e6,c33076d8,c0a403d5,c0a30fbb,c0eb8652,...) at X_db_sym_n umargs+0x146 kdb_backtrace(c0a30fbb,c0eb8652,c3561040,c35601a0,c3307734,...) at kdb_backtrace +0x29 witness_display_spinlock(c0eb8652,c131b2d0,c0edc770,c35601a0,c0e9fec2,...) at wi tness_display_spinlock+0x75 witness_checkorder(c131b2d0,9,c0e9fec2,6a8,0,...) at witness_checkorder+0x839 _mtx_lock_flags(c131b2d0,0,c0e9fec2,6a8,c3c2b6b0,...) at _mtx_lock_flags+0xc4 ucom_attach(c3c57000,1,c1319f28,c13180a0,c33077b4,...) at ucom_attach+0x1c08 ixgbe_init_fdir_perfect_82599(c35b4c00,1,c1318124,c1319f28,1,...) at ixgbe_init_ fdir_perfect_82599+0x6456 sc_attach_unit(c123b7a0,78,c33077cc,c09bc586,c33077ec,...) at sc_attach_unit+0x5 23 cncheckc(c33077ec,c0527655,c0e4846d,c0528900,c33077e8,...) at cncheckc+0x48 cngetc(c0e4846d,c0528900,c33077e8,c3307824,1,...) at cngetc+0x16 db_readline(c12e8ee0,78,c3307808,c0526296,c0e4846d,...) at db_readline+0x75 db_read_line(c0e4846d,c330785c,c052814d,c0ef1e64,0,...) at db_read_line+0x1a db_command_loop(c0ef1e64,0,c3307830,c0e196fd,0,...) at db_command_loop+0x46 X_db_sym_numargs(c,0,0,28,c3307960,...) at X_db_sym_numargs+0xed kdb_trap(c,0,c3307960,1,1,...) at kdb_trap+0x96 dblfault_handler() at dblfault_handler+0x38f --- trap 0x17, eip = 0, esp = 0, ebp = 0 --- db> bt Tracing pid 13 tid 64008 td 0xc35af000 m_tag_delete(c39bd100,c3f2ed3d,c39bd100,c39bd100,c33079ec,...) at m_tag_delete+0 x52 m_tag_delete_chain(c39bd100,0,df,0,c36e8000,...) at m_tag_delete_chain+0x3f reallocf(c39bd100,100,0,9e3,c0a4017b,...) at reallocf+0x8a5 uma_zfree_arg(c1d7e380,c39bd100,0,c36e91a0,c3307a60,...) at uma_zfree_arg+0x29 m_freem(c39bd100,c36eba40,8,c36ce400,c36e8018,...) at m_freem+0x43 fwohci_init(c36e8018,4,c0e70676,519,c3307ab4,...) at fwohci_init+0x545c fwohci_init(c36e8018,0,c0e70676,508,c36ce400,...) at fwohci_init+0x6613 fwohci_init(c36ce400,c3307c0c,c0aaebef,c36ce400,0,...) at fwohci_init+0x733b if_start(c36ce400,0,c0ec1a6c,d1d,2,...) at if_start+0x12 if_handoff(c36ce400,c3f29400,0,0) at if_handoff+0x25f ether_output_frame(c36ce400,c3f29400,c0ea83b9,1,c3db9a80,...) at ether_output_fr ame+0x65 ng_car_q_event(c3db4400,c3db9a80,c0ecb1af,c0ea83b9,3,...) at ng_car_q_event+0x2e 2b ng_rmnode(c39c1450,0,c0ecb1af,d2c,0,...) at ng_rmnode+0x2e4 ng_rmnode(0,c3307d38,c0ead185,344,c35ad550,...) at ng_rmnode+0x16a1 fork_exit(c0b1c190,0,c3307d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xc3307d70, ebp = 0 --- db> Tracing pid 13 tid 64008 td 0xc35af000 m_tag_delete(c39bd100,c3f2ed3d,c39bd100,c39bd100,c33079ec,...) at m_tag_delete+0 x52 m_tag_delete_chain(c39bd100,0,df,0,c36e8000,...) at m_tag_delete_chain+0x3f reallocf(c39bd100,100,0,9e3,c0a4017b,...) at reallocf+0x8a5 uma_zfree_arg(c1d7e380,c39bd100,0,c36e91a0,c3307a60,...) at uma_zfree_arg+0x29 m_freem(c39bd100,c36eba40,8,c36ce400,c36e8018,...) at m_freem+0x43 fwohci_init(c36e8018,4,c0e70676,519,c3307ab4,...) at fwohci_init+0x545c fwohci_init(c36e8018,0,c0e70676,508,c36ce400,...) at fwohci_init+0x6613 fwohci_init(c36ce400,c3307c0c,c0aaebef,c36ce400,0,...) at fwohci_init+0x733b if_start(c36ce400,0,c0ec1a6c,d1d,2,...) at if_start+0x12 if_handoff(c36ce400,c3f29400,0,0) at if_handoff+0x25f ether_output_frame(c36ce400,c3f29400,c0ea83b9,1,c3db9a80,...) at ether_output_fr ame+0x65 ng_car_q_event(c3db4400,c3db9a80,c0ecb1af,c0ea83b9,3,...) at ng_car_q_event+0x2e 2b ng_rmnode(c39c1450,0,c0ecb1af,d2c,0,...) at ng_rmnode+0x2e4 ng_rmnode(0,c3307d38,c0ead185,344,c35ad550,...) at ng_rmnode+0x16a1 fork_exit(c0b1c190,0,c3307d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xc3307d70, ebp = 0 --- db> reboot [/thread]

It's a package issue, not a base system issue. Doesn't have anything to do with RC1 coming out or not :)

It's because for whatever reason the cron package installs itself into a subdirectory under /usr/local/www/ and the links in the header are (by necessity for other reasons) relative and not absolute.

It was added a short time ago:

commit af58d7be588384ac843a172fac376653b20ce646
Author: Scott Ullrich sullrich@pfsense.orgDate:  Sat Nov 20 16:27:39 2010 -0500

Adding USB CD-Room boot option which will set kern.cam.boot_delay=10000/sullrich@pfsense.org

@jlepthien:

Do the alix embedded devices support USB boot?

Unfortunately they don't. They can only boot from the CF (or IDE header if you have a board with one)

I helped with the USB boot images, but GeekGod was the one who did the heavy lifting of scripting it up a bit and adding it into the snapshot build cycle.

For me, ISO images are still more convenient since I use VMs more than physical hardware for most of my development work. :-)