[SOLVED] pfSense SG-1000 lan-interface missing IP with snapshot 20171007

bastolino · Oct 8, 2017, 9:15 AM

Hi everyone,

I have an issue with the current snapshot. After upgrading, the LAN-interface did not respond to any IP address. Connecting via USB-Cable to console has no other effect.
Neither re-assignment of the interfaces, of the IP-addresses, resetting to factory defaults did change the behaviour.
A hardware-failure can be spaced out as changing WAN/LAN-interfaces on hardware-level worked in a way that the (new) WAN-Interface (which is the default LAN-Interface) received an IP-address.
[Remark: WAN: DHCPv4-Client; LAN: IPv4 static; DHCPv4-Server]

At the moment I do not know how to resolve that, I think this is a bug. Can someone confirm that?
Otherwise I will open a bugreport.

Best wishes

Basti

seanr22a · Oct 8, 2017, 9:53 AM

2.4.0.r.20171007.1416 no good. Stupid as I am I upgraded two firewalls at the same time. Non of them come up again. Now 50 minutes later it's still saying retrying another xx seconds. It's one SG2440 and one SG8860.

[EDIT] this is the upgrade log - looks normal to me
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pfSense-kernel-pfSense: 2.4.0.r.20171006.2203 -> 2.4.0.r.20171007.1416 [pfSense-core]
pfSense-rc: 2.4.0.r.20171006.2203 -> 2.4.0.r.20171007.1416 [pfSense-core]

Number of packages to be upgraded: 2
[1/2] Upgrading pfSense-rc from 2.4.0.r.20171006.2203 to 2.4.0.r.20171007.1416…
[1/2] Extracting pfSense-rc-2.4.0.r.20171007.1416: ….. done
[2/2] Upgrading pfSense-kernel-pfSense from 2.4.0.r.20171006.2203 to 2.4.0.r.20171007.1416…
[2/2] Extracting pfSense-kernel-pfSense-2.4.0.r.20171007.1416: …....... done
===> Keeping a copy of current kernel in /boot/kernel.old
Upgrade is complete. Rebooting in 10 seconds.
Success

iculookn · Oct 8, 2017, 11:10 AM

Yep, same with me. Cant get to lan interface.

Can get to console via serial. lan is set to 10.0.0.1. trying to use "set interfaces IP address" to set it to another ip does not work.

Can we restore previous build from the console?

stephenw10 · Oct 8, 2017, 11:44 AM

Looks like an error crept in with a revision we made to address something else.

We have removed that snapshot from the repos now. New snaps should be up later. Until then use a snap from Oct 6th or earlier.

Steve

iculookn · Oct 8, 2017, 11:46 AM

are you able to explain how to go back to the Oct 6th snapshot from the console?

Thanks

seanr22a · Oct 8, 2017, 11:51 AM

@iculookn:

are you able to explain how to go back to the Oct 6th snapshot from the console?

Thanks

I want to know too … tried to search but didn't find anything. It says it saves the old kernel but what is the procedure to get it back ?

Grimson · Oct 8, 2017, 12:15 PM

Do a fresh install and restore your config backup.

iculookn · Oct 8, 2017, 12:34 PM

so this?
https://doc.pfsense.org/index.php/Upgrading_via_Shell_(old)

from console, option 8
fetch -o /root/firmware.tgz https://snapshots.pfsense.org/amd64/pfSense_RELENG_2_4_0/installer/pfSense-CE-memstick-serial-2.4.0-RC-amd64-20171006-1536.img.gz

then
/etc/rc.firmware pfSenseupgrade /root/firmware.tgz

Then once in webgui, Diagnostics, Backup/Restore -> Config History

Yes?

stephenw10 · Oct 8, 2017, 12:54 PM

No you can't do that. No such image exists for SG-1000 (ARMv6).

We have just replaced the image available at the support portal with the Oct 6th recover image:
https://portal.pfsense.org/firmware/sg-1000/pfSense-netgate-uFW-recover-2.4.0-RC-arm-latest.img.gz

