[pfSense] RRD Graphs on 2.1.4-RELEASE (i386) nano

2014-08-14 Thread Wade Blackwell
Good morning List,
 The RRD graphs on my nano PF just dissapeared about two days ago. I
now only have allgraphs and throughput on the system tab whereas I used
to have memory, states, CPU etc. The graphs that do show up have no data in
them. I seem to recall this happened a few months back just before I
upgraded to 2.1.4. Has anyone else experienced this and is there a
workaround? Thanks all.

  -W

Wade Blackwell
Solutions Architect
(D) 805.457.8825
(C) 805.400.8485
(S) coc.wadeblackwell
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

[pfSense] IPv6 and OS X?

2014-08-14 Thread Benno Rice
Hi,

I’ve got a system running pfSense 2.1.4 (most recent) acting as a gateway for 
my Comcast internet service. I’ve got IPv6 configured as DHCP6 on the WAN side 
requesting a /64 prefix. For the LAN interface I have it set to track the WAN 
interface.

I can confirm that the WAN interface is getting an IPv6 address:

re1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC
ether 00:0d:b9:34:c6:19
inet 67.182.141.248 netmask 0xf800 broadcast 255.255.255.255
inet6 fe80::20d:b9ff:fe34:c619%re1 prefixlen 64 scopeid 0x2
inet6 2001:558:600a:35:309a:40e2:efb8:28ca prefixlen 128
nd6 options=3PERFORMNUD,ACCEPT_RTADV
media: Ethernet autoselect (1000baseT full-duplex,master)
status: active

and I seem to be getting the delegated prefix and it appears to end up on the 
LAN interface:

re2: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500

options=209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC
ether 00:0d:b9:34:c6:1a
inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255
inet6 2601:8:9a80:69d:20d:b9ff:fe34:c61a prefixlen 64
inet6 fe80::1:1%re2 prefixlen 64 scopeid 0x3
nd6 options=1PERFORMNUD
media: Ethernet autoselect (1000baseT full-duplex)
status: active

Connectivity appears to be working from the pfSense system:

[2.1.4-RELEASE][admin@pfSense]/root(32): ping6 -c 5 pfsense.org
PING6(56=40+8+8 bytes) 2001:558:600a:35:309a:40e2:efb8:28ca -- 
2610:160:11:11::69
16 bytes from 2610:160:11:11::69, icmp_seq=0 hlim=52 time=77.539 ms
16 bytes from 2610:160:11:11::69, icmp_seq=1 hlim=52 time=78.463 ms
16 bytes from 2610:160:11:11::69, icmp_seq=2 hlim=52 time=77.437 ms
16 bytes from 2610:160:11:11::69, icmp_seq=3 hlim=52 time=76.808 ms
16 bytes from 2610:160:11:11::69, icmp_seq=4 hlim=52 time=79.694 ms

--- pfsense.org ping6 statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 76.808/77.988/79.694/1.003 ms

However, my OS X system (Mavericks, up to date) doesn’t appear to be acting on 
the router advertisements the pfSense box is sending:

 ifconfig en0
en0: flags=8863UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST mtu 1500
ether 94:94:26:09:b8:1c
inet6 fe80::9694:26ff:fe09:b81c%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.15 netmask 0xff00 broadcast 192.168.1.255
nd6 options=1PERFORMNUD
media: autoselect
status: active

Even though the network configuration is set up to automatically configure IPv6 
(and has done in the past, when I was using a FRITZ!Box on Internode ADSL in 
Australia) and the pfSense system is definitely sending the router 
advertisements and they’re definitely reaching the OS X system:

 sudo tcpdump - -i en0 ip6
tcpdump: listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes
21:45:00.342737 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 112) 
fe80::1:1  ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 112
hop limit 64, Flags [other stateful], pref medium, router lifetime 30s, 
reachable time 0s, retrans time 0s
  prefix info option (3), length 32 (4): 2601:8:9a80:69d::/64, Flags 
[onlink, auto, router], valid time 86400s, pref. time 14400s
0x:  40e0 0001 5180  3840   2601
0x0010:  0008 9a80 069d    
  rdnss option (25), length 24 (3):  lifetime 10s, addr: 
2601:8:9a80:69d:20d:b9ff:fe34:c61a
0x:    000a 2601 0008 9a80 069d 020d
0x0010:  b9ff fe34 c61a
  unknown option (31), length 24 (3):
0x:    000a 086a 6561 6d6c 616e 6403
0x0010:  6e65 7400 
  mtu option (5), length 8 (1):  1500
0x:    05dc
  source link-address option (1), length 8 (1): 00:0d:b9:34:c6:1a
0x:  000d b934 c61a

Any ideas where I’d go from here?

Many thanks,
Benno.



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list