SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-03 10:19 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0001380	ClearOS	snort	public	2013-10-16 09:50	2013-11-04 15:43
Reporter	bchambers
Assigned To	user2
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version	6.5.0 Beta 2
Target Version	6.5.0 Beta 3	Fixed in Version	6.5.0 Beta 3
Summary	0001380: Snort fails to start on DSL (pppoe) interfaces
Description	Oct 16 11:45:11 chambers snort[877]: Daemon initialized, signaled parent pid: 876 Oct 16 11:45:11 chambers snort[877]: Reload thread starting... Oct 16 11:45:11 chambers snort[877]: Reload thread started, thread 0x7f79ff122700 (878) Oct 16 11:45:11 chambers kernel: device ppp0 entered promiscuous mode Oct 16 11:45:11 chambers snort[877]: FATAL ERROR: Cannot decode data link type 113 Oct 16 11:45:11 chambers kernel: device ppp0 left promiscuous mode
Steps To Reproduce	service snort start on system using DSL
Additional Information	Possible relevant code: http://www.linuxquestions.org/questions/linux-software-2/snort-2-9-4-5-cannot-decode-data-link-type-113-a-4175463405/#post4958690 [^]
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes

There are no notes attached to this issue.

Notes

Issue History
Date Modified	Username	Field	Change
2013-10-16 09:50	bchambers	New Issue
2013-10-16 09:50	bchambers	Status	new => assigned
2013-10-16 09:50	bchambers	Assigned To	=> user2
2013-10-16 16:56	user2	Category	app-intrusion-detection - Intrusion Detection => snort
2013-10-17 10:12	user2	Status	assigned => resolved
2013-10-17 10:12	user2	Fixed in Version	=> 6.5.0 Beta 3
2013-10-17 10:12	user2	Resolution	open => fixed
2013-11-04 15:43	user2	Status	resolved => closed

Issue History