Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - patan32

#1
I have the same issue. I have disabled IDS/IPS all to gather. Nothing i change in the GUI fixes the issue. They have broke the suricata package with the new update. Had similar issue when they release Netmap version 14. I had issue with my fiber 10gig interfaces. The new update with cause my cisco switch 10 gig port to flap which i have increase the flap time and recovery if the port gets disabled. I am not sure why the port has to go down multiple times on and off which cisco switch thinks the port is flapping and disables it.

Had a very stable firewall to very unstable with this new update. :(
#2
Hello,

After upgrading to the new version of opnsense it breaks my 10gig network. Please see the video below. I did a fresh install and same issue. I am using Sophos SG320 hardware with 10 Gig modules. If i unplug the fiber cable it will boot okay and not kill my cisco switches uplink. If the fiber is plugged in the uplink port will change to orange.

Orange error in cisco means: solid orange - port in error disable, spanning-tree negotiation, Trunk to access port mismatch or switch may have a faulty port. Port is shutdown for a 6500.

This must be something to do with FreeBSD or IX drivers. I have multiple VLANS assigned to the 10Gig network.  I am currently using Mikrotik Cloud Core since new version is broken. I can do testing if need be. Everything was working fine before upgrade. 
#3
Quote from: AdSchellevis on December 14, 2021, 06:06:10 PM
On the physical interface it should work in principle, provided the hardware is properly supported. You can always try the beta for 22.1 by the way, maybe if there's a driver issue a newer version of the kernel might show different behaviour.

Best regards,

Ad


Why am i getting lots of errors on the interface WAN where IPS is enabled on physical interface. I didn't have this problem when i had IPS enabled on VLAN interface. Is this normal?

https://ibb.co/vvjNbjB

Doesn't seem to make sense now why have so much dropped packets.
#4
This is my current setup with 21.7.5.

https://ibb.co/ZgNmvY0

Why does Suricata only show one physical interface? It really doesn't matter but my main capturing interface is igb0. Shouldn't i be seeing ix0 interface too which is on LAN side?

https://ibb.co/z6S7ZwC
#5
Quote from: AdSchellevis on December 14, 2021, 08:36:45 AM
Officially IPS doesn't support virtual interfaces, such as VLAN's (https://docs.opnsense.org/manual/ips.html#choosing-an-interface). In 21.7.6 we added the new netmap api which seems to enable emulated mode in these cases.

I've seen a similar setup yesterday where someone added a bunch of vlan's to IPS, which starts but will not detect anything in previous versions of suricata (for a functional setup you need to capture the parent in promisc mode).

In 21.7.7 we will temporary revert the new api, which will then be back in 22.1, I haven't tried if it works for vlan's in 22.1, maybe it does, maybe it doesn't, if it doesn't we may have to tighten validations at some point from preventing people to choose these type of setups.

Best regards,

Ad

I have even enabled it on physical interface and still kills my internet using the new suricata package. I enabled igb0 with  Promiscuous mode enabled and it was dropping lots of packets on the Errors Out in the interfaces. Doesn't matter what interfaces i choose when using 21.7.6 it kills my internet and the config works on 21.7.5. Clearly i have a supported hardware with supported NIC drivers from Freebsd.

How do i upgrade to 22.1? Is this still in DEV?

#6
Describe the bug
After updating opnsense to version OPNsense 21.7.6-amd64 and enabling suricata 6.0.4 version stops my internet connectivity. The service will start as normal with nothing in the logs and after few hours it will kill my internet connection and in the wan interface it will remove the ip and replace it with .dhcp. As soon as i restart suricata service my internet comes back and i can see my public ip address (nothing will show in the suricata and system logs).

I am using all the rule sets in suricata and created policies. I have been running the same system with version 21.7.5 which had no issues and with the same rule set. After upgrading to version 21.7.6 the problem appeared and it will kill my internet connection. I run my internet connection directly from ISP ONT on VLAN 10. On suricata i have WAN selected for interface which is a VLAN 10 and i have enabled Promiscuous mode. I have not changed anything on my config side.

I knew the problem started after upgrading to latest version. I re-imaged the box to 21.7.1 and using the manual Flavour settings under updates i put this code "21.7/MINT/21.7.5/OpenSSL/" to upgrade to version 21.7.5 and restoring my config. I enabled suricata and i haven't had any issues. This tells me the issue is with suricata killing internet connection without any logs. I am not sure what has changed with the new version of suricata. I tested on Sophos SG430 Rev 1 hardware and the issue is the same.

Relevant log files
Suricata shows no faults or issues in the logs when it drops internet connection. System logs show no issues.

I did see this though in the system logs, but i also see this error when i am running version Suricata 6.0.3_3.

2021-12-12T13:45:06 kernel 906.106372 [ 853] iflib_netmap_config txr 4 rxr 4 txd 1024 rxd 1024 rbufsz 2048
2021-12-12T13:45:06 kernel 906.015935 [ 853] iflib_netmap_config txr 4 rxr 4 txd 1024 rxd 1024 rbufsz 2048
2021-12-12T13:45:06 kernel 905.926248 [ 853] iflib_netmap_config txr 4 rxr 4 txd 1024 rxd 1024 rbufsz 2048

Environment
Software version used and hardware type if relevant.
e.g.:
Hardware is : Sophos SG330 Rev 1
Currently running OPNsense 21.7.5-amd64FreeBSD 12.1-RELEASE-p21-HBSDOpenSSL 1.1.1l 24 Aug 2021
CPU type | Intel(R) Core(TM) i5-4570S CPU @ 2.90GHz (4 cores)
'I210 Gigabit Network Connection'

ix0@pci0:1:0:0: class=0x020000 card=0x02031374 chip=0x10c68086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = '82598EB 10-Gigabit AF Dual Port Network Connection'
class = network
ix1@pci0:1:0:1: class=0x020000 card=0x02031374 chip=0x10c68086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = '82598EB 10-Gigabit AF Dual Port Network Connection'
class = network
igb0@pci0:2:0:0: class=0x020000 card=0x30e015bb chip=0x15338086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
igb1@pci0:3:0:0: class=0x020000 card=0x30e015bb chip=0x15338086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
igb2@pci0:4:0:0: class=0x020000 card=0x30e015bb chip=0x15338086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
igb3@pci0:5:0:0: class=0x020000 card=0x30e015bb chip=0x15338086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
igb4@pci0:6:0:0: class=0x020000 card=0x0000ffff chip=0x15338086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
igb5@pci0:7:0:0: class=0x020000 card=0x0000ffff chip=0x15338086 rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = 'I210 Gigabit Network Connection'
class = network
igb6@pci0:8:0:0: class=0x020000 card=0x000015bb chip=0x15218086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class = network
igb7@pci0:8:0:1: class=0x020000 card=0x000015bb chip=0x15218086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Network Connection'
class = network
igb8@pci0:9:0:0: class=0x020000 card=0x0000ffff chip=0x15228086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Fiber Network Connection'
class = network
igb9@pci0:9:0:1: class=0x020000 card=0x0000ffff chip=0x15228086 rev=0x01 hdr=0x00
vendor = 'Intel Corporation'
device = 'I350 Gigabit Fiber Network Connection'
class = network

https://github.com/opnsense/plugins/issues/2706
#7
General Discussion / Re: per user bandwidth limits
April 20, 2020, 10:50:01 AM
I am also interested in this.
#8
Hello All,

I am needing help with LCDProc on Opnsense. I have manually edited LCDd-sdeclcd.conf  and lcdproc.conf to suit my needs. The LCD is working but i am not able to display the hard drive data. Please see the attached pictures.

I tried to set disk to "false" in the config file but after the reboot it shows up. If i run "service LCDProc onerestart" it doesn't show the hard drive data as per config. If enabled in the config it still doesn't show the data properly.

Any help will be appreciated.




#9
Quote from: Maestro86 on March 21, 2020, 05:57:05 PM
Maybe I can help. I run OPNsense on a Sophos SG330rev1 and I got my LCD screen working with lcdproc. Use the following config:

[server]
DriverPath=/usr/local/lib/lcdproc/
Driver=hd44780
Bind=127.0.0.1
Port=13666
ReportToSyslog=yes
User=nobody
Foreground=no
Hello="  Welcome to"
Hello="   OPNsense!"
GoodBye="Thanks for using"
GoodBye="   OPNsense!"
WaitTime=5
TitleSpeed=5
ServerScreen=on
Backlight=open
ToggleRotateKey=Enter
PrevScreenKey=Up
NextScreenKey=Down

[menu]
MenuKey=Escape
EnterKey=Enter
UpKey=Up

[hd44780]
ConnectionType=ezio
Device=/dev/cuau1
Keypad=yes
Size=16x2
KeyMatrix_4_1=Enter
KeyMatrix_4_2=Up
KeyMatrix_4_3=Down
KeyMatrix_4_4=Escape


You may have to change a few things, especially under the hd44780-section, but this should give you a start for getting the LCD panel to work.

Hello Maestro86,

I have the same setup as you. The LCD is working fine but i can't get the disk stats to show. It's disabled in the config file but it still shows up when i reboot. If you have a idea to disable it or get it going would be great.

I have the same hardware also.

Regards Ronald.
Modify message
#10
Quote from: optic on March 23, 2020, 08:42:00 PM
@Maestro86: Thank you so much!!! this worked!

Hello Maestro86,

I have the same setup as you. The LCD is working fine but i can't get the disk stats to show. It's disabled in the config file but it still shows up when i reboot. If you have a idea to disable it or get it going would be great.

I have the same hardware also.

Regards Ronald.