Netgate SG-1000 microFirewall

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - johnpoz

Pages: 1 ... 3 4 5 6 [7]
Ok running ipv6 gitsync stuff, so not sure if related to that or what?  But getting these errors whenever look at traffic or packet graphs

Mar 12 08:01:47    php: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Could not parse color in ''/usr/bin/nice -n20 /usr/local/bin/rrdtool graph /tmp/wan-traffic.rrd-4year.png --start 1199080800 --end 1299938506 --vertical-label "bits/sec" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "`hostname` - WAN :: Traffic - 3 years - 1 day average" --height 200 --width 620 DEF:wan-in_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass:AVERAGE DEF:wan-out_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass:AVERAGE DEF:wan-in_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock:AVERAGE DEF:wan-out_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock:AVERAGE DEF:wan-in6_bytes_pass=/var/db/rrd/wan-traffic.rrd:inpass6:AVERAGE DEF:wan-out6_bytes_pass=/var/db/rrd/wan-traffic.rrd:outpass6:AVERAGE DEF:wan-in6_bytes_block=/var/db/rrd/wan-traffic.rrd:inblock6:AVERAGE DEF:wan-out6_bytes_block=/var/db/rrd/wan-traffic.rrd:outblock6:AVERAGE CDEF:"wan-in_bits_pass=wan-in_bytes_pass,8,*" CDEF:"wan-out_bi

Also if you unclick openntpd service shows running, if you check it says off.

Running current snap
2.0-RC1-IPv6 (i386)
built on Sat Mar 12 01:18:33 EST 2011

and just ran
pfSense shell: playback gitsync master

so should be on latest.

IPv6 / openvpn broke since added ipv6
« on: March 07, 2011, 03:22:58 pm »
Does anyone have openvpn working after they have added the ipv6 stuff.

edit: ok, seems I just had to go into the openvpn connection, click edit and save.. now working!!

Seems my openvpn interface as missing the inet4 address, saving the config put it back

inet --> netmask 0xffffffff

So far have everything working!!! sweet!!!

IPv6 / unbound on ipv6
« on: March 06, 2011, 06:32:45 pm »
So ran through the setup on the welcome message.  Ran smooth as silk, had to toggle the default gateway on the wanipv6 I setup -- but other than working great, dhcp works -- pointed dns to the dns, and hands that out great.

But running unbound and would like clients to use that, but when I tell unbound to use the lan, and wanipv6 interface created via the welcome thread instructions - unbound dies.

Any tricks here?  I have to run so will look at closer later - but shouldn't I be able to get unbound to listen on both ipv4 and ipv6 addresses?  But it seems to die when I do that, and get this error in the system log

Mar 6 18:22:43    php: /pkg_edit.php: The command '/usr/local/sbin/unbound-control start' returned exit code '1', the output was '/usr/local/etc/unbound/unbound.conf:32: error: stray '"' /usr/local/etc/unbound/unbound.conf:32: error: stray '"' read /usr/local/etc/unbound/unbound.conf failed: 2 errors in configuration file [1299457363] unbound[19270:0] fatal error: Could not read config file: /usr/local/etc/unbound/unbound.conf'

Just a cosmetic thing, but under diag menu you see two states links, bottom one is the summary - possible to update menu to say "States Sum" or something ;)


Ok running vmware server 2.02 on 2k8 windows box.

2.0-BETA4  (i386)
built on Tue Aug 17 03:29:48 EDT 2010

So install went fine - host box is on vmnet0 (bridged) intel motherboard nic, wan of pfsense is on vmnet2 (bridged) realtek, lan of pfsense was also on vmnet0

Can not get any port forwards to work.. To copy of vm ubuntu connected to vmnet0, ssh.  Can not forward to host box either, ssh or dns.  But can forward to another physical box just fine through the virtual pfsense.

Outbound internet works just fine from other physical boxes, the host and the virtuals.  Just can not get any forwards to work - unless send off the host machine to another physical box.

So thinking it might have something to do with all the lan interfaces of the host, ubuntu and pfsense were on the same physical nic connected to vmnet0, I added another nic to the host on vmnet3.. But still can not forward to host machine, or ubuntu with this setup either.  But forwards to physical box works just fine.

Any ideas??  I would really love to keep running pfsense virtual - but if I can not get forwards to work to other virtual machines on the same host will have to go back to running pfsense on its own hardware.

Pages: 1 ... 3 4 5 6 [7]