Creat

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

Creat ,

Just to comment on your first point, while in Utopia it wouldn't be worth mentioning, the fact that not every companys job listing even includes home office, that makes it not just worth mentioning, but means it needs to be highlighted. People look for jobs that allow some or full time home office (for whatever reasons, or in general). How are they supposed to find them if it's not mentioned anywhere?

Creat ,

Do I understand this correctly? Your PC is on .6.X, and your connecting to the PiAlert on .1.X, but it also has an interface on .6.X? You just can't do that with Linux. Weirdly enough I hink Windows handles this correctly and sends the responses back via your router (I think any stateful TCP connection will use the same interface both ways). This doesn't explain why anything actually freezes though. Did the VM lock up, or is it just ssh that's dropping?

But as for the solution: if both devices have interfaces on the same network, you should connect to that interface.

Creat ,

Yes I know why you have so the interfaces, but as far as I know: Linux simply can't do what you want. So if you want to access PiAlert from your main PC on .6.X, you need to make that accessible from .6.Y on that VM. If you want to have the management port (UI) only open on the management interface, you would need to remove it's interface on .6.X.

As I said, as far as I'm aware Linux simply can't not route packets properly in an environment like that. I won't respect that the interface packets came in on needs to also be the outgoing interface for the return trip. I also had that problem and eventually j I've just given up.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • All magazines
    •