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.

Messages - carepack

Pages: 1 [2]

German - Deutsch / Re: OPNsense 16.7.10 und Einrichtung mit Squid und Suricata

« on: December 13, 2016, 08:27:21 pm »

Quote from: fabian on December 13, 2016, 07:18:10 pm

Was die Firewall-Regeln angeht: einfach mal den Hilfetext anzeigen lassen - dann bekommst du einen Link zur vorkonfigurierten NAT-Regel.

MfG

Fabian

Hi fabian,

danke für die antwort. Ja, mein fehler. Hab die firewallregeln hinzugefügt und es funktioniert. Leider habe ich aber noch keine lösung für suricata und das wan interface. Ich versuch mal logs zu ziehen.

German - Deutsch / OPNsense 16.7.10 und Einrichtung mit Squid und Suricata

« on: December 13, 2016, 10:45:22 am »

Hallo OPNsense-Gemeinde,

ich freu mich meine Firewall endlich auf OPNsense umgestellt zu haben. Es war mir schon lange ein Anliegen, vor allem seit ich vermehrt die Debatte zwischen PFsense und OPNsense Debatte verfolge (anderes Thema und gehört nicht hier her).

Mit Squid und Suricata hab ich leider ein paar Probleme. Logs kann ich erst später bereitstellen. Hier mal meine Config

Interfaces:
WAN: re0 -> vlan_tag 7 -> pppoe t-online
OPT1: mein wlan
LAN: mein lan

Suricata:
Grundsätzlich funktioniert Suricata, allerdings ist mein Problem, wenn ich Suricata nur das WAN Interface überwachen lasse, dass keine Alerts oder Infos im Log angezeigt werden. Um zu testen ob Suricata grundsätzlich funktioniert, habe ich die Interfaces getauscht, und lasse Suricata auf den Interfaces LAN und OPT1 lauschen und siehe da, es werden Infos und Alerts angezeigt.
Eigentlich wäre der Zustand für mich tragbar, wenn nicht die wlan Schnittstelle OPT1, signifikante Geschwindigkeitseinbußen hätte. Hat jemand eine Idee wie ich Suricata dazu bekomme, dass WAN Interface zu überwachen? Wäre mir die liebste Lösung. Ich könnte auch damit leben wenn die Performance für WLAN / OPT1 passen würde. Ist vielleicht das VLAN Tag7 das Problem? Suricata läuft auf promiscious mode.

Squid:
Der Proxy Server läuft im transparenten Modus. Blacklists sind installiert und aktiviert. SSL ist deaktiviert, es sollen also nur nicht SSL Verbindungen gefiltert werden. Als Interfaces / Netze habe ich OPT1 und LAN angegeben.
Ich habe die Kategorien z.B. gambling, webtv usw in den Blacklists aktiviert, kann jedoch alle Seiten die mir einfallen aufrufen. Es scheint irgendwie, dass der Traffice nicht über Squid läuft, den Squid Server kann ich allerdings gezielt über ip:port aufrufen.
Auch hier würde ich mich freuen wenn jemand eine Idee hätte. Logs kommen später.

Quote

Edit: Ich muss meine FW-Rules nochmal prüfen.

Ich sag schon mal vielen Dank an die Community.

16.7 Legacy Series / Re: kernel: ath0: ath_chan_set: concurrent reset! Danger!

« on: December 13, 2016, 10:24:32 am »

Hi,
I'd similar problems and I've found something in the freebsd forum. I've tested the approach on pfsense and it looks more stable and reliable to me. Maybe it's an approach for opnsense too.

Create the file
/etc/rc.conf.local

with the following content:

Code: [Select]

ifconfig_ath0="ssid speedy.i mode 11g mediaopt hostap channel 2 -bgscan up"
Here is the link to the forum post:
https://forums.freebsd.org/threads/22112/

