[pfSense] pfsense ipv6 not working

[Eero Volotinen]

Hi List,

Running ipv6 with dhcpv6 from isp and it works on my laptop without pfsense,
but on pfsense shell, I cannot even ping other network addresses that gw:

ping6 fe80::208:20ff:fe4e:1c1b

PING6(56=40+8+8 bytes) fe80::ae1f:6bff:fe43:a993%igb3 -->
fe80::208:20ff:fe4e:1c1b

16 bytes from fe80::208:20ff:fe4e:1c1b%igb3, icmp_seq=0 hlim=64 time=0.573
ms

16 bytes from fe80::208:20ff:fe4e:1c1b%igb3, icmp_seq=2 hlim=64 time=0.578
ms

16 bytes from fe80::208:20ff:fe4e:1c1b%igb3, icmp_seq=3 hlim=64 time=0.518
ms


and when trying to ping google:



ping6 2a00:1450:4001:820::200e

PING6(56=40+8+8 bytes) fe80::ae1f:6bff:fe43:a993%igb3 -->
2a00:1450:4001:820::200e

^C

--- 2a00:1450:4001:820::200e ping6 statistics ---

7 packets transmitted, 0 packets received, 100.0% packet loss

Wan configuration is using DHCPv6

--
Eero
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.4 consistently crashes daily

[WebDawg]

It should work though.  A great many people virtualize pfSense:

https://doc.pfsense.org/index.php/PfSense_on_VMware_vSphere_/_ESXi

Here is some more information:

https://doc.pfsense.org/index.php/VirtIO_Driver_Support
https://doc.pfsense.org/index.php/Lost_Traffic_/_Packets_Disappear
https://doc.pfsense.org/index.php/Virtualizing_pfSense_on_Proxmox

I know what it is like to ask for support and see people stop helping
because something is virtualized.  I have seen bad code fail in
virtualization situations only to here 'do not virtualize'.

>From what I know, BSD has trouble with NIC interfaces and such.  Do
you have any limiters or QOS installed?  I would take a look at the
nic interfaces first.  Can you actively monitor the log to look for
errors once the VM is booted?

I virtualized pfSense on proxmox about a year ago and BSD hated the
cpu timers and such.  I would get so many issues from it until I
figured it out but everything was plain as day in the kernel messages
that were outputted.

There is an ova file available via the gold subscription:

https://doc.pfsense.org/index.php/VMware_Appliance

You need to get more information for me to help further.  It would be
great to get a copy of some logs.

Here is a XenServer thread:  https://forum.pfsense.org/index.php?topic=88467

Last time I virtualized the big deal was hvm nic vs pvhvm NIC.  You
could do limiters on one (I think hvm) but the NIC's become CPU bound
because of how HVM works.  I could only push like 10-30 mbits out of
an i3 processor.

I do not know if this has been solved, or if it is solvable.  pfSense
follows FreeBSD so most of the fixes for this come from FreeBSD,
though pfSense had/has some of its own kernel hacks.



On Mon, Nov 20, 2017 at 10:58 AM, Vick Khera  wrote:
> Oh, so you're not running it on hardware, but inside ESXi? Then I have no
> more ideas for you. You should mention these things when asking for help,
> by the way.
>
>
> On Mon, Nov 20, 2017 at 8:12 AM, Liwei  wrote:
>
>> Thanks for the quick reply. It is a Supermicro 5018A-FTN4 based on
>> the A1SRi-2758F which contains an Atom C2758. RAM tests are fine. This
>> machine also contains a few other VMs which are running fine.
>>
>> By the way, I missed out reporting the crash itself:
>>
>> Fatal trap 12: page fault while in kernel mode
>> cpuid = 2; apic id = 02
>> fault virtual address = 0x60
>> fault code = supervisor read data, page not present
>> instruction pointer = 0x20:0x80cbcb0f
>> stack pointer = 0x28:0xfe02390bf070
>> frame pointer = 0x28:0xfe02390bf070
>> code segment = base 0x0, limit 0xf, type 0x1b
>> = DPL 0, pres 1, long 1, def32 0, gran 1
>> processor eflags = interrupt enabled, resume, IOPL = 0
>> current process = 12 (irq267: vmx0)
>>
>> On Mon, 20 Nov 2017 at 20:55 Vick Khera  wrote:
>>
>> > On Mon, Nov 20, 2017 at 7:36 AM, Liwei  wrote:
>> >
>> > >
>> > > Anyone has any idea what's going on? Restoring to pfSense 2.3 seems
>> > to
>> > > solve this problem, so it is more likely a software than hardware
>> issue.
>> > >
>> > >
>> > What's your hardware? Have you tested your RAM using memtest86?
>> > ___
>> > pfSense mailing list
>> > https://lists.pfsense.org/mailman/listinfo/list
>> > Support the project with Gold! https://pfsense.org/gold
>> >
>> --
>> Clear Skies,LiweiCo-Founder, CTO
>>
>> TinyMOS
>>
>>
>>  
>>  
>>
>> 21 Heng Mui Keng Terrace, Level 1 The Hangar, Singapore 119613
>> ___
>> pfSense mailing list
>> https://lists.pfsense.org/mailman/listinfo/list
>> Support the project with Gold! https://pfsense.org/gold
>>
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.4 consistently crashes daily

