Messages

1

20.1 Production Series / Re: Sonos speakers on a VLAN

« on: April 16, 2020, 06:06:19 pm »

Ah yes the old Sonos ports and firewalls issue

A struggled as well and after googling, it came to the conclusion that Sonos doesn't play properly with ports. So even if you create rules for the ports Sonos claim that need it won't work across VLANs

So I went for a slightly less robust route but one that I'm pretty comfortable with

I have a few LANS but for this explanation, IOT is where Sonos sits and my Trusted devices (Mac, iPhones etc) are on LAN
I allow any LAN device to any other VLAN. But I only allow the Sonos players on IOT to access the Sonos Controllers (iPhones for me) by having a rule like this below

I block everything else from IOT out to any other VLAN


EDIT - Don't use Safari though hate it. Chrome for me. But I'll play later and let you know

EDIT 2 - used Safari see below looks okay to me
 

2

20.1 Production Series / Lost WAN Access - 20.1.1

« on: February 21, 2020, 01:22:43 pm »

In the early hours of this morning, I noticed that I had lost WAN access.

When checking my monitoring systems I could see that I was still able to ping my firewall from external locations and all LAN access was as expected. Just no access to the internet.

I signed into the firewall GUI from the LAN and all the gateways and connections were showing as active, but still no WAN access.

I used a serial cable connection to sign in to the console then issued a reboot of from the GUI to see what messages appeared.

Nothing happened.  The console gave no indication the system was rebooting. So I issued console option 6 and the reboot started. However this also hung whilst closing down the processes - Sorry don't remember which point as I then did a power cycle.

During the power cycle, I got a message of "damage tar "repeatedly
So hit control C from the console and the startup completed. Subsequent powerups and restarts have been fine

If from the console I issue

# find . -name *.core

I get

./python3.7.core

Do you want a copy of this core file it's circa 23MB

3

General Discussion / Re: UDP Broadcast Relay

« on: February 05, 2020, 08:21:47 am »

Great thread

Marjohn has done some great work getting the plugin sorted. One day he will forgive me for all the work I caused him by saying “eh take a look at this pimd thing I’ve found” as always he did his normal “that’s really good but here’s something better”

Back to the questions

I’ve not needed  to specify more than one mcast address but I agree allowing it will future proof the plugin

I like the idea of using the DSCP as the id and allowing the user to manually set the TTL value maybe via advanced options. Again future proofing

4

20.1 Production Series / Re: Remote Syslog Settings - 20.1.RC

« on: January 27, 2020, 03:14:02 pm »

thank you all clear now

20.1.RC1 is surviving all the load testing and reboots etc that I'm throwing at it so seems very good so far

5

20.1 Production Series / Re: Remote Syslog Settings - 20.1.RC

« on: January 27, 2020, 03:05:11 pm »

Yes I missed that :-(

Mine wasn't set up anyway, so nothing to delete but what I had missed in the docs was this

"The remote logging feature will likely be removed in OPNsense 20.1, since the new Logging / targets offers more flexibility and has overlapping functionality. We advise to switch as soon as possible."

One final question now I've seen this I would have assumed the "syslog-ng" service would also be deleted (mine is still active) or is that a 20.1.1 activity/cleanup

6

20.1 Production Series / Remote Syslog Settings - 20.1.RC

« on: January 27, 2020, 02:27:02 pm »

Can't find anything in the 20.1 release notes but GUI in 19.7 at

System: Settings: Logging had a section for remote syslog

at 20.1.RC its missing and only Local Logging options exist

Did I miss something ?

7

20.1 Production Series / Re: 20.1.r_6

« on: January 27, 2020, 12:57:28 pm »

yep that fixed it 

8

20.1 Production Series / Re: 20.1.r_6

« on: January 27, 2020, 12:50:53 pm »

ok tried that

Then set GUI to Production
Requested an upgrade

Got this

***GOT REQUEST TO UPGRADE: maj***
Fetching packages-20.1.r1-OpenSSL-amd64.tar: ...................................................................... done
Fetching base-20.1.r1-amd64.txz: .. failed, no signature found
***DONE***

9

20.1 Production Series / 20.1.r_6

« on: January 27, 2020, 11:16:28 am »

As per subject line. I was running dev versions of 20.1

Switch back to Production in GUI and did the upgrade

My console is showing

OPNsense 20.1.r_6-amd64
FreeBSD 11.2-RELEASE-p16-HBSD
OpenSSL 1.1.1d 10 Sep 2019

Is that right ? was expecting rc1

10

19.7 Legacy Series / Re: [Solved] Sonos on VLANS

« on: January 15, 2020, 04:22:28 pm »

tested the plugin in test and now production and works perfect nice smooth install process

11

19.7 Legacy Series / Re: [Solved] Sonos on VLANS

« on: January 10, 2020, 11:11:33 pm »

@marjohn I'm waiting for you to read my last email re /etc/rc.conf.d/ 
 

12

19.7 Legacy Series / Re: [Solved] Sonos on VLANS - PIMD

« on: January 09, 2020, 07:11:28 pm »

@skywalker007

I can't say if this will work at the same time as IGMPproxy because I haven't tried it

But when I tried to run PIMD and IGMPProxy at the same time PIMD complained
When I tried udp-broadcast-relay-redux with PIMD it worked so my suspicion is udp-broadcast-relay-redux will work with IGMPproxy

But only one way to really know :-)

13

19.7 Legacy Series / Re: [Solved] Sonos on VLANS - PIMD

« on: January 06, 2020, 01:22:45 pm »

Yes confirmed this one allows both Sonos and SkyQ to work together which PIMD didn't seem to handle

14

French - Français / Re: Fibre Orange - configuration opnsense

« on: January 02, 2020, 05:20:25 pm »

J'ai écrit le guide original mais je n'ai pas eu la chance de le mettre à jour. La clé est de changer l'option-90 au nouveau format comme expliqué ici.

https://lafibre.info/remplacer-livebox/cacking-nouveau-systeme-de-generation-de-loption-90-dhcp/

15

19.7 Legacy Series / Re: [Solved] Sonos on VLANS - PIMD

« on: December 31, 2019, 02:31:28 pm »

Good catch - just amended the post incase others read it later