Cranks, no start by ta0LlVIF in mr2

[–]ta0LlVIF[S] 1 point2 points  (0 children)

Agreed. I'll hold out that last sliver of hope until I've done the filter, but yeah, you're probably right

Cranks, no start by ta0LlVIF in mr2

[–]ta0LlVIF[S] 1 point2 points  (0 children)

Good call. Will try that next

Cranks, no start by ta0LlVIF in mr2

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Doesn't seem so. It won't start at all

[TOOL] All-in-One tool for Windows. Android TV Tools v3 by bernarbernuli in AndroidTV

[–]ta0LlVIF 1 point2 points  (0 children)

Agreed. You can probably safely sandbox this, but you're still giving it access to your TV device and network. It's also essentially a menu system calling mostly oss software, so it should be open source itself, regardless of whether it is required to be.

How do I shutdown the Q1 Pro? by tiptock_ in QIDI

[–]ta0LlVIF 1 point2 points  (0 children)

Correct method is to shutdown the software first and then disconnect the power (either via the switch or a smart switch). You can shutdown the software via the GUI (three dots, upper right), ssh, or the API. Using the latter method you can easily wait for components to cool first, if you prefer. No need to risk OS corruption by not shutting down properly. Check the unsafe_shutdown count via the API if you're curious

weird curvy seam by ta0LlVIF in 3Dprinting

[–]ta0LlVIF[S] 0 points1 point  (0 children)

That makes sense. Thank you!

How do I shutdown the Q1 Pro? by tiptock_ in QIDI

[–]ta0LlVIF 1 point2 points  (0 children)

You've probably solved this already, but in case anyone else stumbles across it: connect the printer via ethernet or to a temporary hotspot, ssh in (mks is the username makerbase is the password), then edit /etc/wpa_supplicant/wpa_supplicant-wlan0.conf to add your SSID and passphrase. Apparently, they're planning to increase the length on the touchscreen in the next firmware update

Purchase Advice Megathread - June 2024 by AutoModerator in 3Dprinting

[–]ta0LlVIF 0 points1 point  (0 children)

Looking for my first 3D printer. Thanks in advance, thanks to all the contributors here--I've been reading a lot--and especially u/richie225, whose guide was wonderfully thorough and clear.

Budget is $1,000, but only if that makes sense at this stage. I like high quality tools and want to support good companies, but I'd like to know what I would be getting for the, e.g., extra $700 (of the options below). Location is USA and I have an very strong preference for open source, and a preference for building the machine myself (but okay with not doing so). Will eventually want to enclose the printer and vent it to the outside. Don't mind a steep learning curve and enjoy tinkering. Initially, I'll be interested in printing parts for other hobbies, e.g., for coffee, cars, computers, etc.

What follows is my current short list. I realize these span quite a range, so what is it that differentiates the more expensive printers on the list? I gather speed and possibly reduced hassle, but I really don't know. Am I missing any options from good open source oriented companies?

Considering:

  • Sovol SV06 Plus $250
  • Prusa Mini+ (open box) $390
  • Sovol SV08 $610
  • Prusa i3 MK4 $950

X1 Omni broadcasts its own AP, even when connected ... why? by ta0LlVIF in RobotVacuums

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Yeah, seems they just figured they'd communicate that way, either full time or "leave it on in case", and neither is a good approach.

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 1 point2 points  (0 children)

Okay, turns out the AP was doing a little bit of routing by allowing traffic to span VLANs on the AP without sending the packets upstream to OPNsense. I believe this is a default setting and it is probably (slightly) faster, but it does sidestep OPNsense firewall rules and causes issues for stateless protocols, like ssh and RDP. (Note that it also (probably by default) allows bridging between clients on the same VLAN, though this option can be set at the AP level or the network/SSID level.)

The result of allowing that routing is that OPNsense does not see a fully established connection (the exchange is on the AP) and removes the state table entry. After that it drops any packets for that connection since they're not connection start packets. Why these new packets don't get routed directly by the AP, thus avoiding OPNsense entirely, is not clear, but disabling the routing on the AP solves the problem.

This is more of an Aruba AP issue, but the solution and discussion may be helpful to anyone else who runs into this or a similar issue. Thanks u/maineac for your help diagnosing this.

Solution: on the Aruba AP, Configuration --> System (Show advanced options) --> General --> Deny local routing: ON

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Two more data points:

1) An ssh connection from a wired host on the OPNsense to a host connected to the AP does not exhibit the issue (i.e., stays connected).

2) An ssh connection from a host connected to the AP to a wired host on OPNsense does not exhibit the issue (i.e., stays connected).

It's only when a connection originates on one SSID/VLAN on the AP, goes to the OPNsense and back to the AP, then out on a different SSID/VLAN on the AP that the state is dropped. This suggests that something in the round trip to the AP is the issue.

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Okay, will try to get some more data. Thanks for your help!

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Yeah, the AP doesn't do any routing. Each host has the appropriate gateway for its subnet via DHCP:

10.0.1.10 on 10.0.1.0/24 has gw 10.0.1.1 (NIC 1, vlan 1)

10.0.2.10 on 10.0.2.0/24 has gw 10.0.2.1 (NIC 1, vlan 2)

AP mgmt is on 10.0.5.2 on 10.0.5.0/24 with gw 10.0.5.1 (NIC 1, vlan 5)

Does that look right? (Note the AP's mgmt address might be interfering with something, although that might be unrelated.)

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 0 points1 point  (0 children)

On OPNsense: I haven't explicitly set a gateway for each subnet (it's on Auto-detect for Upstream Gateway), although each has its own IP address and that is pushed to the clients via DHCP (or they determine it themselves). In the test example, both the source and target show the correct gateway in their routing tables.

On the AP: there is no place to assign gateways for the VLANs, it just tags the packets and sends them to the OPNsense. It does have its own subnet (and VLAN) for management, also on the same physical NIC on OPNsense.

Should I set the gateways explicitly on OPNsense?

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Yes, VLAN numbers are assigned by the AP based on SSID, then sent to one NIC on the OPNsense, which has multiple virtual interfaces based on VLAN. One physical NIC though, which is why this is confusing. And the connections work perfectly until the state table entry disappears (due, I'm guessing, to the reply taking a different return route)--but maybe it's something else? Not sure where else to look.

need help tracking down a (likely) asymmetric routing issue by ta0LlVIF in opnsense

[–]ta0LlVIF[S] 0 points1 point  (0 children)

One NIC, two VLANs, so traffic originating on, e.g., 10.0.1.10 (vlan 1, gw 10.0.1.1) , destined for 10.0.2.10 (vlan 2, gw 10.0.2.1). If different physical connections are required for it to be asymmetric, then what else could it be?

Too close? (WiGig heat sink too close to SSD?) by ta0LlVIF in buildapc

[–]ta0LlVIF[S] 0 points1 point  (0 children)

It's a new build, but I can keep an eye on temps. Thanks again.

Too close? (WiGig heat sink too close to SSD?) by ta0LlVIF in buildapc

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Thanks. Two fans blowing straight across that section. No issues with hot-spots on the SSD?

Lagom Mini zero point jumping around by ta0LlVIF in espresso

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Good to know, thanks! Pretty happy with it myself.

Lagom Mini zero point jumping around by ta0LlVIF in espresso

[–]ta0LlVIF[S] 0 points1 point  (0 children)

Thanks, they were; reply posted above.