[Vick Khera]

Oh, so you're not running it on hardware, but inside ESXi? Then I have no
more ideas for you. You should mention these things when asking for help,
by the way.


On Mon, Nov 20, 2017 at 8:12 AM, Liwei  wrote:

> Thanks for the quick reply. It is a Supermicro 5018A-FTN4 based on
> the A1SRi-2758F which contains an Atom C2758. RAM tests are fine. This
> machine also contains a few other VMs which are running fine.
>
> By the way, I missed out reporting the crash itself:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 2; apic id = 02
> fault virtual address = 0x60
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0x80cbcb0f
> stack pointer = 0x28:0xfe02390bf070
> frame pointer = 0x28:0xfe02390bf070
> code segment = base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 12 (irq267: vmx0)
>
> On Mon, 20 Nov 2017 at 20:55 Vick Khera  wrote:
>
> > On Mon, Nov 20, 2017 at 7:36 AM, Liwei  wrote:
> >
> > >
> > > Anyone has any idea what's going on? Restoring to pfSense 2.3 seems
> > to
> > > solve this problem, so it is more likely a software than hardware
> issue.
> > >
> > >
> > What's your hardware? Have you tested your RAM using memtest86?
> > ___
> > pfSense mailing list
> > https://lists.pfsense.org/mailman/listinfo/list
> > Support the project with Gold! https://pfsense.org/gold
> >
> --
> Clear Skies,LiweiCo-Founder, CTO
>
> TinyMOS
>
>
>  
>  
>
> 21 Heng Mui Keng Terrace, Level 1 The Hangar, Singapore 119613
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.4 consistently crashes daily

[Liwei]

ESXi 6.5
On Mon, 20 Nov 2017 at 22:04 WebDawg  wrote:

> What virt software?
>
> On Mon, Nov 20, 2017 at 7:12 AM, Liwei  wrote:
> > Thanks for the quick reply. It is a Supermicro 5018A-FTN4 based on
> > the A1SRi-2758F which contains an Atom C2758. RAM tests are fine. This
> > machine also contains a few other VMs which are running fine.
> >
> > By the way, I missed out reporting the crash itself:
> >
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 2; apic id = 02
> > fault virtual address = 0x60
> > fault code = supervisor read data, page not present
> > instruction pointer = 0x20:0x80cbcb0f
> > stack pointer = 0x28:0xfe02390bf070
> > frame pointer = 0x28:0xfe02390bf070
> > code segment = base 0x0, limit 0xf, type 0x1b
> > = DPL 0, pres 1, long 1, def32 0, gran 1
> > processor eflags = interrupt enabled, resume, IOPL = 0
> > current process = 12 (irq267: vmx0)
> >
> > On Mon, 20 Nov 2017 at 20:55 Vick Khera  wrote:
> >
> >> On Mon, Nov 20, 2017 at 7:36 AM, Liwei  wrote:
> >>
> >> >
> >> > Anyone has any idea what's going on? Restoring to pfSense 2.3
> seems
> >> to
> >> > solve this problem, so it is more likely a software than hardware
> issue.
> >> >
> >> >
> >> What's your hardware? Have you tested your RAM using memtest86?
> >> ___
> >> pfSense mailing list
> >> https://lists.pfsense.org/mailman/listinfo/list
> >> Support the project with Gold! https://pfsense.org/gold
> >>
> > --
> > Clear Skies,LiweiCo-Founder, CTO
> >
> > TinyMOS
> >
> >
> >  
> >  
> >
> > 21 Heng Mui Keng Terrace, Level 1 The Hangar, Singapore 119613
> > ___
> > pfSense mailing list
> > https://lists.pfsense.org/mailman/listinfo/list
> > Support the project with Gold! https://pfsense.org/gold
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.4 consistently crashes daily

