Service Providers

https://www.zdnet.com/google-amp/article/cisco-these-wi-fi-access-points-are-easily-owned-by-remote-hackers-so-patch-now/

@black3dynamite said in Miscellaneous Tech News:

@wrx7m said in Miscellaneous Tech News:

Fedora 31 Release Held Up By Installer + DNF Bugs
https://www.phoronix.com/scan.php?page=news_item&px=Fedora-31-Release-Delayed

*Fedora developers had been trying to ship Fedora 31 for their original release target of next Tuesday, 22 October, but that isn't going to happen due to remaining blocker bugs.

At today's meeting they decided F31 is a "No-Go" due to open issues.

Among the blocker bugs at this point are upgrade issues over libgit2.so.28()(64bit) not being found, a DNF exception around armv7hcnl, a dnf-yum upgrade issue from Fedora 30, dnfdragora having complaints about a locked process after updates, and a Fedora 31 KDE Live graphics issue when booting in BIOS mode, among other proposed blockers.*

But also a good thing showing that things are clearly tested before release.

Homeward bound.

@scottalanmiller said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

@JaredBusch said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

@dafyre said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

@Pete-S said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

Is it possible / bad practice to use the first address in the network, for instance 192.168.0.0 (netmask 255.255.255.0) ?

If I remember correctly a long time ago it wasn't possible but nowadays it is. I never use it but when you have small subnets like /29 it could be nice.

@Pete-S : The short answer is No. The longer answer is that it depends on the math.

In 192.168.0.0/24, 192.168.0.0 is the network address... 192.168.0.255 is the broadcast address.

In a 192.168.0.0/23, 192.168.0.0 is the network address, and 192.168.1.255 is the broadcast address.... 192.168.1.0 is a usable IP address in that network.

No that’s not how that works. The first address in a subnet is never usable. The last address in a subnet is never usable. There is no in between. Every single subject has exactly one first address and exactly one last address.

He pointed that out.

Yes in a very confusing way by starting off the short answer is......

There is only one answer to the question

@JaredBusch said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

@dafyre said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

@Pete-S said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

Is it possible / bad practice to use the first address in the network, for instance 192.168.0.0 (netmask 255.255.255.0) ?

If I remember correctly a long time ago it wasn't possible but nowadays it is. I never use it but when you have small subnets like /29 it could be nice.

@Pete-S : The short answer is No. The longer answer is that it depends on the math.

In 192.168.0.0/24, 192.168.0.0 is the network address... 192.168.0.255 is the broadcast address.

In a 192.168.0.0/23, 192.168.0.0 is the network address, and 192.168.1.255 is the broadcast address.... 192.168.1.0 is a usable IP address in that network.

No that’s not how that works. The first address in a subnet is never usable. The last address in a subnet is never usable. There is no in between. Every single subject has exactly one first address and exactly one last address.

He pointed that out.

@dafyre said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

@Pete-S said in Can I use the first IP in a subnet, for instance 192.168.0.0?:

Is it possible / bad practice to use the first address in the network, for instance 192.168.0.0 (netmask 255.255.255.0) ?

If I remember correctly a long time ago it wasn't possible but nowadays it is. I never use it but when you have small subnets like /29 it could be nice.

@Pete-S : The short answer is No. The longer answer is that it depends on the math.

In 192.168.0.0/24, 192.168.0.0 is the network address... 192.168.0.255 is the broadcast address.

In a 192.168.0.0/23, 192.168.0.0 is the network address, and 192.168.1.255 is the broadcast address.... 192.168.1.0 is a usable IP address in that network.

No that’s not how that works. The first address in a subnet is never usable. The last address in a subnet is never usable. There is no in between. Every single subject has exactly one first address and exactly one last address.

End of day reboots are the best. Machine is up for work, but nothing is logged in and the machines don't stay booted up indefinitely.

@stacksofplates mangobot commands!

@Skyetel said in VOIP.ms more secure:

SIP Trunking by IP is so much better than registration, we don't even allow you to register.

About a year ago, a customer came to us from one of our competitors that used SIP Registration. A hacker broke into his PBX, and instead of relaying all the calls through his PBX like they normally do, they got his SIP Trunking username & password for his carrier. They then proceeded to register half a dozen systems and burned through tens of thousands of dollars before the carrier realized something was wrong. They then forced him to pay the bill (which is why he quickly looked to move away to us).

I can rant all day about the pitfalls of SIP Registration, but I shall refrain

Multiple failures in the scenario you listed. Anyone of those failures being not there would’ve made the entire thing not a problem.

@LilAng said in Installing Windows 10 without a Microcoft account:

@scottalanmiller said in Installing Windows 10 without a Microcoft account:

@LilAng said in Installing Windows 10 without a Microcoft account:

OMG!!! this is perfect!!! Thanks @JaredBusch , it will be easier to walk people through an out of the box pc.

We use this constantly

yes and it will be great for my padawan to use as reference as well

I need to update this a little bit. The best thing to do with windows 10 pro, is the click set up for business and domain join (even if no domain). Type in admin username. Leave password blank. Wait for install to complete. Install remote access tool. Set admin account password. Create user account. Reboot.