By far the easiest way is to reinstall using that image right now.

When the pkg repos are rebuilt with good images you should be able to update to that from the console assuming the device has WAN connectivity.

Steve

iculookn · Oct 8, 2017, 12:56 PM

I have SG-4860?

stephenw10 · Oct 8, 2017, 1:22 PM

Ah, I'm sorry, thread title threw me!

In that case you can access the snapshots directly but you would need to use the ADI image for the 4860:
https://snapshots.pfsense.org/amd64/pfSense_RELENG_2_4_0/installer/pfSense-CE-memstick-ADI-2.4.0-RC-amd64-20171006-1536.img.gz

You would still need to reinstall from that image though. You can't run the firmware update from an offline upgrade image as described in that doc unless you're running 2.2.X or earlier.

However if you're running CE new snaps are up now so you can try updating directly from the console.

Steve

iculookn · Oct 8, 2017, 1:44 PM

ok thanks, yeah I just saw the new snaps, but if I try to update via the console (option 13) I get the following errors

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_0_amd64-core/meta.txz: Not Found
repository pfSense-core has no meta file, using default settings
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_0_amd64-core/packagesite.txz: Not Found
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_0_amd64-pfSense_factory-v2_4_0/meta.txz: Not Found
repository pfSense has no meta file, using default settings
pkg: https://firmware.netgate.com/pkg/pfSense_factory-v2_4_0_amd64-pfSense_factory-v2_4_0/packagesite.txz: Not Found
Unable to update repository pfSense
Error updating repositories!
Netgate SG-4860

iculookn · Oct 8, 2017, 1:55 PM

oh, I think I need to wait till the FACTORY versions are ready?

cat /usr/local/etc/pkg/repos/pfSense.conf
FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+https://firmware.netgate.com/pkg/pfSense_factory-v2_4_0_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+https://firmware.netgate.com/pkg/pfSense_factory-v2_4_0_amd64-pfSense_factory-v2_4_0",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

Grimson · Oct 8, 2017, 2:22 PM

Keep your hands away from x86 CE build 2.4.0.r.20171008.0625 IPv4 is broken in it you can't even assign an IPv4 address to an interface with it.

stephenw10 · Oct 8, 2017, 2:48 PM

Yes, you won't be able to see that until the factory repos are updated.

Thanks for the feedback on 2.4.0.r.20171008.0625 :-\

Steve

Grimson · Oct 8, 2017, 3:02 PM

Build 2.4.0.r.20171008.0640 seems to be working fine now.

Edit: It seems this build has problems with traffic shaping, I'm using HFSC queues but Status -> Queues can't find any statistics. Ping seems to suffer under traffic so it seems the queues aren't working at all.

stephenw10 · Oct 8, 2017, 3:12 PM

Yes I just installed .640 and it seemed to run OK. I am certainly able to assign IPs to interfaces.

If you run:

pfctl -f /tmp/rules.debug

Does it return clean or with any errors?

Steve

Grimson · Oct 8, 2017, 3:16 PM

Sorry, I already went back to build 2.4.0.r.20171006.1536 as I need traffic shaping to keep my rather slow DSL connection in a decent state (see my edit above).

stephenw10 · Oct 8, 2017, 3:20 PM

Ok, no problem.

I ran the shaping wizard and setup queues using both PRIQ and HSFC and they came up as expected.

If you see it again try to grab whatever data you can get. Reload the ruleset manually as shown above. Open a bug report.

Steve

kpa · Oct 8, 2017, 4:32 PM

Logging is broken on 2.4.0-RC-amd64-20171008-0640. This is a clean install on ZFS with the configuration restored after first boot:


Starting syslog...done.
Oct  8 18:26:24  syslogd: /var/log/routing.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/ntpd.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/gateways.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/resolver.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/dhcpd.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/filter.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/nginx.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/dhcpd.log: Operation not supported by device
Oct  8 18:26:24  syslogd: /var/log/system.log: Operation not supported by device

The system works otherwise but no logs are shown in the webgui.

I have already tried reset logs but no difference.