[WebDawg]

What virt software?

On Mon, Nov 20, 2017 at 7:12 AM, Liwei  wrote:
> Thanks for the quick reply. It is a Supermicro 5018A-FTN4 based on
> the A1SRi-2758F which contains an Atom C2758. RAM tests are fine. This
> machine also contains a few other VMs which are running fine.
>
> By the way, I missed out reporting the crash itself:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 2; apic id = 02
> fault virtual address = 0x60
> fault code = supervisor read data, page not present
> instruction pointer = 0x20:0x80cbcb0f
> stack pointer = 0x28:0xfe02390bf070
> frame pointer = 0x28:0xfe02390bf070
> code segment = base 0x0, limit 0xf, type 0x1b
> = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 12 (irq267: vmx0)
>
> On Mon, 20 Nov 2017 at 20:55 Vick Khera  wrote:
>
>> On Mon, Nov 20, 2017 at 7:36 AM, Liwei  wrote:
>>
>> >
>> > Anyone has any idea what's going on? Restoring to pfSense 2.3 seems
>> to
>> > solve this problem, so it is more likely a software than hardware issue.
>> >
>> >
>> What's your hardware? Have you tested your RAM using memtest86?
>> ___
>> pfSense mailing list
>> https://lists.pfsense.org/mailman/listinfo/list
>> Support the project with Gold! https://pfsense.org/gold
>>
> --
> Clear Skies,LiweiCo-Founder, CTO
>
> TinyMOS
>
>
>  
>  
>
> 21 Heng Mui Keng Terrace, Level 1 The Hangar, Singapore 119613
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.4 consistently crashes daily

[Liwei]

Thanks for the quick reply. It is a Supermicro 5018A-FTN4 based on
the A1SRi-2758F which contains an Atom C2758. RAM tests are fine. This
machine also contains a few other VMs which are running fine.

By the way, I missed out reporting the crash itself:

Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0x60
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x80cbcb0f
stack pointer = 0x28:0xfe02390bf070
frame pointer = 0x28:0xfe02390bf070
code segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 12 (irq267: vmx0)

On Mon, 20 Nov 2017 at 20:55 Vick Khera  wrote:

> On Mon, Nov 20, 2017 at 7:36 AM, Liwei  wrote:
>
> >
> > Anyone has any idea what's going on? Restoring to pfSense 2.3 seems
> to
> > solve this problem, so it is more likely a software than hardware issue.
> >
> >
> What's your hardware? Have you tested your RAM using memtest86?
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
>
-- 
Clear Skies,LiweiCo-Founder, CTO

TinyMOS


 
 

21 Heng Mui Keng Terrace, Level 1 The Hangar, Singapore 119613
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] pfSense 2.4 consistently crashes daily

[Vick Khera]

On Mon, Nov 20, 2017 at 7:36 AM, Liwei  wrote:

>
> Anyone has any idea what's going on? Restoring to pfSense 2.3 seems to
> solve this problem, so it is more likely a software than hardware issue.
>
>
What's your hardware? Have you tested your RAM using memtest86?
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] pfSense 2.4 consistently crashes daily

[Liwei]

Hi list,
I upgraded to pfSense 2.4.1 (from 2.3) recently, and ever since the
upgrade, the machine has been crashing multiple times daily. Here's a list
of Dumptimes extracted from the bug reporting module:

