The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Ha, another twist on Windows 10 and optical drives.
In my case my home machine permanently indicates my optical drive as an "unknown device" but I can play CD/DVD content, burn discs etc... Windows explorer and device manager refuse to recognize it as an optical drive though, as long as it works its fine by me but it is definitely weird.
Seems like an app to monitor the bandwidth used on a given computer.
If I have a mixture of desktops, servers, laptops, phones, tablets, game consoles, etc...that's going to be woefully inadequate. My router has a page that shows realtime bandwidth usage, and I can often see that something on my network is downloading as fast as my connection allows - and I have no idea what that might be.
To be useful, these tools needs to start by telling you what device is sucking up the bandwidth. Then worry about individual apps.
(so in my case, the first step is to map out what devices own the MAC addresses displayed by my router...something I've been putting for, oh...years now?)
I'm not sure I understand what you mean. The impression I got was that the app was designed to monitor the bandwidth usage for a given computer. If you want to get a complete picture of where your bandwidth is being used, you need something that monitors the router that all traffic is going through.
So when you say "server", you essentially mean have all traffic rerouted through that machine.
I've never tried to set up a network that way, but that sounds like it could work.
Is that "just" a matter of setting up that computer's IP as the gateway for every device that otherwise would try to connect to the router?
Ideally that's be set up on the router (so there's a single location to edit), but then how do you set up the computer itself so it can talk to the router to reach the outside world (and not try to "get back to itself" in an endless loop)?
Ideally that's be set up on the router (so there's a single location to edit) but then how do you set up the computer itself so it can talk to the router to reach the outside world (and not try to "get back to itself" in an endless loop)?
On the router, set it to allow access only from the IP of the selected server machine, then set the server as an alternative gateway on each of the other machines (without removing the router as the primary gateway), and don't set an alternative gateway on the server machine.
• The router's docs will tell you which admin page to go to filter on IPs.
• To set an alternative gateway, just click the Advanced button on the network adapter's TCP/IP properties dialog, and then the gateway section's "Add" button.
With that set-up, if a non-server machine wants to access the network, it will try the router IP, be rejected, and fall through to the server, which will forward to the router.
You can then install all manner of packet-sniffers and network monitors on the server machine, and get all the info you want much quicker and easier than by relying on what you can squeeze out of the router.
When you're finished, there's no hurry to delete all the alternative gateways, because once the router is set to again allow access from all the machines, their requests will go straight to the router.
I wanna be a eunuchs developer! Pass me a bread knife!
then set the server as an alternative gateway on each of the other machines
That's really the bummer. I have, quite literally, over 100 VMs (not all running at the same time, obviously), and then probably close to 20 physical devices...some of which I'm not sure where these network settings reside.
But I've copied and pasted this into OneNote, so when I get around to it, I have something more concrete to get me started.
I've got an unsused motherboard laying around that has two network interfaces. I am seriously considering setting that up as a transparent pipeline, simply forwarding packet from one interface to the other without changing a single bit. This would require some fairly low level programming; I couldn't do it through a socket interface. But it is certainy possible, at a reasonable level of effort.
This would be a plain single-cable-to-single-cable pipeline, invisible to either the end PC or the router. Either would transmit their packages onto the cable, with no concern for the pipeline machine. No routing/switching, just simple two-way forwarding, that would allow the pipeline machine to peek at every package it forwards. Later, as I gain experience, it could even not forward selected IP-packets. If new, unknown IP addresses where detected, as source or destination, it could inject a downstream series of packages reporting it to my PC, for me to check off "OK", "reject all traffic" or whatever action, and return to this "pipeline PC". I am sure that it would have more than enough capacity do DNS lookups to report more information with the "unknown address" report.
I really expect this to be near-trivial, once I learn to do packet forwarding (which in principle is trivial as well...). My only problem is that this project currently is #34 on my list of near-trivial hobby projects.