Maybe it's not exactly what you want, but it helped to get my wlan more stabe and get rid of the stuck kernel messages. At least, the number of message with stuck_beacon became less.

A feedback would be nice!

16.1 Legacy Series / Re: ssh public key error

« on: May 15, 2016, 05:45:36 pm »

unfortunately, it's not solved. After next reboot the problem is there again

16.1 Legacy Series / Re: ssh public key error

« on: May 15, 2016, 11:14:40 am »

ok. solved. ssh in via root and execute the following:

chsh -s /usr/local/etc/rc.initial username

to define the shell for the user. should work! seems that the shell is not longer added to a new user

16.1 Legacy Series / Re: ssh public key error

« on: May 13, 2016, 01:06:19 pm »

ok. I'm one step further. I'm able to login via ssh again with the root user. but with every other user(existing, new, recreated) I can't. The error message is:

Code: [Select]

FreeBSD 10.2-RELEASE-p14 (SMP) #0 1b3679a(stable/16.1): Mon Apr  4 15:36:45 CEST 2016

Welcome to FreeBSD!

Release Notes, Errata: https://www.FreeBSD.org/releases/
Security Advisories:   https://www.FreeBSD.org/security/
FreeBSD Handbook:      https://www.FreeBSD.org/handbook/
FreeBSD FAQ:           https://www.FreeBSD.org/faq/
Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/
FreeBSD Forums:        https://forums.FreeBSD.org/

Documents installed with the system are in the /usr/local/share/doc/freebsd/
directory, or can be installed later with:  pkg install en-freebsd-doc
For other languages, replace "en" with a language code like de or fr.

Show the version of FreeBSD installed:  freebsd-version ; uname -a
Please include that output and any error messages when posting questions.
Introduction to manual pages:  man man
FreeBSD directory layout:      man hier

Edit /etc/motd to change this login announcement.
This account is currently not available.
Connection to ofw closed.

Is there any switch to enable ssh again. The test users are all in the admin group btw.

16.1 Legacy Series / Re: ssh public key error

« on: May 11, 2016, 12:02:11 pm »

so, system logs of pfsense

Code: [Select]

May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:55:44	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:54:54	lighttpd[75436]: (connections.c.1550) SSL: 1 -1 error:140E0197:SSL routines:SSL_shutdown:shutdown while in init
May 11 11:54:48

The file requires 0600. The thing is, I dont want a certiface authentication. I will go back to normal password query. I think opn got some problems with removing the authority.

thats grabbed from the system logs of opn also when I try to sign in:

Code: [Select]

May 11 11:59:49	sshd[51833]: Disconnected from 192.168.179.32 port 38230
May 11 11:59:49	sshd[51833]: Received disconnect from 192.168.179.32 port 38230:11: disconnected by user
May 11 11:59:49	sshd[51272]: Accepted keyboard-interactive/pam for admin from 192.168.179.32 port 38230 ssh2
May 11 11:59:40	sshd[50762]: Connection closed by 192.168.179.32 port 38222 [preauth]

16.1 Legacy Series / ssh public key error

« on: May 10, 2016, 11:33:07 pm »

Hi all there,

I'm new to here. So hi everybody. I have hopefully a small problem. Following happened. I wanted to activate squid also for ssl. Following the opnsense guid I created the ca, created the cert and imported it on my client machine. In the end in my fast and hurry action it didn't work and I decided to move on when more time is present. I deleted the CA for fw. The result is that I'm not longer able to ssh into my fw. Neither with root or additional users. Thats the verbose output from my ssh client:

Code: [Select]

debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/micha/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/micha/.ssh/id_dsa
debug3: no such identity: /home/micha/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/micha/.ssh/id_ecdsa
debug3: no such identity: /home/micha/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/micha/.ssh/id_ed25519
debug3: no such identity: /home/micha/.ssh/id_ed25519: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

I hope the community is able to help. I want to avoid to resetup the whole system. Thank you all

Pages: 1 [2]