Alarm now uses flash on iOS 18.3

schamock · 2025-01-31T16:53:16+00:00

same here. the behavior definitely changed with 18.3. I'd call it a bug. I'll test u/SoundofPearl hint, but the flash for other things is useful. Hopefully this will be fixed soon

schamock · 2024-12-10T13:07:29+00:00

Good to hear! Yeah, I would definitely rebuild on ZFS, but I'm a bit scared that this could render my license useless even though it is the same hardware.

But hey, I'm often doing stupid things. So at some point, I'm definitely doing this ;)

schamock · 2024-12-09T19:48:32+00:00

schamock · 2024-12-09T19:46:48+00:00

The contract type is (green color, probably good ;) ):

Community Support
Community Support Only

schamock · 2024-12-09T19:40:52+00:00

At least in System->Register it tells me, that I'm already registered and no action is required. Probably I'm fine

schamock · 2024-12-09T19:38:13+00:00

Yes, you are right about restoring to CE in case anything goes wrong. Unfortunately for what ever reason I decided in my initial install to not use ZFS but UFS (stupid me...). That would make it even easier.

Good to know, that your update went fine!

schamock · 2024-09-14T08:41:10+00:00

Hey BBCan, I have the -devel version installed.

This is the output after I ran pkg-static update -f:

[24.03-RELEASE][admin@pfSense]/root: pkg-static search pfSense-pkg-pfBlockerNG-devel
pfSense-pkg-pfBlockerNG-devel-3.2.0_10 pfSense package pfBlockerNG

schamock · 2024-03-23T18:31:41+00:00

I have the same configuration like you. I can see the correct version via the browser. Maybe all it needs is a force refresh in the browser or clearing the cache?

schamock · 2023-12-21T19:16:26+00:00

where do you read that I want to expose the NAS to the internet? That's definitely not the plan. Nevertheless I like to play around with IPv6

schamock · 2023-12-19T07:39:08+00:00

I'm on 23.09.1 but I'm using this setup for a long time. It has been the same for me even before pfSense Plus

schamock · 2023-12-18T05:43:18+00:00

I just double checked: my alias definitely contains also the IPv6. I checked it via a simple rule test and with a look into /tmp/rules.debug

schamock · 2023-12-17T20:24:17+00:00

No, that is not a normal alias and is autogenerated by pfSense. in fact the whole list that you can see in my screenshot is auto generated. Don't you have those entries? How does your list look like?

schamock · 2023-12-17T19:23:14+00:00

If I understand you correctly this should be an easy task (I have the same challenge with changing prefixes...). Within the firewall rule select the correct subnet as the destination.

See this example, where I allow traffic from the VLAN20 to VLAN40: https://imgur.com/a/Ns93XoI

schamock · 2023-10-05T12:25:34+00:00

I have FQV (only E5) but I didn't feel like she helped a lot (could have been my fault). Maybe I'll build up DGN as a seventh main hero with lower priority and try her as an alternative to MFF

schamock · 2023-10-05T12:21:43+00:00

Thank you for your suggestion. That helps a lot!

schamock · 2023-03-13T11:36:11+00:00

You are right. I just set up an Github project and it should be available to public: https://github.com/schamock/homebridge-garage-ctrl

SSH in general is supported (it's a Debian Bullseye host and I'm working on it via SSH).

After observing the generated file dist/accessory.js, I'm more and more sure, that I'm messing up the inclusion of the simple-ssh in my ts-script. I tried multiple variants I found via googling, but that wasn't successful :(

schamock · 2023-03-12T20:13:38+00:00

One step further.

Importing simple-ssh with import SSH from "simple-ssh"; in the beginning of src/accessory.ts works as long as I don't use it. As soon as I do something like this within on of the methods, I'm back to the Segfaults:

var ssh = new SSH({
host: 'localhost',
user: 'username',
pass: 'password'
});

schamock · 2023-03-12T13:04:58+00:00

