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

iculookn

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

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

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

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

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

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

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

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.

kpa

Another full reinstall, this time using the config rescue option. No difference, syslogd still spits out the same errors.

lololo

@kpa:

Another full reinstall, this time using the config rescue option. No difference, syslogd still spits out the same errors.

Same problem… clean install on a vm
Have you found a solution?

kpa

@lololo:

@kpa:

Another full reinstall, this time using the config rescue option. No difference, syslogd still spits out the same errors.

Same problem… clean install on a vm
Have you found a solution?

Upgrade to the 2.4 release version and reset your log files.

bastolino

Hi Guys
Thank you for that fix - I honestly thought I made a brick :o

Best wishes
Bastolino