Messages

1

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: January 11, 2019, 09:44:44 am »

As I have another APU around, with Realtek nics, I've switched to it and tried.
I don't see any error on serial console, but the APU hangs and becomes unreachable. So different behaviour, but same result.
Thank you.

2

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: January 11, 2019, 08:38:48 am »

Thank you everybody.
Yes, it is stock opnsense kernel, so I guess stock FreeBSD driver. The device is a APU2C4 with Intel NICs

3

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: January 09, 2019, 10:42:30 am »

Thank you. Actually everything was ok except sticky connections.
Unfortunately, it didn't help. Here's what appears on console, then the APU hangs:

Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80c2f323
stack pointer           = 0x28:0xfffffe0120f9f5e0
frame pointer           = 0x28:0xfffffe0120f9f620
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 31763 (dpinger)

4

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: January 08, 2019, 07:49:28 pm »

It didn't work. As soon as I unplug one of the wans, the system hangs

5

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: January 08, 2019, 03:40:40 pm »

Yes, I had that checked. Now I tried to uncheck it and see what happens. Thank you, I will report here ASAP

6

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: January 08, 2019, 12:07:43 pm »

Hello everybody,
still having the same problem. This morning one of my two Wans is flappy and, from time to time, the pppoe connection disappears (it's a wireless provider). If this down lasts for more than one or two minutes, the entire opnsense hangs and I have to manually restart the APU, otherwise it continues to be stuck there.

Is there anything I can do/try to avoid this? It's not a big issue when I'm here, but quite strong when away and the APU stays blocked for days.

Thank you!

7

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: October 12, 2018, 07:05:58 pm »

Hello,
sorry for the long delay, strong flu here.

I just tested a new installation  from ISO and a restore from the backup. No updates. Same result.

Thank you.

8

18.7 Legacy Series / Re: Kernel panic when unplugging WAN network interface

« on: October 04, 2018, 12:55:42 pm »

I haven't tried, yet. I'll be trying as soon as possibile.
Do you mean also re-importing  configurations from the backup?

Thank you

9

18.7 Legacy Series / Kernel panic when unplugging WAN network interface

« on: October 01, 2018, 02:15:38 pm »

Hello everybody, I've been using opnsense for 9 months now. Before last week, all it was doing was just a multi-wan gateway and firewall, but now I'm implementing some more advanced configurations (like ipv6, zerotier, etc.).
Performing some tests, I've noticed that unplugging of my two wan interfaces (both of them show the same problem) I hit a kernel panic and everything hangs. Sometimes it reboots, sometimes it just sits and stops working.
Both of my wans are connected via PPPoE (one is a wlan connection, the other an ADSL) and this is the error I get:

Code: [Select]

Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address   = 0x0
fault code              = supervisor read data, page not present
instruction pointer     = 0x20:0xffffffff80c2ab63
stack pointer           = 0x28:0xfffffe011abf2f60
frame pointer           = 0x28:0xfffffe011abf2f70
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 12 (irq259: igb0:que 3)

I've also tried to follow this, but no luck:
https://www.netgate.com/docs/pfsense/hardware/tuning-and-troubleshooting-network-cards.html#Intel_igb.284.29_and_em.284.29_Cards

What could it be? Searching on the forum I've found some similar posts, related to PPPoE Wan devices, but I read things should have been fixed long ago. My opnsense version is OPNsense 18.7.4-amd64 - FreeBSD 11.1 RELEASE-p14 - LibreSSL 2.7.4
Thank you
Stefano

10

General Discussion / MPD5 multilink ppp using different connections

« on: March 04, 2018, 09:33:58 am »

Hello everyone, I've switched from PFSense to OPNsense some months ago and I'm not going to look back. Multi wan works a lot better here, as PFSense didn't often re-enable a gateway after being put down because of latency or packet loss. OPNSense is great.

There's something I'd like to implement here: I've two connections, one is 30 MBit/sec but its speed is unreliable (goes from 1 Mbit to 30 Mbit according to weather (it's a Wireless connection) and external traffic), the other one is an ADSL connection, more or less 4/5 Mbit/sec, quite stable in speed. At the moment, I've gateway switching for high latency and it works, but it's suboptimal. Weighted gateway distribution is out of question as the first connection is unreliable in speed.

Some years ago, something like in 2010, I experimented an interesting setup in FreeBSD: using mpd5 I have been able to create a multilink ppp tunnel using the two connections. The first one was always active while the second one got fired up as soon as latency went over a specific threshold. As a result, I could combine both of them when needed, while using just one when latency was low.

This kind of setup would be great here: when the unreliable connection is at 30Mbit/sec, the second one would be more or less "spare" (unless I start to download a big file), but when it's at 1 Mbit, the second one would stay up and take the biggest part of the traffic as the latency would otherwise be high.

Is there a way to achieve it in OPNSense? I know I can start using the configuration files manually, as I do in FreeBSD, but I'd prefer to keep it "OPNSense way". Thank you!