Tailscale shouldn't advertise a route that is local to the machine. This is a routing loop. The way SR route distribution works in Tailscale is that you accept all routes or nothing. Routing platforms have the concept of route filters to prevent accepting an advertised route that would create a loop.
There are hacky ways around this without having to deal with metrics (just advertise a /23 instead of a /24 and the /24 will be selected by default). But if you've got contiguous subnets you may not be able to clobber the additional address space just to avoid the route.
I really thought Tailscale would automagically figure this out. If this were true in all cases, my internet would not work at all since it would try to reach my router through the Tailscale interface.
You don’t have any specific routes to random internet addresses though. And Tailscale would not either. Unless your Windows server is running BGP, all your Internet traffic is hitting the default route.
It won't be visible to the naked eye. Maya ruins like these are covered by centuries of overgrowth. Lidar scans can spot shapes buried under this overgrowth, but from the air it'll at best look like random hills of dirt.
Maybe if there are structures comparable to Calakmul (which is close to Xpujil), you'll see some rocks on a tall hill.
I mean if you have the coordinates? And it’s 15 minutes away, why would you need Lidar or drones? You could probably send in some inquisitive geeky nerds from the local schools to scout it out.
> The result of the expression is the condition. Thus, in your example, the bool check would apply to "s", after the expression is evaluated.
This is a contradiction. There is no expression in my code that evaluates to s. foo() is an expression, and then std::string s = ... is assignment initialisation, which is not an expression.
Edit: I suppose that if I used another form of initialisation, the answer becomes a bit more obvious:
if (std::string s('x', 3))
(Not that this makes sense but just the point is to use a constructor with more than one argument.) In this case it's clear the test has to be the just-initialised variable. In fact there could be no arguments at all!
Yes, both of these would be in my top ten hall of fame software books. Bought both very early on in my career and they put me so far ahead of my peers.
My information would be decades out of date unfortunately. I suppose any current edition of "Internetworking with TCP/IP" would do, but they are horrendously expensive on Amazon so maybe out of print ?
I think either of these authors' books is fine by itself. You just need to update yourself with RFCs and any other sources of info for newer developments in the stack.
Stack ranking existed at MSFT before Ballmer became CEO, i.e., when billg was CEO.
It was a practice that Jack Welch brought into the corporate world and Microsoft was just guilty of following what were thought to be best practices at the time.
Source: worked at Microsoft before Windows Mobile was a thing.
As an aside, Windows Phone was my favorite phone OS and Ballmer seemed like the one who actually cared about it a lot.
Tangent:
I love that phrase. Anytime I hear someone make that statement I think about the 9,000 things that have been considered "best practice" until we actually understood that they weren't even "good practice". It gets thrown around as if it's been studied and confirmed when in reality it means "a bunch of people are doing it"
I'm really out of the loop on this, but in the past for Windows at least you could customize an image and use PXE to install it from the network. Then all the user had to do was login with a domain account.
Does that not work any more or is it just not popular ? Any insights as to why not ?
At least in the Apple world, my IT dept drop-ships MacBooks direct from Apple to employees, already enrolled in our MDM via their business partner program. Any additional software installations and provisioning happens after first boot via the MDM platform.
New hardware is never on a company campus or in IT hands where it could be pointed to a PXE server and imaged in that way (assuming we were running a Windows fleet too)
How do other OSes handle the situation of having two interfaces with identical routes to a given destination ?
I don't see a better solution than using link speed, but I haven't thought about it too deeply.