Line 20:   Dumptime: Thu Nov 16 19:59:59 2017
Line 36:   Dumptime: Thu Nov 16 20:02:04 2017
Line 52:   Dumptime: Sat Nov 18 19:11:50 2017
Line 68:   Dumptime: Sat Nov 18 20:06:03 2017
Line 84:   Dumptime: Sat Nov 18 20:08:33 2017
Line 100:   Dumptime: Sat Nov 18 20:10:41 2017
Line 116:   Dumptime: Sat Nov 18 20:12:57 2017
Line 132:   Dumptime: Sat Nov 18 20:18:13 2017
Line 148:   Dumptime: Sat Nov 18 20:20:51 2017
Line 164:   Dumptime: Sat Nov 18 22:13:42 2017
Line 180:   Dumptime: Sun Nov 19 00:01:08 2017
Line 196:   Dumptime: Sun Nov 19 09:14:27 2017
Line 212:   Dumptime: Thu Nov 16 20:04:19 2017
Line 228:   Dumptime: Sun Nov 19 12:24:57 2017
Line 244:   Dumptime: Sun Nov 19 19:00:57 2017
Line 260:   Dumptime: Sun Nov 19 19:16:59 2017
Line 276:   Dumptime: Sun Nov 19 19:19:04 2017
Line 292:   Dumptime: Sun Nov 19 19:21:34 2017
Line 308:   Dumptime: Sun Nov 19 19:31:04 2017
Line 324:   Dumptime: Sun Nov 19 20:19:43 2017
Line 340:   Dumptime: Sun Nov 19 21:19:33 2017
Line 356:   Dumptime: Sun Nov 19 21:55:31 2017
Line 372:   Dumptime: Mon Nov 20 18:52:17 2017
Line 388:   Dumptime: Thu Nov 16 20:08:31 2017
Line 404:   Dumptime: Mon Nov 20 18:54:32 2017
Line 420:   Dumptime: Mon Nov 20 18:57:50 2017

As you can see, it seems to occur around 7 to 8pm (GMT+8) daily and
occurs in rapid succession. There are exceptions though (e.g. the crashes
that happened at midnight, 9am and 1pm above). Eventually it does stabilise
and things appear well for another 24 hours or so.

Looking through the dumps, the backtrace is always this:

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100085 td 0xf80006613560
strlen() at strlen+0x1f/frame 0xfe02390bf070
kvprintf() at kvprintf+0x93c/frame 0xfe02390bf160
vlog() at vlog+0x9b/frame 0xfe02390bf240
log() at log+0x3f/frame 0xfe02390bf2a0
ip6_forward() at ip6_forward+0xc5/frame 0xfe02390bf3f0
pf_refragment6() at pf_refragment6+0x17a/frame 0xfe02390bf4b0
pf_test6() at pf_test6+0x2176/frame 0xfe02390bf710
pf_check6_out() at pf_check6_out+0x1d/frame 0xfe02390bf730
pfil_run_hooks() at pfil_run_hooks+0x7b/frame 0xfe02390bf7c0
bridge_pfil() at bridge_pfil+0x61b/frame 0xfe02390bf850
bridge_broadcast() at bridge_broadcast+0x249/frame 0xfe02390bf8c0
bridge_forward() at bridge_forward+0x23b/frame 0xfe02390bf920
bridge_input() at bridge_input+0x2bd/frame 0xfe02390bf990
ether_nh_input() at ether_nh_input+0x292/frame 0xfe02390bf9f0
netisr_dispatch_src() at netisr_dispatch_src+0xa0/frame 0xfe02390bfa40
ether_input() at ether_input+0x26/frame 0xfe02390bfa60
vmxnet3_rxq_eof() at vmxnet3_rxq_eof+0x811/frame 0xfe02390bfae0
vmxnet3_legacy_intr() at vmxnet3_legacy_intr+0xf1/frame 0xfe02390bfb20
intr_event_execute_handlers() at intr_event_execute_handlers+0xec/frame
0xfe02390bfb60
ithread_loop() at ithread_loop+0xd6/frame 0xfe02390bfbb0
fork_exit() at fork_exit+0x85/frame 0xfe02390bfbf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfe02390bfbf0

While it takes less than a minute for pfSense to reboot, the frequency
of it happening is starting to become a big nuisance.

Anyone has any idea what's going on? Restoring to pfSense 2.3 seems to
solve this problem, so it is more likely a software than hardware issue.

Warm regards,
Liwei
-- 
Clear Skies,LiweiCo-Founder, CTO

TinyMOS


 
 

21 Heng Mui Keng Terrace, Level 1 The Hangar, Singapore 119613
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold