Messages

1

22.7 Legacy Series / Re: Error opnsense/usr/local/etc/rc.newwanip every 2 minutes

« on: August 02, 2022, 05:20:54 am »

@Scuro do you have DHCP for your WAN and it's on interface igc0?

Yes and I had made a similar thread. https://forum.opnsense.org/index.php?topic=29571.0

The error varies between 10 minutes to an hour.

2

22.7 Legacy Series / Re: Error opnsense/usr/local/etc/rc.newwanip every 2 minutes

« on: August 02, 2022, 04:51:00 am »

You can check lease time via i.e.

# cat /var/db/dhclient.leases.igb1

I didn't have that file but I did have dhclient.leases.igc0.
Am I supposed to have 13 leases in that file all of them with the same interface and address?

I have one of these for every hour

Code: [Select]

lease {
  interface "igc0";
  fixed-address 67.###.##.35;
  option subnet-mask 255.255.252.0;
  option routers 67.###.##.1;
  option domain-name-servers 75.75.75.75,75.75.76.76;
  option host-name "scuros-fw";
  option domain-name "##.##.comcast.net.";
  option broadcast-address 255.255.255.255;
  option dhcp-lease-time 3600;
  option dhcp-message-type 5;
  option dhcp-server-identifier 96.###.###.143;
  option dhcp-renewal-time 657;
  option dhcp-rebinding-time 2700;
  renew 1 2022/8/1 19:55:10;
  rebind 1 2022/8/1 20:03:21;
  expire 1 2022/8/1 20:44:13;
}

3

22.7 Legacy Series / Re: Error opnsense/usr/local/etc/rc.newwanip every 2 minutes

« on: August 02, 2022, 04:23:24 am »

But the renewal and error happens every 2 and a half mins

That is standard behavior for DHCP. They always request renewal at half of lease.

4

22.7 Legacy Series / Re: Unbound Restarting every 2 hours after upgrade to 22.7

« on: July 30, 2022, 09:53:04 pm »

I need one info from everyone having this issue: under WAN settings, what is your IPv4 type?

IPv4 Configuration Type: DHCP

5

22.7 Legacy Series / WAN IPv4 Renewal Every Few Minutes to an Hour Since 22.7

« on: July 30, 2022, 09:11:11 pm »

It was every hour but after a reboot it has been every 10 minutes now.

No perceivable issues, just noticed when checking for errors after the update

This is what the logs look like. They keep repeating the same messages.

Code: [Select]

2022-07-30T11:52:10-07:00 Notice opnsense plugins_configure hosts (execute task : unbound_hosts_generate())
2022-07-30T11:52:10-07:00 Notice opnsense plugins_configure hosts (execute task : dnsmasq_hosts_generate())
2022-07-30T11:52:10-07:00 Notice opnsense plugins_configure hosts ()
2022-07-30T11:52:10-07:00 Error opnsense /usr/local/etc/rc.newwanip: On (IP address: 67.###.###.###) (interface: WAN[wan]) (real interface: igc0).
2022-07-30T11:52:10-07:00 Error opnsense /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'igc0'
2022-07-30T11:52:10-07:00 Notice dhclient Creating resolv.conf
2022-07-30T11:40:11-07:00 Notice opnsense plugins_configure hosts (execute task : unbound_hosts_generate())
2022-07-30T11:40:11-07:00 Notice opnsense plugins_configure hosts (execute task : dnsmasq_hosts_generate())
2022-07-30T11:40:11-07:00 Notice opnsense plugins_configure hosts ()
2022-07-30T11:40:11-07:00 Error opnsense /usr/local/etc/rc.newwanip: On (IP address: 67.###.###.###) (interface: WAN[wan]) (real interface: igc0).
2022-07-30T11:40:11-07:00 Error opnsense /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'igc0'
2022-07-30T11:40:11-07:00 Notice dhclient Creating resolv.conf
2022-07-30T10:40:11-07:00 Notice opnsense plugins_configure hosts (execute task : unbound_hosts_generate())
2022-07-30T10:40:11-07:00 Notice opnsense plugins_configure hosts (execute task : dnsmasq_hosts_generate())
2022-07-30T10:40:11-07:00 Notice opnsense plugins_configure hosts ()
2022-07-30T10:40:11-07:00 Error opnsense /usr/local/etc/rc.newwanip: On (IP address: 67.###.###.###) (interface: WAN[wan]) (real interface: igc0).
2022-07-30T10:40:11-07:00 Error opnsense /usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'igc0'
2022-07-30T10:40:11-07:00 Notice dhclient Creating resolv.conf

6

22.1 Legacy Series / Re: WAN interface flapping with 22.1.2

« on: July 14, 2022, 03:49:51 am »

My 5 port Intel I225-V box with the latest opnsense updates does not have this issue.

My 4 port I225-V b3 box is having this issue.

Details:
No spoofing, no IDS. Just IPv4, VLANS, and a weighted upload.
WAN will randomly disconnect and show the following repeated:

Code: [Select]

2022-07-13T18:03:33-07:00 Critical dhclient exiting.
2022-07-13T18:03:33-07:00 Error dhclient connection closed
2022-07-13T18:03:33-07:00 Error opnsense /usr/local/etc/rc.linkup: DEVD: Ethernet detached event for dynamic wan(igc0)

Most times it will come back up on its own, other times it will refuse to pick up DHCP from WAN.
Turning interface on/off doesn't fix. Requires reboot or physically unplugging port.

7

22.1 Legacy Series / Re: Dashboard not accessible via VLAN

« on: June 29, 2022, 07:23:49 am »

Do you have it listening on that VLAN interface?
System > Settings > Administration > Listen Interfaces

8

22.1 Legacy Series / Re: [CALL FOR TESTING] FreeBSD 13.1 / 22.7 operating system preview

« on: June 23, 2022, 03:37:10 pm »

Correct. It seems this issue is common.
https://forum.opnsense.org/index.php?topic=28809.msg140202#msg140202

9

22.1 Legacy Series / Re: [CALL FOR TESTING] FreeBSD 13.1 / 22.7 operating system preview

« on: June 23, 2022, 03:24:22 pm »

I tried getting details of errors but all I could find was interface errors in netstat.
Speed test also were unable to reach full WAN speeds. After switching to untagged vlans full speeds were reached.

10

22.1 Legacy Series / Re: [CALL FOR TESTING] FreeBSD 13.1 / 22.7 operating system preview

« on: June 22, 2022, 09:28:07 pm »

Yes, and I also tried giving it an IP for untagged traffic.

And because of a new issue (WAN interface refused to pull IP from DHCP because it thought the interface was down) I reverted back to the current stable.

Both versions however have the same symptoms; tagged vlans generate errors.

11

General Discussion / Re: I225V Interface errors on trunked (tagged) port

« on: June 22, 2022, 01:29:55 am »

Thank you for those threads.
I did some testing and moved a VM off of a trunked port.
I can confirm that the errors stop if it is untagged.

12

22.1 Legacy Series / Re: [CALL FOR TESTING] FreeBSD 13.1 / 22.7 operating system preview

« on: June 21, 2022, 08:22:19 pm »

I've been getting errors on my i225v ports that have VLANed traffic. I tried updating to see if driver changes fixed it. No change.

13

General Discussion / I225V Interface errors on trunked (tagged) port

« on: June 21, 2022, 08:19:52 pm »

Just wondering if anyone else with an Intel I225V interface is getting errors on both in and out for interface that has VLANed traffic.

It looks like it is mostly benign as I don't notice anything and the errors are roughly 0.01% of traffic.

However it is easily reproducible. If I run any bandwidth testing that uses full bandwidth, the errors immediately go up.

The errors happen at both speeds of 1gbps or 2.5 if manually set.

I tried updating to 22.7.b, still get the same errors.

14

General Discussion / Re: [Solved] Displaying console menu in ssh connection for non-root admins

« on: May 17, 2022, 12:23:45 am »

Your profile script looks a little different from mine. I am wondering if there is a syntax error.
When you login, what happens if you type sh .profile

My .profile script looks like this:

Code: [Select]

# $FreeBSD$
#
HOME=/root
export HOME
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:~/bin
export PATH
TERM=${TERM:-xterm}
export TERM
PAGER=less
export PAGER

# set ENV to a file invoked each time sh is started for interactive use.
ENV=$HOME/.shrc; export ENV

# Query terminal size; useful for serial lines.
if [ -x /usr/bin/resizewin ] ; then /usr/bin/resizewin -z ; fi

# Uncomment to display a random cookie on each login.
# if [ -x /usr/bin/fortune ] ; then /usr/bin/fortune -s ; fi
sudo opnsense-shell

15

General Discussion / Re: [Solved] Displaying console menu in ssh connection for non-root admins

« on: May 16, 2022, 09:17:41 pm »

If you replace sudo su with sudo opnsense-shell does it fix the problem?