Avatar

ScandalFan85

ScandalFan85@feddit.de
Joined
24 posts • 22 comments
Direct message

You’re welcome. I’m glad that I could help you :)

permalink
report
parent
reply

You can also download the *.vsix file of the desired extension from either Github or Microsoft’s extension marketplace and install it manually by clicking on “Install from VSIX” in the Extensions menu.

This obviously doesn’t solve the update problem and it is also questionable if this is in terms with the “Microsoft Terms of Use” of the extension.

permalink
report
parent
reply

My rack currently consumes about 300W. This includes the following hardware:

  • Dell PowerEdge R730 with 128GB RAM, 1x E5-2630 v3 (the second socket is unpopulated), 5x HDD and 4x SSD
  • MikroTik CRS309-1G-8S+ (8 port 10Gbit/s switch)
  • MikroTik CRS326-24G-2S+ (24 port 1Gbit/s switch)
  • MikroTik RB5009UPr (Router)
  • Whitebox NAS with Intel Pentium Gold G5400, 16GB RAM, Adaptec RAID controller in IT mode, 19x HDD and one SSD
permalink
report
reply

I’m fairly new to MikroTik and no expert either, but I don’t think you need a second bridge. You can add your VLANs to the default bridge and handle internet access through firewall rules. Depending on your existing firewall logic, you may have to drop/reject all traffic from the IoT subnet to the internet and all other subnets. Make sure that you add the bridge also as a tagged interface to the VLAN! Else, the DHCP server and all services on the router can not reach the IoT subnet.

I would also recommend to segregate all traffic into different VLANs (WAN, LAN, IoT, …). This makes it easy to manage firewall rules because you can then use either VLAN interfaces or interface lists containing multiple VLAN interfaces for similiar firewall rules. You can simply untag outgoing traffic on specific ports if you want and add a specific tag for incoming traffic.

I have a similiar setup running. Everything is separated into VLANs and these VLANs are configured on the default bridge. Routing/allowing and denying traffic to/from the internet is handled by firewall rules. And I have defined interface lists like NO_INTERNET_ACCESS, NO_LAN_ACCESS, etc. These lists are then used by the firewall rules. If you later want to add another VLAN that should not get access to the internet you can simply add it to the NO_INTERNET_ACCESS list and you do not have to alter your firewall rules for that specific VLAN.

Take this advice with a grain of salt. If possible, do not test this on your production network but on a separate, isolated router.

permalink
report
reply

What software did you use to make this diagram?

permalink
report
parent
reply

What does DSO stand for?

permalink
report
parent
reply

Wait, the peggies split up?!

permalink
report
parent
reply

What’s up with bandcamp?

permalink
report
parent
reply

Oh, no. I love bandcamp. I don’t want it to go down the drain. :c

permalink
report
parent
reply

Cube 2: Sauerbraten seems to still be maintained. I haven’t played it for a long time, though.

permalink
report
reply