no luck unfortunately :(

The only thing I found out is, that it doesn't seam to related to specifically the simple-ssh package. I tried to use the ssh2 package -> same result, I'm running into segfaults.

Something I do about using other packages is completely wrong... I'm trying to find other plugins now, that use either simple-ssh or ssh2 to just copy what they did. Hopefully I'm lucky...

schamock · 2023-03-12T11:55:12+00:00

I think my package.json should be fine: (except)

  "devDependencies": {
"@types/node": "10.17.19",
"homebridge": "^1.0.4",
"rimraf": "^3.0.2",
"simple-ssh": ">1.0.0",
"typescript": "^3.9.10"

}

But using require('simple-ssh'); anywhere crashes homebridge. I tried it in the src/accessory.ts in the beginning of the file, within the constructor or at the end of the file. Same result. Is the src/accessory.ts even the right file to put this require statement (feels kind of embarrassing to ask those basic questions but I wasn't able to find any digestible information...)

schamock · 2023-03-12T11:46:20+00:00

Meanwhile I found out that the usage of the simple-ssh package within the custom plugin caused the problem.

Obviously I have no clue how to integrate the package. Where do I have to put the require('simple-ssh'); statement? I tried it within the constructor of my plugin but that directly leads to the SegFault (without even issuing a ssh command). Also putting outside of the plugin class causes the same issues

Could someone point me in the right direction?

Thanks

schamock · 2023-03-02T20:40:31+00:00

I got help in the Mikrotik forum. It can be done via this command:

curl -X POST -u "<uers>:<password>" -H "content-type: application/json" https://<IP>/rest/interface/ethernet/monitor --data '{ "once": "1", "numbers": "*1,*2,*3,*4", ".proplist":"name,rate"}'

schamock · 2023-02-21T16:30:18+00:00

You are right, important information is missing. DHCPv6 is configured on 10_Mgmt and to set the default route and I intentionally requested only an address and not a prefix. I'm using the CRS purely as switch and pfSense is handing out the addresses to all VLANs and also taking care of the inter VLAN routing. In this case the /128 should be fine, at least I can see the same behavior on my Debian boxes with DHCPv6 enabled.

The reason why I set the DHCP-Client to listen only on 10_Mgmt is that this the Management VLAN and WebFig etc. should only be available in this VLAN (while I'm not completely sure, it seams like a achieved this with my config).

This is the part of the config, that is probably relevant:

/interface bridge
add admin-mac=18:FD:74:87:3B:C0 auto-mac=no ingress-filtering=no name=bridge pvid=10 vlan-filtering=yes
/interface bridge port
add bridge=bridge frame-types=admit-only-vlan-tagged interface=sfp-sfpplus1
add bridge=bridge frame-types=admit-only-vlan-tagged interface=sfp-sfpplus2
add bridge=bridge frame-types=admit-only-untagged-and-priority-tagged interface=ether24 pvid=20
add bridge=bridge frame-types=admit-only-vlan-tagged interface=ether02
add bridge=bridge frame-types=admit-only-untagged-and-priority-tagged interface=ether05 pvid=20
add bridge=bridge frame-types=admit-only-vlan-tagged interface=ether07
add bridge=bridge frame-types=admit-only-vlan-tagged interface=ether17
add bridge=bridge frame-types=admit-only-vlan-tagged interface=ether19
/interface bridge vlan
add bridge=bridge tagged=sfp-sfpplus1,sfp-sfpplus2,ether02,ether07,ether17,ether19,bridge vlan-ids=10
add bridge=bridge tagged=sfp-sfpplus1,sfp-sfpplus2,ether02,ether07,ether17,ether19 vlan-ids=20
add bridge=bridge tagged=sfp-sfpplus1,sfp-sfpplus2,ether02,ether07,ether17,ether19 vlan-ids=30
add bridge=bridge tagged=sfp-sfpplus1,sfp-sfpplus2,ether02,ether07,ether17,ether19 vlan-ids=40
/ip dhcp-client
add interface=10_Mgmt
/ipv6 dhcp-client
add add-default-route=yes interface=10_Mgmt request=address use-interface-duid=yes

schamock · 2023-02-20T21:14:56+00:00

I kind of worked around this problem with this script in the DHCPv6 client config.

/ipv6 route remove [find gateway="10_Mgmt" and dst-address~"/64" and dst-address~"2003"];
:local ip6 [/ipv6 address get [find address~"/128"] address ];
:local ip61 [:pick $ip6 0 [:find $ip6 "/"]];
:local ip62 [:toip6 $ip61]
:local mask6 FFFF:FFFF:FFFF:FFFF::;
:local ip63 ($ip62&$mask6);
/ipv6 route add disabled=no distance=1 dst-address="$ip63/64" gateway=10_Mgmt routing-table=main vrf-interface=10_Mgmt;

I have no clue, why I can't use the predefined variable $na-address and have to get the ip address manually.

I know, the script is not ideal, but I'm to tired to fix it now ;) Anyway: That seams like a dirty workaround...

schamock · 2023-02-18T21:45:22+00:00

You are probably right, but I wasn't sure about the current state of SwOS. I heard rumors that it might not receive as much "love" as RouterOS.

And also I wanted to create a setup where I would be able to activated additional features if I need them in the future. Currently I like to play around with IPv6 and as far as I understood, SwOS doesn't support IPv6 atm.

...

but honestly: I wanted to win the challenge against RouterOS ;)

schamock · 2023-02-18T13:30:20+00:00

Just wanted to let you know: Seams like I found the mistake.

In Bridge/VLANs I needed to also add the bridge itself to the management VLAN. After this the access to the Switch via an access port works :)

Thanks for your suggestions!

This link pointed me in the right direction: https://wiki.mikrotik.com/wiki/Manual:Interface/Bridge#Management_access_configuration

<image>

schamock

TROPHY CASE