Re: [pfSense] USB3 to ethernet adaptor
As a general note, I have had trouble with them if I run the adapter through a USB3 hub and then connect to an Ethernet cable. The system would periodically kernel panic and once I plugged it directly into the USB3 slot on the box, then the problems went away. On Mon, May 02, 2016 at 09:56:49AM +0200, Frans Meulenbroeks wrote: > Hi, > > Has anyone experience using USB3 to ethernet adapters ? I need an extra > interface but my HW (Intel NUC) does not have room for another card). > Anything recommendable? > > Best regards, Frans. > ___ > 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] 2.3_1 ?
It will restart on its own Sent from my Sprint Samsung Galaxy S7. Original message From: Bob Gustafson Date: 5/5/16 4:36 PM (GMT-06:00) To: Larry Rosenman Cc: pfSense Support and Discussion Mailing List Subject: Re: [pfSense] 2.3_1 ? On 05/05/2016 03:13 PM, Larry Rosenman wrote: > On 2016-05-05 15:11, Bob Gustafson wrote: >> On 05/05/2016 02:35 PM, Larry Rosenman wrote: >> >>> On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: >> On May 5, 2016, at 6:26 AM, Paul Mather >> wrote: >> >> On May 5, 2016, at 9:13 AM, Vick Khera wrote: >> >>> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland >>> wrote: >>> Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. >>> I just did the upgrade and it succeeded. However, ntpd was not >>> restarted on >>> either of the two systems upgraded. I had to manually restart ntpd. >> >> Same here. In fact, in my case, ntpd ended up in the stopped >> state, and I had to start it manually. > it’s documented that you need to (re)start NTP manually. > I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? >>> 2.3 to 2.3_1 is NO reboot. >>> >> What does "2.3 to 2.3_1 is NO reboot" mean? >> >> Does it mean that even through power failures, the little pfSense >> soldiers on - pinging ntp even without power? > No, the upgrade from 2.3 to 2.3_1 does *NOT* force a reboot. > > You just need to restart the ntpd service. I'm sorry to be so dense on this subject... My question assumes that the box *has been upgraded* to 2.3_1 - perhaps yesterday. And nptd has been started just after the upgrade. Along comes a power failure. Then the power is restored to the box. When the pfSense within the box is running, is the ntpd running, or does it (again) need to be restarted manually? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 05/05/2016 03:13 PM, Larry Rosenman wrote: On 2016-05-05 15:11, Bob Gustafson wrote: On 05/05/2016 02:35 PM, Larry Rosenman wrote: On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. What does "2.3 to 2.3_1 is NO reboot" mean? Does it mean that even through power failures, the little pfSense soldiers on - pinging ntp even without power? No, the upgrade from 2.3 to 2.3_1 does *NOT* force a reboot. You just need to restart the ntpd service. I'm sorry to be so dense on this subject... My question assumes that the box *has been upgraded* to 2.3_1 - perhaps yesterday. And nptd has been started just after the upgrade. Along comes a power failure. Then the power is restored to the box. When the pfSense within the box is running, is the ntpd running, or does it (again) need to be restarted manually? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 2016-05-05 15:11, Bob Gustafson wrote: On 05/05/2016 02:35 PM, Larry Rosenman wrote: On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. What does "2.3 to 2.3_1 is NO reboot" mean? Does it mean that even through power failures, the little pfSense soldiers on - pinging ntp even without power? No, the upgrade from 2.3 to 2.3_1 does *NOT* force a reboot. You just need to restart the ntpd service. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On Thu, May 5, 2016 at 3:11 PM, Bob Gustafson wrote: > On 05/05/2016 02:35 PM, Larry Rosenman wrote: > >> On 2016-05-05 14:23, Bob Gustafson wrote: >>> >>> On 05/05/2016 02:05 PM, Jim Thompson wrote: > > On May 5, 2016, at 6:26 AM, Paul Mather > wrote: > > On May 5, 2016, at 9:13 AM, Vick Khera wrote: > >> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: >> >>> Does this update actually work? >>> >>> After hitting install and crunching for a while, it showed "firmware >>> installation failed!" at the top. >>> >> I just did the upgrade and it succeeded. However, ntpd was not >> restarted on >> either of the two systems upgraded. I had to manually restart ntpd. > > > Same here. In fact, in my case, ntpd ended up in the stopped state, > and I had to start it manually. it’s documented that you need to (re)start NTP manually. >>> I haven't yet upgraded to 2.3+ >>> >>> My question is whether ntpd is dead on every reboot of pfSense, or >>> just the one after upgrading? >> >> 2.3 to 2.3_1 is NO reboot. >> > What does "2.3 to 2.3_1 is NO reboot" mean? > That doing the upgrade from 2.3 to 2.3_1 doesn't reboot the system. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 05/05/2016 02:35 PM, Larry Rosenman wrote: On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. What does "2.3 to 2.3_1 is NO reboot" mean? Does it mean that even through power failures, the little pfSense soldiers on - pinging ntp even without power? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 2016-05-05 14:23, Bob Gustafson wrote: On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? 2.3 to 2.3_1 is NO reboot. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On 05/05/2016 02:05 PM, Jim Thompson wrote: On May 5, 2016, at 6:26 AM, Paul Mather wrote: On May 5, 2016, at 9:13 AM, Vick Khera wrote: On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. it’s documented that you need to (re)start NTP manually. I haven't yet upgraded to 2.3+ My question is whether ntpd is dead on every reboot of pfSense, or just the one after upgrading? ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
> On May 5, 2016, at 6:26 AM, Paul Mather wrote: > > On May 5, 2016, at 9:13 AM, Vick Khera wrote: > >> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: >> >>> Does this update actually work? >>> >>> After hitting install and crunching for a while, it showed "firmware >>> installation failed!" at the top. >>> >> >> I just did the upgrade and it succeeded. However, ntpd was not restarted on >> either of the two systems upgraded. I had to manually restart ntpd. > > > Same here. In fact, in my case, ntpd ended up in the stopped state, and I > had to start it manually. it’s documented that you need to (re)start NTP manually. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On Thu, May 5, 2016 at 9:47 AM, Jeppe Øland wrote: > This install is running a 4G NANO image ... maybe there's a problem with > that? > I just did the update on a nano image system (netgate, not vanilla pfsense) and had success other than having to manually restart ntpd. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On May 5, 2016, at 9:47 AM, Jeppe Øland wrote: > So the update failed, and pfSense still says 2.3 - but NTP was indeed > updated (but not restarted). > > I then tried installing the RRD_Summary package. > That one also said it failed, but still completed enough that the menu > appeared and worked. > > I forget if it said "failed" when I uninstalled it again ... probably did. > > This install is running a 4G NANO image ... maybe there's a problem with > that? FWIW, the system I updated is a 4G NANO install (amd64). The update status shows it is at version 2.3_1 after the update. The only issue I encountered is ntpd being stopped and having to start it manually. Cheers, Paul. > > Regards, > -Jeppe > > On Thu, May 5, 2016 at 6:26 AM, Paul Mather wrote: > >> On May 5, 2016, at 9:13 AM, Vick Khera wrote: >> >>> On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: >>> Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top. >>> >>> I just did the upgrade and it succeeded. However, ntpd was not restarted >> on >>> either of the two systems upgraded. I had to manually restart ntpd. >> >> >> Same here. In fact, in my case, ntpd ended up in the stopped state, and I >> had to start it manually. >> >> Cheers, >> >> Paul. >> >> ___ >> 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] 2.3_1 ?
So the update failed, and pfSense still says 2.3 - but NTP was indeed updated (but not restarted). I then tried installing the RRD_Summary package. That one also said it failed, but still completed enough that the menu appeared and worked. I forget if it said "failed" when I uninstalled it again ... probably did. This install is running a 4G NANO image ... maybe there's a problem with that? Regards, -Jeppe On Thu, May 5, 2016 at 6:26 AM, Paul Mather wrote: > On May 5, 2016, at 9:13 AM, Vick Khera wrote: > > > On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: > > > >> Does this update actually work? > >> > >> After hitting install and crunching for a while, it showed "firmware > >> installation failed!" at the top. > >> > > > > I just did the upgrade and it succeeded. However, ntpd was not restarted > on > > either of the two systems upgraded. I had to manually restart ntpd. > > > Same here. In fact, in my case, ntpd ended up in the stopped state, and I > had to start it manually. > > Cheers, > > Paul. > > ___ > 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] kernel arpresolve: can't allocate llinfo for x.x.x.x on yy0 Issue
Hello all. I am seeing the issue below: kernel arpresolve: can't allocate llinfo for x.x.x.x on em0 The only way to resolve this issue is to bump the interface, or perform any other task in the GUI that reloads fundamental components of the interface. I've found the below links that speak to the problem, but offer no real solution: https://forum.pfsense.org/index.php?topic=63474.0 https://forum.pfsense.org/index.php/topic,62964.0.html System is running pfSense 2.3.1. The issue is affecting only one of the two interfaces. The em1 interface is Internet-facing, while the em0 interface is on a private network. I also confirm that this issue affects only IPv4. IPv6 on em0 is not affected, and IPv6 traffic continues to flow fine after the IPv4 traffic stops. I suppose it fits with the kernel error, since IPv6 uses ND in lieu of ARP. Does anyone know what this really is? All help appreciated. Mark. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On May 5, 2016, at 9:13 AM, Vick Khera wrote: > On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: > >> Does this update actually work? >> >> After hitting install and crunching for a while, it showed "firmware >> installation failed!" at the top. >> > > I just did the upgrade and it succeeded. However, ntpd was not restarted on > either of the two systems upgraded. I had to manually restart ntpd. Same here. In fact, in my case, ntpd ended up in the stopped state, and I had to start it manually. Cheers, Paul. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
Re: [pfSense] 2.3_1 ?
On Tue, May 3, 2016 at 11:24 AM, Jeppe Øland wrote: > Does this update actually work? > > After hitting install and crunching for a while, it showed "firmware > installation failed!" at the top. > I just did the upgrade and it succeeded. However, ntpd was not restarted on either of the two systems upgraded. I had to manually restart ntpd. My guess on the "pfSense" package is all that does is bump the displayed release number. ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
