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 - FillFeile

#1
18.1 Legacy Series / Re: IGMPProxy1.3 is not starting
January 15, 2019, 06:54:00 PM
Quote from: gliddie on July 28, 2018, 09:48:25 AM
Hey,
I am now using the MR401 since 2 weeks.
Only firmware upgrades are not possible, since I am struggling with the tftp proxy.
Everything else has been working great.
No issues with watching TV.

Did you try it Frank?

Hi @gilddie, Hi to everyone,
I'm currently not able to get the MagentaTV IPTV working on my BNG based FTTH connection. I run my OPNSense directly connected to the FTTH Modem with an VLAN 7 Tagged Interface which is used by my PPPoE based WAN interface. I have tried several FW-Rulesets and also configured the IGMP-Proxy but the IPTV stream starts to stuck after round about 30 seconds streaming.

Could someone post his detailed FW-Rulesset and IGMP-Proxy settings that he/she used to get IPTV working on a Telekom based link using a OPNSense FW?

Thanks for any help in advance - I can post a more detailed config of my current setup if needed,

Cheers,

FillFeile
#2
18.7 Legacy Series / Re: Firewall Log not working
August 30, 2018, 05:25:56 PM
@marjohn56 you made my day! Clearing /var/log an restarting the daemon did the trick.

syslogd is not eating up the RAM anymore and the firewall live logging works again.

Thank you some much!  ;)
#3
18.7 Legacy Series / Re: Firewall Log not working
August 29, 2018, 06:19:02 PM
Sadly I didn't find any message from my syslog deamon in my system.log. Here is the most current content and nothing was added after the daemon died again:


Sep 29 10:59:23 OPNsense configd.py: [32ea2b13-4821-48a8-9d0b-78a481c59ffa] request pfctl byte/packet counters
Sep 29 10:59:30 OPNsense configd.py: [d82f2168-41c7-4f26-b655-4543d180a8ef] request pfctl byte/packet counters
Sep 29 10:59:37 OPNsense configd.py: [7e116d12-1f8e-4377-9d59-a4ca92d14732] request pfctl byte/packet counters


I debugged a little more on my side and made an interesting discovery - after starting the syslog service via the web interface the syslogd process shows up in the process list. Observing the process list for a little while showed be this:


PID USERNAME  THR PRI NICE   SIZE    RES STATE   C   TIME    WCPU COMMAND
3494 root             1  25    0  1051M   602M bo_wwa  3   0:12   8.49% syslogd
3494 root             1  24    0  1051M   760M bo_wwa  3   0:15   9.63% syslogd
3494 root             1  25    0  1051M   843M bo_wwa  3   0:17   9.78% syslogd
3494 root             1  26    0  1051M   929M bo_wwa  0   0:20  11.04% syslogd
3494 root             1  27    0  1051M  1029M bo_wwa  2   0:23   7.54% syslogd


The reserved (I think this is what RES stands for?) memory grows over time and the services dies after hitting the 1051M border.

Any ideas?
#4
18.7 Legacy Series / Re: Firewall Log not working
August 28, 2018, 05:08:28 PM
Thanks for your fast answer Animosity022!

Actually there is on syslog file under /var/log...


root@OPNsense:/var/log # la
./                      flowd.log.000006        pf.today                suricata.log.2
../                     flowd.log.000007        pf.yesterday            suricata.log.3
bsdinstaller/           flowd.log.000008        portalauth.log          suricata.log.4
configd.log             flowd.log.000009        ppps.log                suricata.log.5
dhcpd.log               flowd.log.000010        relayd.log              suricata.log.6
dmesg.today             gateways.log            resolver.log            suricata.syslog.log
dmesg.yesterday         installer/              routing.log             system.log
dnsmasq.log             ipsec.log               setuid.today            userlog
filter.log              lastlog                 setuid.yesterday        utx.lastlogin
flowd.log               lighttpd/               squid/                  utx.log
flowd.log.000001        lighttpd.log            squid.syslog.log        vpn.log
flowd.log.000002        mount.today             suricata/               wireless.log
flowd.log.000003        ntp/                    suricata.log
flowd.log.000004        ntpd.log                suricata.log.0
flowd.log.000005        openvpn.log             suricata.log.1


Any ideas?
#5
18.7 Legacy Series / [SOLVED] Firewall Log not working
August 27, 2018, 05:48:31 PM
Hi all,

System Info:  OPNsense 18.7.1_3-amd64 on AMD GX-412TC SOC

Currently I'm facing an strange issue with my OPNSense box. A while ago I noticed that my firewall logging is not updating anymore (and so do other logs like System->Log Files->General).

For example if I go to Firewall>Log Files>Live View the last entries there are from March this year - and no current log events are displayed. The firewall itself seems to work just fine by the way.

I also recognized that the syslog service on the dashboard is stopped - if I try to restart the service it runs for a couple of minutes and dies again afterwards. Could this be related?

Any suggests? Can I provide you with additional information?

Cheers,

FillFeile
#6
Only for reference:

I just updated OPNsense to verison 16.7.12 and now the IDS & web proxy settings are not broken anymore.

So this issue is solved for me :)
#7
Hello together,

I just installed OPNsense on my fresh arrived PCEngines apu2 with an 16GB SSD.

I used the following image to install: OPNsense-16.7-OpenSSL-serial-amd64.img

Everything seems to work fine, but if I try to setup either the proxy or the IDS feature OPNsense shows me only a broken settings page (see the picture in the attachments).

Does anyone know the reason for this? I read some posts in this forum where people used the IDS and proxy feature on my hardware...

I know that 16 GB of storage are not sufficient for operating both of the with many users, but I would like to give it a try..

Thanks for your help ;)

FillFeile