barry99705

That's why I stopped using it. The idea is there, but networking and usb support sucks.

Just don't forget, networking in Qubes is weird. So is usb support.

There's a few how-to's on Qubes site for setting this up.

If its a serial gps, kismet should "just work".

Wireshark is a pain in the ass without a gui. This little laptop has a little more horsepower than a pi as well.

Qubes is a little different. I think I remember there being a how-to on their site for wireless cards. https://www.qubes-os.org/doc/wireless-troubleshooting/

Adapters. USB-C isn't that wide spread yet.

No one is going to use an electron microscope to "rebuild" the data on a drive. You're talking about billions to trillions of bits of data, that any mistake between a dot or a dash will render the whole thing useless. A single zero pass on a "current" hard drive is enough to render it practically impossible to recover anything. Really, call up a recovery place and tell them that a drive got zero wiped with dban or something. They'll laugh at you, then hang up. "Current" being 500gb or larger. Though probably anything that's sata will be current enough. The only reason the electron microscope thing used to work was because the bits on the drive were larger, and there weren't as many. Though I've never seen actual proof it's ever been done. Here we go. https://www.vidarholen.net/~vidar/overwriting_hard_drive_data.pdf And a quote from the paper, emphasis is mine. 4 Conclusion The purpose of this paper was a categorical settlement to the controversy surrounding the misconceptions involving the belief that data can be recovered following a wipe procedure. This study has demonstrated that correctly wiped data cannot reasonably be retrieved even if it is of a small size or found only over small parts of the hard drive. Not even with the use of a MFM or other known methods. The belief that a tool can be developed to retrieve gigabytes or terabytes of information from a wiped drive is in error. Although there is a good chance of recovery for any individual bit from a drive, the chances of recovery of any amount of data from a drive using an electron microscope are negligible. Even speculating on the possible recovery of an old drive, there is no likelihood that any data would be recoverable from the drive. The forensic recovery of data using electron microscopy is infeasible. This was true both on old drives and has become more difficult over time. Further, there is a need for the data to have been written and then wiped on a raw unused drive for there to be any hope of any level of recovery even at the bit level, which does not reflect real situations. It is unlikely that a recovered drive will have not been used for a period of time and the interaction of defragmentation, file copies and general use that overwrites data areas negates any chance of data recovery. The fallacy that data can be forensically recovered using an electron microscope or related means needs to be put to rest. Still, if you really want to go all medieval on a drive, fire is best.

I'm on the other side of the US from them. Yea, if you're in another country I could see it getting routed weird. My crap used to get routed weird when I lived in Alaska.

Nope. Mine went Richmond, Oakland, Cincinnati, Greenville. Took 3 days.

Really no need for the firewall to have a ssd unless the box you built had one to begin with. They don't exactly have a lot of disk io, so a spinning drive will work just fine. Usually the only thing that kills ours are lightning strikes coming over the cable. Sometimes it just kills the wan network card, other times it takes the whole machine.

The needle on the bullshit meter just flew off. Having worked and occasionally still work for school districts in the US, I can say that yes, the school can confiscate anything that a student uses on school property that damages the property. The network is school property.

Any consumer wifi equipment you pick up will have rp connectors on them. The pineapple was the weird one with the standard polarity connectors. Though I guess it's not standard consumer gear.

It's a cable modem. You'll have to get the cable provider to change the settings, they usually don't allow access to them directly from the client side. Sometimes you can get to them from the wired client side with the defaults, after you change your ip to something like 192.168.0.XXX or 192.168.1.xxx, depends on the isp.

See if this helps. I don't have a windows 7 machine to test it with though. https://support.microsoft.com/en-us/help/230148/how-to-change-the-ip-range-for-the-internet-connection-sharing-dhcp-se You should be able to change the ICS settings to match what the bunny is expecting.

You're using internet connection sharing in Windows. That's where your 192.168.xxx.xxx IP is coming from. Windows creates a router and this is the range it makes.

I've only ever installed them with a local controller. I've thought about setting up raspi-pi's as a controller. Some of our clients don't have server's to install it to, and I hate having to kick someone off their desktop to make a change.

Usually it's the dvr that connects to the cameras. At least the three systems I work with do it that way. You might be able to put a network tap in between and wireshark the creds, but most of the newer cameras connect over https.

Try the wp5 script. Also copy what you get in the terminal when you run the script. That way we can see what you tell the script to use for the connections.

You probably already know this, so putting it out there for the new to radio folks. Use as short as you can coax if you really have to use coax. Make sure what you're using is made for microwave. The stuff they sell at your average home store is not. Microwave grade coax and connectors require special tools to crimp, don't use pliers. Here's an idea for you to ponder. Build a Poe injector set for a raspberry pi and connect the adapter I showed you to that with the yagi. Mount this in a weatherproof box on your antenna spinner. This will keep your coax to the foot or so on the antenna, so minimal signal loss. You can vnc or ssh into the pi from your desktop.

Is that with the cloud keys, or can the desktop controller do it too? I've not seen that option yet.

Yea, once all the hardware is installed it only takes 10-15 minutes to set them all up. We usually set up the controller before any of the hardware swaps, so we can spool up an access point as the old ones are going down. Keeps the down time for the client at a minimum. The one thing I wish Ubiquiti did that Ruckus does is auto configure new hardware. If you have a Ruckus controller on your network, when it sees a new access point it will auto configure it. That would be really handy if you're doing a job by yourself.

If you're doing a fox and hound, just use a usb wifi adapter and a directional antenna. It will be much easier to set up. Any adapter with monitor mode capability and an external antenna attachment will work. This is a good one.

The building is covered with lightning rods, so we think most of the damage was induced voltage on the lines. Basically an EMP. We had suppressors installed at another facility once, took them off about two weeks after. Caused all kinds of connectivity issues, not sure if they were installed correctly though. I think it's weird that a cable modem will usually survive a power surge through the coax, but the wan port of the firewall will almost always blow out...

Just don't run it without the antenna.