• 0 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle


  • ScandalFan85@feddit.detohomelab@lemmy.mlMikrotik/RouterOS headache
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    8 months ago

    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.





  • ScandalFan85@feddit.deto3DPrinting@lemmy.worldPrusa MK4 or Bambu labs p1s
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    9 months ago

    I was in the same position two months ago and decided to go with the Prusa MK4 kit with the enclosure. So far I’m happy with my purchase. The deciding factor for me was lastly the loudness of the device because I wanted to use the printer in my apartment. Reviews said that the printer is relatively quiet and I can confirm that. If the door to my “printer room” is closed I’m not able to hear it.

    Some points about the MK4:

    Positives:

    • It prints very fast with the new Input Shaper firmware
    • I can control the printer via LAN and WiFi (or print directly from a USB drive)
    • Excellent print quality
    • Open Source and spare parts are avaiable for a long time

    Negatives:

    • Maintenance is complicated after installing the printer in the enclosure. You can only access the printer through the front door which makes reaching the sides of the printer difficult and removing the printer from the enclosure is not easy as well because you first have to disassemble the display unit.

    I dont’ have access to a Bambulab printer so I’m not able to compare both the Prusa MK4 and the Bambulab P1S. Nevertheless, I’m happy with my printer and can recommend it.







  • I’ve purposely build that NAS around two or three years ago. It’s a Gigabyte B360M D3H mainboard, Intel Pentium Gold G5400 and 16GB of the cheapest RAM I could find. An Adaptec 71605 card provides SAS/SATA connections for up to 16 drives and a Mellanox Connect-X3 connects my NAS via 10Gbit/s to my network. The case is an Inter-Tech IPC 4U-4424 . It has 24 hot swap bays. But I would not recommend it because the backplane is terrible. Four or five slots are not working. Sometimes, when I re-insert a drive, it is not detected.

    Using cheap RAM bit me in the ass last year as one of the RAM sticks started to fail. I didn’t notice that there is a problem with the RAM at first. Only when I observed that one of my scripts was not working I started to investigate the problem. Turns out that one of the RAM sticks failed. Re-inserting the stick did not resolve the problem so I replaced all sticks with old Crucial RAM I had laying around. Some files that I transfered to the NAS during that time period are corrupt. In the future I won’t use cheap RAM anymore and I’m also currently planning to replace the mainboard and CPU with something that supportes ECC RAM so that I can be notified when on of the sticks starts to fail.

    Here are some pics from building the NAS



  • I believe I could reduce the power consumption by ~50W-60W by replacing the R730 with a modern “consumer” mainboard + CPU. But I need two power supplies (I had some issues a few months ago with my UPS) and iDRAC/IPMI is so convenient that I don’t want to miss it anymore.

    I’m also currently searching for something power efficient to replace the Pentium in my NAS. Reason for that are some problems with bad RAM a year ago. ECC RAM would be nice to have, so that I can be notified when a RAM stick goes bad. I currently do not know for how long the old RAM stick was bad and which files may be corrupted because of that (I do not use a checksumming file system such as ZFS or BTRFS on my NAS).


  • 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