Help! Console going mad with freenas kernel messages after update

Status
Not open for further replies.

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
After updating my 2nd box and everything looking fine for a week or so I thought I'd bite the bullet and update my main box (and hopefully stop the daily e-mail reminders ;))

Updated to FreeNAS-9.3-STABLE-201503170439 which appeared to work fine, although I wasn't sat watching it. When I logged back in I noticed the console streaming lots and lots of this:

Code:
Mar 17 20:37:19 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.52:17500 255.255.255.255:17500 in via epair1b
Mar 17 20:37:19 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.52:17500 192.168.168.255:17500 in via epair1b
Mar 17 20:37:21 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.82:49516 192.168.168.255:32414 in via epair1b
Mar 17 20:37:26 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.82:49516 192.168.168.255:32414 in via epair1b
Mar 17 20:37:31 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.82:49516 192.168.168.255:32414 in via epair1b
Mar 17 20:37:34 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.50:17500 255.255.255.255:17500 in via epair1b
Mar 17 20:37:34 freenas kernel: <110>ipfw: 500 Deny UDP 192.168.168.50:17500 192.168.168.255:17500 in via epair1b


First IP addresses in the message are the devices on my network, but don't have anything with an address 192.168.168.255. Thought it might be related to openVPN jail so stopped this but the messages keep on coming. Rebooted and they are still there.

From a quick check everything appears to be working OK. I can access the AFP shares, ownCloud jail is up, as are Plex Media Server and PlexConnect jails. And openVPN jail is connecting too.

Didn't change anything and just checked 'ipfw list' which is set as '65535 allow ip from any to any'

Any ideas what might be causing this and more importantly how to stop it?

Thanks

UPDATE

I've pinned this down to the firewall in my ownCloud jail that is being used for Fail2ban. Stopping Fail2ban and ipfw service stops the messages.

Now to try and understand why the update has affected this, and how to correct it.

Any ideas?

UPDATE2

I've actually manage to fix this myself without appearing to break anything, which must be a first :D

I removed the following line from my ipfw.rules config:

Code:
# $IPF 500 deny log all from any to any


and both the IPFW and Fail2ban services started back up without a single message in the console! Not quite sure what this was doing, so if anyone has to time to continue my education I'd be most grateful.

Thanks
 
Last edited:
Status
Not open for further replies.
Top