Hey im in school (in egypt) and im trying to install command and conquer generals but it always needs a fucking admin password. can someone install it and put it on google drive for me? i really fuckin bored with cs 16.

I recently faced the challenge of setting up multiple mailboxes under the same domain for a project I’m working on. After some trial and error, I thought I’d share the process here to help anyone else who might be in the same boat. Here’s a step-by-step guide:

1. Choose Your Email Hosting Provider: First things first, you need to decide on an email hosting service. Some popular ones include Google Workspace, Microsoft 365, and Zoho Mail. Each of these services allows you to create multiple mailboxes under the same domain. I personally went with Google Workspace because of its seamless integration with other Google services.
   
2. Domain Verification: Once you’ve chosen your provider, you’ll need to verify your domain. This usually involves adding a TXT record to your domain’s DNS settings. Your email host will provide detailed instructions on how to do this. It might take a few minutes to a couple of hours for the changes to propagate.
   
3. Create User Accounts: After your domain is verified, you can start creating user accounts/mailboxes. In Google Workspace, this is done through the Admin Console. Go to “Users” and click “Add a user.” Fill in the necessary details like name, email address, and password. Repeat this process for each mailbox you need.
   
4. Configure DNS Settings: To ensure your emails are delivered correctly, you’ll need to configure your domain’s MX (Mail Exchange) records. Your email hosting provider will give you the specific MX records to add. These records tell other mail servers where to deliver emails sent to your domain. Again, this can take some time to propagate.
   
5. Set Up Email Clients: Once the mailboxes are created and the DNS settings are configured, you can set up your email clients (like Outlook, Thunderbird, or the native email apps on your devices) to access these mailboxes. You’ll need the incoming and outgoing server settings, which your email host will provide.
   
6. Add Aliases (Optional): If you want certain mailboxes to receive emails sent to different addresses (like info@yourdomain.com and support@yourdomain.com going to the same inbox), you can set up email aliases. This is usually done in the admin console of your email host.
   
7. Test Everything: Before you announce the new email addresses to the world, send test emails to and from each mailbox to ensure everything is working correctly. Check spam folders and ensure that emails are being delivered as expected.
   
8. Set Up Forwarding and Filters: Depending on your needs, you might want to set up email forwarding or filters. For example, you can forward emails from one mailbox to another or create filters to organize incoming emails automatically.
   

That’s pretty much it! It might seem a bit overwhelming at first, but once you go through the process, it’s pretty straightforward. If you run into any issues, most email hosting providers have comprehensive support documentation and customer service teams that can help you out.
What tools to use for your business? • email warmup: warmup inbox •automate customer support: Algomo • landing pages: leadpages • Publishing: Wordpress • Social Media Marketing - AdEspresso

Hi guys,
I received a second dreaded letter the other day. I'm through the thick of it, and I've cleaned up all the malware, but this is the second time this has happened. I need your best tips to prevent malware incursions on wordpress sites. Our hosting provider is pair.com. I've completed all the remediation steps they requested, but I can't help but think that it's missing something, to have allowed a second breach. The first time they said it was a compromised user account. I could never find evidence of that, it's really possible it was. The second time they said it was because I didn't change the passwords of the users. I did. I setup a salt rotation also. I changed the db passwords and deleted all non-essential users.
Thanks for any help you can provide.
-signed exhausted sys admin, who shouldn't be doing website anything...
"Hello,
We are writing to you from the Security Department at Pair Networks regarding your web hosting account 'acmeinc'.
We have again received multiple third party complaints regarding both attacks and phishing sites related to your account.
In examining the issue it is apparent that, while some malware is new, the intrusion stretches back into other previous intrusions that were not fully and appropriately addressed. As mentioned during the prior incident, there were still issues of which you were informed that were dormant issues from yet prior exploits that were not addressed and that password protections put in place by Pair Networks were circumvented.
This remediation list will need to be fully addressed:

• Remove any malicious files and/or code injections
• Upgrade all Wordpress installs to the latest release
• Update all Wordpress plugins
• Update all Wordpress themes
• Change all Wordpress passwords
• Change Wordpress database passwords and SALTs
• Check that no malicious users were added to the various backends
• Adjust unsecure, world-writable permissions. Typically, files/directories shouldn't have permissions higher than 755. However, "the lower, the better" is a good rule to follow. This is especially true with regards to config files, which should never have permissions higher than 600.

To allow you access to perform these tasks, we have setup password protection so that you can work without risking further intrusion or malware spread. You will need the following credentials to gain access:"

I have 11 Amcrest cams running in Surveillance Station. I created limited login credentials on the cams to use for SS so that SS can't change the A/V parameters on the cameras. Two of the cams refuse to connect using these credentials. The other 9 connect fine. On the cams that won't connect, if I change the login credentials to the limited account and hit Test Connection, it works fine. But when I save the settings, the cams don't show up and I get a warning about Username/Password errors. Logging into the cams directly using these credentials works fine as well. For the two problem cams, only the admin login for the cams work in SS. I don't think it's camera model dependent since I have several cams of the same model that work fine with the limited user login.
Any ideas? I've thought about factory resetting the two problem cams and deleting them from SS, then starting over from scratch. But that's a bit of a pain.

Hi u/PaloCommunity,
I've just finished writing my Discussion Post in the PaloAlto Networks Live Community. I'm copying the content (unformated) below. If you want to view it formated, go to following link: https://live.paloaltonetworks.com/t5/next-generation-firewall/guide-quot-how-to-replace-firewalls-with-minimal-changes-quot/m-p/586777
~Foreword~
Last weekend we changed from old Firewall Hardware to new one.
On our Productionsite we switched from "PA-3250" to "PA-1410".
In our Datacenter, we switched from "PA-5250" to "PA-5410".

I am writing this article in case someone needs an easy way to replace old Hardware.
I wasnt able to find an article/discussion on this topic directly, so I'm writing one.

The Discussion/Article will consist of the following Points:

1. Foreword
2. General Information
3. Our approach
4. "How To" (TLDR)
5. How to replace a Firewall with "Device States"-Export (In Detail)
6. "Nice to know" Information

~General Information~
Some Information about our envrionment:
-We use Panorama to manage our Firewalls
-We use "Active/Passive" on all "HA"-Sites

Initial Situation:
-We wanted to do a "1:1" replacement/swap,
This means we wanted to:
-Use the same "Mgmt Ips"
-Use the Same Hostname
-Use similar Interfaces
-Use the same Ruleset
-Same Objects, NAT Rules, VPNs, etc…
-We wanted to have minimal Downtime during the swap


~Our approach~
We asked ourself: "What is the best approach for a replacement like this"
We thought "If we have the whole config in place on the new device, including Ips, Interfaces, Ruleset, etc., we should be able to "Unplug" the old Devices and just have the new one "Active" running".

After defining our way to go, we started searching on "How to export Config, including Ruleset etc"
Thats where we stumbled upon the "Device State*"
-What is "Device State"?
-Device State is essentially the config, including Ruleset, thats been pushed from panorama. (The device state contains ALL information pushed from the Panorama + the "running config". NAT-Rules, Interfaces etc. will also be included in this .xml)

Once we had this information we started on the replacement (TLDR follows, to save you time in case that verison is not feasible for you)


~"How To" (TLDR)~
(TLDR) Quick Rundown:

• Export Original Device State
• Setup new Firewall (Mgmt IP and Password)
  • Export "Device State" of new Device
  • Replace "Admin"-User in "Original-Device-State" with the "Admin"-User of the "New-Device-State"
• Import Edited, Original-Device-State to new Hardware
• "Validate commit"
  • CleanUp "Commit-Errors" in imported Config
• Commit
• Finished

~How to replace a Firewall with "Device States"-Export~

1. Export Original Device State

"How to export a Device State of old Hardware?"
● Go to "Device -> Setup -> Operations -> "Export device state""
Save the Device State with a proper name, youll need it later (PA01001_OriginalHardware.tgz")

1. Setup new Firewall

You'll need to perform the initial Setup for your new Firewall. (CLI)
● Setup Password AND COMMIT
● Setup Mgmt IP (So you can access the Web-UI)
Example: set deviceconfig system ip-address 192.168.0.1 netmask 255.255.0.0

1. Export "Device State" of new Device

After successfully setting up "Mgmt-IP" and "Password" for the new Firewall, export the Device State of the new Firewall (WebUI)
● Go to "Device -> Setup -> Operations -> "Export device state""
Save the Device State with a proper name (PA01001_NewHardware.tgz")

1. Replace "Admin"-User in "PA01001_OriginalHardware.tgz" with the "Admin"-User of the "PA01001_NewHardware.tgz"

You have to replace the Adminuser, in the "PA01001_OriginalHardware.tgz" with the Adminuser, of the "PA01001_NewHardware.tgz" because passwords are hashed by the device.
!The hashed password of the "PA01001_OriginalHardware.tgz" will not work on the new device!
To replace the Admin user you have to do the following:
● Open "PA01001_OriginalHardware.tgz" and "PA01001_NewHardware.tgz" in "7zip"
● Search for "running-config.xml" in both device states and open it by hiting "Edit"
● In the "PA01001_NewHardware.tgz" Search for and copy it
Copy the whole block:

59193ioasdo%93osaPASSWORDHASH


yes



● In the "PA01001_OriginalHardware.tgz" running-config, search for and replace this user with the just copied user from above
● Save the "PA01001_OriginalHardware.tgz"

1. Import Edited, "PA01001_OriginalHardware.tgz" to new Hardware

Now, after you edited the "PA01001_OriginalHardware.tgz" to have the new user, you can start importing the device state to the new Firewall.
● Log on to WebUI of the new Firewall
● Go to "Device -> Setup -> Operations -> "Import device state""
● Select the "PA01001_OriginalHardware.tgz" file and hit "Ok"
You might have to reload the page (and maybe give yourself another IP) because the Mgmt-IP has now been swapped to the Mgmt-IP of the "PA01001_OriginalHardware.tgz"

1. "Validate commit"

Now, once youve uploaded the "PA01001_OriginalHardware.tgz" you can hit "Vallidate Commit"
During this step you might see some errors that you have to clean up in your "PA01001_OriginalHardware.tgz"
Example of errors during the Vallidate:
deviceconfig -> setting -> management -> quota-settings -> chassis-quota unexpected here
deviceconfig -> setting -> management -> quota-settings is invalid
deviceconfig -> setting -> management is invalid
deviceconfig -> setting is invalid
deviceconfig is invalid
rulebase -> security -> rules -> Block_TorAddresses -> source 'panw-torexit-ip-list' is not an allowed keyword
rulebase -> security -> rules -> Block_TorAddresses -> source panw-torexit-ip-list is an invalid ipv4/v6 address
rulebase -> security -> rules -> Block_TorAddresses -> source panw-torexit-ip-list invalid range start IP
rulebase -> security -> rules -> Block_TorAddresses -> source 'panw-torexit-ip-list' is not a valid reference
rulebase -> security -> rules -> Block_TorAddresses -> source is invalid
rulebase -> security -> rules is invalid
rulebase -> security is invalid
rulebase is invalid
vsys is invalid
devices is invalid
log-settings -> correlation unexpected here
log-settings is invalid
shared is invalid

Example on "How to clean up "chassis-quota unexpected here""
● Open "PA01001_OriginalHardware.tgz" and search for "running-config.xml"
● Search for
● Delete the whole block from the Device State:



16
32
5
2
2
2
20
20



● Save the "PA01001_OriginalHardware.tgz" again
● Upload the Updated "PA01001_OriginalHardware.tgz" and hit "Validate Commit" again.
● If there are still errors, you have to clean up those errors as well (might also be settings in "template-config.xml" for example)
● Repeat those steps until there are no errors left


7. Commit
After you cleaned up the commit errors, and "Vallidate Commit" does not display any more errors, you are ready to hit "Commit"
Once you've hit "Commit", you are done and ready to use the new Firewall

We had literally no downtime. The worst downtime with this method was 6 ping losses in our Datacenter.
It was my first replacement I've ever performed so I was kinda nervours at the beginning, but after the replacement of the first HA-Pair the way to go was pretty clear and I was calm for the following replacements.





~"Nice to know" Information~

• I disabled "ZTP" (ZeroTouchProvisioning) immediately after first boot of the new Firewall
• Remember to commit after changing the password via CLI!
• To have the smoothes transition of old hardware to new one, I recommend activating "Trial" Licenses for the new Hardware.
  • With trial licenses you are able to download content updates, EDLs, etc…
• Make sure the Interface speed of the new Hardware matches the interface speed of the old hardware
  • If Interface Speed differs, you have to swap interfaces (GUI or CLI) after successfully importing the "PA01001_OriginalHardware.tgz"
• If your setting up a new "HA-Pair" you have to export/import the HA Key of both new devices

If I'd had to replace Firewalls next week, I would use the same method. Once you get used to interpreting the Error Messages during "Validate Commit", its smooth sailing.

If you have any questions, feel free to ask and imma try to get back to you asap.

As title says. The very first Frigate+ model was around the same, which is both expected and unexpected. Expected, because I only uploaded the bare minimum required to generate a model, unexpected because it's supposed to be based on a much better base model.
Next, in about a week or two, I required my 2nd model which has many hundred if not thousand verified images. Cautiously done. Yet, it's actually getting worse. Very, very many false positives.
Any idea or strategy to follow? Go back to base model, start over? Go back to first version Frigate+? Use this second, bad model and keep sending in corrected falsepositives?
Thanks
Edit: as proposed, sharing my config for reference:

# logging settings logger: logs: frigate.record.maintainer: debug # go2rtc streams - all input streams defined here go2rtc: streams: driveway: - rtsp://admin:@10.31.17.101:554/Streaming/Channels/101 driveway_sub: - rtsp://admin:@10.31.17.101:554/Streaming/Channels/102 Szabadka_str_side: - rtsp://admin:@10.31.17.102:554/Streaming/Channels/101 Szabadka_str_side_sub: - rtsp://admin:@10.31.17.102:554/Streaming/Channels/102 Drava_str_side: - rtsp://admin:@10.31.17.103:554/Streaming/Channels/101 Drava_str_side_sub: - rtsp://admin:@10.31.17.103:554/Streaming/Channels/102 porch: - rtsp://admin:@10.31.17.104:554/Streaming/Channels/101 porch_sub: - rtsp://admin:@10.31.17.104:554/Streaming/Channels/102 webrtc: candidates: - 10.31.17.100:8555 - stun:8555 # cameras' definitions - inputs are used from go2rtc cameras: driveway: enabled: true birdseye: order: 1 ui: order: 1 ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/driveway roles: [record] - path: rtsp://127.0.0.1:8554/driveway roles: [detect] motion: mask: - 0,70,0,0,369,0,374,69 porch: enabled: true birdseye: order: 2 ui: order: 2 ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/porch roles: [record] - path: rtsp://127.0.0.1:8554/porch roles: [detect] motion: mask: - 0,70,0,0,369,0,374,69 Szabadka_str_side: enabled: true birdseye: order: 3 ui: order: 3 ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/Szabadka_str_side roles: [record] - path: rtsp://127.0.0.1:8554/Szabadka_str_side roles: [detect] motion: mask: - 0,720,475,720,410,522,343,184,334,78,0,79 - 0,72,366,72,369,0,0,0 Drava_str_side: enabled: true birdseye: order: 4 ui: order: 4 ffmpeg: inputs: - path: rtsp://127.0.0.1:8554/Drava_str_side roles: [record] - path: rtsp://127.0.0.1:8554/Drava_str_side roles: [detect] motion: mask: - 837,290,762,720,1280,720,1280,0,844,0 - 0,80,368,73,378,0,0,0 ########################################################################################################################## # AMD iGPU acceleration ffmpeg: hwaccel_args: preset-vaapi # AI Detection type # Google Coral detectors: coral: type: edgetpu device: usb # Frigate+ model model: path: plus:// # detection settings detect: enabled: true width: 1280 height: 720 fps: 5 min_initialized: 5 # Optional: Number of frames without a detection before Frigate considers an object to be gone. (default: 5x the frame rate) max_disappeared: 50 # Optional: Configuration for stationary object tracking stationary: # Optional: Frequency for confirming stationary objects (default: same as threshold) # When set to 1, object detection will run to confirm the object still exists on every frame. # If set to 10, object detection will run to confirm the object still exists on every 10th frame. interval: 100 # Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s) threshold: 100 objects: track: - person - cat - dog # MQTT (for HomeAssistant) mqtt: enabled: true host: 192.168.0.67 user: frigate password:  # Birdseye, live and UI settings birdseye: enabled: true mode: continuous quality: 1 height: 720 restream: true live: height: 1440 quality: 1 ui: live_mode: mse # recording settings record: enabled: true # Optional: Number of minutes to wait between cleanup runs (default: shown below) # This can be used to reduce the frequency of deleting recording segments from disk if you want to minimize i/o expire_interval: 60 # Optional: Sync recordings with disk on startup and once a day (default: shown below). sync_recordings: true # Optional: Retention settings for recording retain: # Optional: Number of days to retain recordings regardless of events (default: shown below) # NOTE: This should be set to 0 and retention should be defined in events section below # if you only want to retain recordings of events. days: 7 # Optional: Mode for retention. Available options are: all, motion, and active_objects # all - save all recording segments regardless of activity # motion - save all recordings segments with any detected motion # active_objects - save all recording segments with active/moving objects # NOTE: this mode only applies when the days setting above is greater than 0 mode: all # Optional: Recording Export Settings export: # Optional: Timelapse Output Args (default: shown below). # NOTE: The default args are set to fit 24 hours of recording into 1 hour playback. # See https://stackoverflow.com/a/58268695 for more info on how these args work. # As an example: if you wanted to go from 24 hours to 30 minutes that would be going # from 86400 seconds to 1800 seconds which would be 1800 / 86400 = 0.02. # The -r (framerate) dictates how smooth the output video is. # So the args would be -vf setpts=0.02*PTS -r 30 in that case. timelapse_args: -vf setpts=0.0007*PTS -r 30 # Optional: Event recording settings events: # Optional: Number of seconds before the event to include (default: shown below) pre_capture: 5 # Optional: Number of seconds after the event to include (default: shown below) post_capture: 5 # Optional: Objects to save recordings for. (default: all tracked objects) #objects: # - person # Optional: Restrict recordings to objects that entered any of the listed zones (default: no required zones) #required_zones: [] # Optional: Retention settings for recordings of events retain: # Required: Default retention days (default: shown below) default: 30 # Optional: Mode for retention. (default: shown below) # all - save all recording segments for events regardless of activity # motion - save all recordings segments for events with any detected motion # active_objects - save all recording segments for event with active/moving objects # # NOTE: If the retain mode for the camera is more restrictive than the mode configured # here, the segments will already be gone by the time this mode is applied. # For example, if the camera retain mode is "motion", the segments without motion are # never stored, so setting the mode to "all" here won't bring them back. mode: all # Optional: Per object retention days #objects: # person: 15 # snapshots config snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) enabled: true # Optional: save a clean PNG copy of the snapshot image (default: shown below) clean_copy: true # Optional: print a timestamp on the snapshots (default: shown below) timestamp: false # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: true # Optional: crop the snapshot (default: shown below) crop: false # Optional: height to resize the snapshot to (default: original size) #height: 175 # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) #required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 30 # Optional: Per object retention days #objects: #person: 15 # Optional: quality of the encoded jpeg, 0-100 (default: shown below) quality: 100 # telemetry settings telemetry: stats: amd_gpu_stats: true network_bandwidth: true 

For example - I'm getting free internet. It was left in my flat when I moved in and I expected it to stop working after a week or so but it's still going over a year later. They hadn't changed the WiFi code or the admin password. At some point I'm expecting it to stop

Is there a way to seed data automatically to a PostgreSQL when it is being provisioned?
Especially when I am using Docker to spin up the instance like this:

 db: image: postgres:alpine container_name: cromp-db volumes: - type: bind source: ./core/init-db.sql target: /docker-entrypoint-initdb.d/init-db.sql environment: - POSTGRES_USER=psqladmin - POSTGRES_PASSWORD=admin ports: - target: 5432 published: 5432 networks: - cromp-net 

Are you ready to supercharge your home network with the WL WN531MX3 AX3000 Router setup . Are you ready to supercharge your home network with the WL WN531MX3 AX3000 Router setup ? Setting up this powerful router is easier than you might think, and we're here to guide you through the process step by step. Whether you're a networking newbie or a seasoned pro, our comprehensive guide will ensure you get the most out of your new router. Let's dive in!

Preparing for Setup

Before we begin, ensure you have the following:

• WL WN531MX3 AX3000 Router
• Power adapter
• Ethernet cable
• Computer or mobile device with Wi-Fi capabilities

Understanding the Basics

Before we dive into the setup process, let's take a moment to understand some key concepts:

What is the WL WN531MX3 AX3000 Router?

The WL WN531MX3 AX3000 Router is a high-performance router that offers fast and reliable Wi-Fi connectivity. It supports the latest Wi-Fi standards and is ideal for streaming, gaming, and browsing.

Why Setup Your Router?

Setting up your router allows you to create a secure Wi-Fi network, customise your settings, and ensure optimal performance.

Getting Started

To begin the setup process, follow these simple steps:

1. Unboxing: Start by unboxing your router and ensuring that all the necessary components are included.
2. Placement: Place your router in a central location to ensure optimal Wi-Fi coverage throughout your home or office.
3. Power On: Plug in your router and power it on. Wait for the power LED to turn solid green.
4. Connectivity: Use an Ethernet cable to connect your router to your modem. Ensure that the cable is securely connected to both devices.

Setting Up Your Router

Once you've completed the initial setup steps, you can proceed with configuring your router:

Accessing the Router's Web Interface

To access the router's web interface, follow these steps:

1. Open a web browser on a device connected to your router's network.
2. Enter "192.168.10.1" in the address bar and press Enter.
3. You will be prompted to enter a username and password. The default credentials are usually "admin" for both the username and password. If these credentials don't work, refer to your router's user manual for the correct login information.

Setting Up Your Wi-Fi Network

Once you've accessed the router's web interface, you can proceed with setting up your Wi-Fi network:

1. Navigate to the Wireless settings section of the web interface.
2. Select the network name (SSID) for your Wi-Fi network and set a password for it. Make sure to choose a strong password to secure your network.

Firmware Update

It's essential to keep your router's firmware up to date to ensure optimal performance and security. To update your firmware, follow these steps:

1. Check for firmware updates in the router's web interface.
2. If an update is available, download and install it following the on-screen instructions.

Setting Up as an Access Point

To set up your router as an access point, follow these steps:

1. Navigate to the Access Point settings section of the web interface.
2. Enable the Access Point mode and configure the settings as per your network requirements.

Resetting Your Router

If you encounter any issues during the setup process or need to restore your router to its factory settings, you can reset it by following these steps:

1. Locate the reset button on your router (usually located on the back or bottom of the device).
2. Press and hold the reset button for at least 10 seconds.
3. Release the reset button and wait for the router to restart.

Conclusion

Congratulations! You've successfully your WL WN531MX3 AX3000 Router setup and unlocked a world of high-speed internet possibilities. Whether you opted for the WPS method or the web-based setup, you're now equipped to enjoy seamless connectivity and robust performance throughout your home. Remember to explore the router's advanced settings and features to further enhance your networking experience.

Having trouble with your TP-Link router's WiFi? You're not alone. Whether you're experiencing intermittent connectivity, slow speeds, or no connection at all, these issues can be incredibly frustrating. Fortunately, there are several steps you can take to troubleshoot and resolve these common problems. If you need immediate assistance, don't hesitate to call our expert support team at +1–888–464–7211.

Common Issues and Solutions

1. No WiFi Signal

Check the Basics

• Power Cycle the Router: Sometimes, a simple restart can fix connectivity issues. Unplug the router, wait 30 seconds, and then plug it back in.
• Check Connections: Ensure all cables are securely connected. The power cord, Ethernet cables, and any other connections should be firmly in place.

Reset the Router

• Soft Reset: Press the reset button on the router for about 10 seconds. This will reboot the device but retain your settings.
• Hard Reset: If a soft reset doesn’t work, perform a hard reset. Hold the reset button for about 30 seconds until the router restarts. Note that this will erase all your settings, so you'll need to reconfigure your network.

2. Slow WiFi Speeds

Optimize Placement

• Central Location: Place your router in a central location in your home for optimal coverage.
• Reduce Interference: Keep the router away from other electronic devices that might cause interference, such as microwaves and cordless phones.

Update Firmware

• Check for Updates: Go to the TP-Link support website and download the latest firmware for your model. Follow the instructions to update your router’s firmware, which can resolve performance issues and security vulnerabilities.

3. Intermittent Connectivity

Channel Interference

• Change the WiFi Channel: Log in to your router’s admin panel (usually by typing 192.168.0.1 or 192.168.1.1 in your web browser). Navigate to the wireless settings and change the channel. Channels 1, 6, and 11 are generally the best options for 2.4 GHz networks.

Bandwidth Management

• Enable QoS (Quality of Service): This feature prioritizes bandwidth for critical applications, ensuring that essential services like video calls and online gaming are not interrupted by less important traffic.

4. Devices Can't Connect

Check Security Settings

• Correct Password: Ensure you are entering the correct WiFi password. If you've forgotten it, you can reset it through the router’s admin panel.
• MAC Filtering: Make sure MAC filtering is disabled or that your device’s MAC address is added to the allowed list.

Network Mode

• Compatibility: Set your router to a mixed mode (e.g., 802.11 b/g/n) to ensure compatibility with older devices.

5. No Internet Access

ISP Issues

• Check with Your ISP: Sometimes, the problem might be with your internet service provider. Contact them to check if there are any outages or service issues in your area.

Modem Issues

• Modem Reset: If your router is connected to a modem, try resetting the modem as well. Unplug it, wait 30 seconds, and plug it back in.

When to Call for Help

If you’ve tried all the above solutions and your TP-Link router's WiFi is still not working, it might be time to call in the experts. Our dedicated support team at +1–888–464–7211 is available to help you resolve any issues quickly and efficiently. Whether you need help with advanced troubleshooting, firmware updates, or configuration, we're here to assist you 24/7.

Conclusion

Dealing with WiFi issues can be a hassle, but with a systematic approach, most problems can be resolved. From checking basic connections to optimizing settings and updating firmware, there are many steps you can take to restore your TP-Link router's performance. And remember, expert help is just a phone call away at +1–888–464–7211. Stay connected and enjoy seamless internet access with TP-Link!

i wanna get a vpn on my school laptop to be able to play stuff but i cant since the microsoft store has been blocked by an admin and even the microsoft website redirects me to the already blocked microsoft store. downloading most things on this laptop doesnt work either since for almost everything, you need the administrator username and password. can anyone please help????

Hello active directory people
I am having some problems with the encryption in windows Laps in Active Directory. I am using Samba-AD, so I have followed this guide: https://samba.tranquil.it/doc/en/samba_advanced_methods/samba_configure_laps.html
Using the guide, I was able to expire the password seamlessly, like you're supposed to in LAPS. (Which is really nice btw) However, I want to encrypt the passwords, as I'm afraid of the security problems of sending unencrypted passwords.
So I added the setting "Enable password Encryption set to Enabled"to the GPO, with Domain Admins group set as the password decryptors. And suddenly LAPS stopped working. Looking at the event viewer on the client computers at Applications and Services Logs > Microsoft > Windows > LAPS > Operational. I see the Errors:
"" LAPS failed to update Active Directory with the new password. The current password has not been modified. Error code: 0x80090034 See https://go.microsoft.com/fwlink/?linkid=2220550 for more information.""
Preceded by the error:
"" Encryption of the new password failed. Error code: 0x80090034 This problem may occur if a KDS root key is not available. Verify that a KDS root key is available by running the Get-KdsRootKey PowerShell cmdlet, and also verify that the root key's EffectiveTime field is valid right now. If a KDS root key is not present, you must add one by running the Add-KdsRootKey PowerShell cmdlet with the -EffectiveImmediately parameter. Allow sufficient time for the new key to replicate around your forest. See https://go.microsoft.com/fwlink/?linkid=2220550 for more information. ""
I didn't have a KDS root key, so i created one and waited the 10+ hours, but it still didn't work. When I run "Get-KDSrootKey" on my client as a user I don't get a response, but when i run as a admin user on a client computer i get the KDSrootKey. I'm starting to think that the KDS root key is maybe not the underlying problem, but i cant guess what else it can be. I found this post https://answers.microsoft.com/en-us/msoffice/forum/all/error-code-80090034/2c968bd7-8f20-4878-83cc-2296e26d5aad and tried following it, but it didn't work. I have looked into replication issues, but it doesn't seem that there is any.
I hope you can help me, as I am very lost and have had problems with this for a looong time now. I would really appreciate any help, as I'm very lost, and new to these things :) Thank you!

Hello all you smart Sysadmins
I am having some problems with the encryption in windows Laps in Active Directory. I am using Samba-AD, so I have followed this guide: https://samba.tranquil.it/doc/en/samba_advanced_methods/samba_configure_laps.html
Using the guide, I was able to expire the password seamlessly, like you're supposed to in LAPS. (Which is really nice btw) However, I want to encrypt the passwords, as I'm afraid of the security problems of sending unencrypted passwords.
So I added the setting "Enable password Encryption set to Enabled"to the GPO, with Domain Admins group set as the password decryptors. And suddenly LAPS stopped working. Looking at the event viewer on the client computers at Applications and Services Logs > Microsoft > Windows > LAPS > Operational. I see the Errors:
"" LAPS failed to update Active Directory with the new password. The current password has not been modified. Error code: 0x80090034 See https://go.microsoft.com/fwlink/?linkid=2220550 for more information.""
Preceded by the error:
"" Encryption of the new password failed. Error code: 0x80090034 This problem may occur if a KDS root key is not available. Verify that a KDS root key is available by running the Get-KdsRootKey PowerShell cmdlet, and also verify that the root key's EffectiveTime field is valid right now. If a KDS root key is not present, you must add one by running the Add-KdsRootKey PowerShell cmdlet with the -EffectiveImmediately parameter. Allow sufficient time for the new key to replicate around your forest. See https://go.microsoft.com/fwlink/?linkid=2220550 for more information. ""
I didn't have a KDS root key, so i created one and waited the 10+ hours, but it still didn't work. When I run "Get-KDSrootKey" on my client as a user I don't get a response, but when i run as a admin user on a client computer i get the KDSrootKey. I'm starting to think that the KDS root key is maybe not the underlying problem, but i cant guess what else it can be. I found this post https://answers.microsoft.com/en-us/msoffice/forum/all/error-code-80090034/2c968bd7-8f20-4878-83cc-2296e26d5aad and tried following it, but it didn't work. I have looked into replication issues, but it doesn't seem that there is any.
I hope you can help me, as I am very lost and have had problems with this for a looong time now. I would really appreciate any help, as I'm very lost, and new to these things :) Thank you!

Hey! I have been through it for the last couple of weeks trying to figure this out like many others. I reached out to xfinity tech support multiple times on all ends and was always given incorrect information. They couldn't seem to understand that the bands need to be on their own individual isolated channels, not supported up thru 2.4-6 G. On their end, they're not seeing that the bands are not individual like we see it in our Xfinity app. I think some of the confusion is that on the consumer side we don't know that band steering is being used, and we would like to have control over our own functionality rather than xfinity automating everything so we cannot change our settings. Or the devices should just be compatible. There is *no longer* a separate "NETWORK NAME - 2.4G / NETWORK NAME - 5G" different login setting. It's all the same network name and password you setup. Anyway, most of the advice I have seen in all the forums asking the same question was also not helpful to solve the issue. But! I figured out how to fix this finally and everything is up and running. I also had trouble during my initial gateway setup after starting service where the app was not working at all and the connection setup always failed. It was ultimately because the error notification kept saying "must use WPA3 password." I told the customer service specialist multiple times but they were going to send someone out because it wasn't working. The problem was that the security mode for the password type was not set correctly in the settings. I had to select WPA3 Personal Only, then I could proceed to change my password and continue with the setup to finally allow me to login and connect to the internet service/network and not just the router. If you're having issues during setup with your new service where your gateway modem is working and connected but you can't connect to the internet -- go into your app settings and make sure that the security mode you selected for login to your network is the one your device requires you to use (WPA2 or WPA3). I think this is because my devices are newer 2019+ apple and require the newer protocols. I'm going to try to make a video to explain it at some point to show. The problem with the smart devices that require the 2.4G band is a similar issue. (The problem isn't unique to Google Nest devices. It can be any 2.4G WPA2 device, like a Dyson smart device, a Ring door cam, Smart TV, etc). There are a few different steps you have to take:

1. go to your xfinity app and do the following: wifi > wifi details > edit wifi settings > security mode: WPA3 - Personal Transition (NOT PERSONAL ONLY). This is necessary because the older smart devices that require the 2.4G IPv6 protocol will also require a WPA2 security protocol and cannot "see" or find WPA3 networks. When you select transition mode you allow the network and device to automatically communicate with one another based on which one they use, either WPA2 or WPA3. If it is set to WPA3 Only, then the WPA2 devices will not connect, and if set to WPA2 only, the WPA3 devices will not connect. Note that there is a toggle function that says "split bands" -- THIS DOES NOT WORK. It will automatically undo itself no matter how many times you toggle it on and select save. Don't worry about it.
   
2. login to a web browser and type in 10.0.0.1 (from your home network. not remotely)
   
3. under username and password type: username:admin / password: password. This is universal at first. Next you will change your password to whatever you want it to be. The username will always remain "admin." Note: the login is NOT your xfinity login info or your network login info.
   
4. Select: connection > wifi . You will now see a page with the individual bands: 2.4G, 5G, and 6G. Select "edit" next to the 5G band and toggle "disable" > save settings. Do the same to disable the 6G band.
   
5. Next go to: connection > status. You will notice that your 2.4 G band is now the only one "active" and the other two are disabled. You will also see that your security mode was changed to "WPA3 Personal transition" mode. You will notice an indicator count for what devices are connected to what band.
   
6. Select the "firewall" dropdown from the lefthand menu. Select "IPv4" and change this security setting to "minimum security low." Save settings. Now select "IPv6" and change this setting to "custom." Make sure that no additional "Block _" boxes are checked. Save settings.
   

Now you should be able to find your network on your device and connect the device to wifi to finish your setup process! For me, I had to reset the Google Nest Smoke Detector following the reset settings. I also uninstalled the Google Nest app. I turned my phone off and back on. I reinstalled the Nest app. I did not have to uninstall and reinstall the Dyson app. My iPhone and Macbook automatically still joined the network no problem because the login info is the same due to the band steering. I just got a notification on my Macbook saying that the WPA3 protocol was changed and said ok. For my Dyson hot and cool air filter I was able to pair the device and the network finally showed up. I followed the settings in the app and now that the network knows the "MAC address of the device" it is stored in the network's memory and they can find and communicate with each other now. Same with the Google Nest. If it doesn't work right away just try another time and it should work.

Important: the reason they automatically merge the bands and steer them is because the 2.4G is more unstable. This is true. You might notice that the connectivity will drop out occasionally for the devices which could explain why it might take another try to finish your setup. Don't worry about it. It will reconnect on it's own.

Now that your smart devices are connected and setup is finished, and your network knows their MAC addresses, you can revert all the changes you made to your network settings to go back to full functionality (2.4G-6 and increase your firewall security standards back up to your desired level. You just follow the reverse order of what you just did. Keep the 2.4G as is of course, but select: "5G > edit" and toggle enable on. Do the same for 6G. Now all your bands are turned back on and you have full access again. Go back to "firewall" and change the IPV4 and IPV6 settings. You will see on the top menu bar in the right that your security is back to "medium."

Go back to "connection > status." You will notice that all your bands are now active. You can see the device count for how many devices are connected and to which band they are connected. This may drop in and out so don't worry if you don't see the correct total. Sometimes the nest will drop out but it will reconnect itself on it's own in a few minutes. You can verify this on your phone by: Going to the Nest app and seeing that your "Protect" or whatever device you setup is good. You can go to the Dyson app and see that it is connected and get your status updates. You can also go to the xfinity app and see what devices are connected to your network as you usually would. Again, this might drop in and out with the Google nest. But! all your settings are restored and all your devices are now fully functioning and connected to your network :) You also might get notifications from xfinity on your iPhone once the devices are finally successfully paired to your network. Cool!

Important note: you can also use the 10.0.0.1 admin tool to manually add a device's MAC address if, for some reason, you still can't get things to work. I thankfully didn't have to do this because I figured out the solution, but it was going to be my next attempt. Thankfully, the Dyson has the MAC address for the device printed on the inside of the device. However, Google Nest unfortunately does not do this and you have to already be connected in to the app to view the system info. However, you could do a workaround for that by taking your device someplace else and using their wifi (as long as it is 2.4 WPA2 IPV6) to connect and setup the device in the app in order to find the MAC address for the device in the settings in the Nest app. Then you can take the device back home to your network, reset, and try to manually add the MAC address now that you found it (hopefully you took a screenshot or something :) ) Thankfully I didn't have to do this either, but it also would have been my next attempt.

Also, make sure you keep your password settings that you changed in your xfinity app to WPA3 Transition Mode. It'll stay that way for both 2.4G and 5G. This is important because the devices still need to be able to communicate and can only use WPA2. Also if in the future you have this problem again with another product, like perhaps an older Smart TV, you will already have the WPA2 functionality enabled.

I hope this was helpful! It's 3am but I'm so glad I eventually figured it out on my own!

Hey! I have been through it for the last couple of weeks trying to figure this out like many others. I reached out to xfinity tech support multiple times on all ends and was always given incorrect information. They couldn't seem to understand that the bands need to be on their own individual isolated channels, not supported up thru 2.4-6 G. On their end, they're not seeing that the bands are not individual like we see it in our Xfinity app. I think some of the confusion is that on the consumer side we don't know that band steering is being used, and we would like to have control over our own functionality rather than xfinity automating everything so we cannot change our settings. Or the devices should just be compatible. There is *no longer* a separate "NETWORK NAME - 2.4G / NETWORK NAME - 5G" different login setting. It's all the same network name and password you setup. Anyway, most of the advice I have seen in all the forums asking the same question was also not helpful to solve the issue. But! I figured out how to fix this finally and everything is up and running. I also had trouble during my initial gateway setup after starting service where the app was not working at all and the connection setup always failed. It was ultimately because the error notification kept saying "must use WPA3 password." I told the customer service specialist multiple times but they were going to send someone out because it wasn't working. The problem was that the security mode for the password type was not set correctly in the settings. I had to select WPA3 Personal Only, then I could proceed to change my password and continue with the setup to finally allow me to login and connect to the internet service/network and not just the router. If you're having issues during setup with your new service where your gateway modem is working and connected but you can't connect to the internet -- go into your app settings and make sure that the security mode you selected for login to your network is the one your device requires you to use (WPA2 or WPA3). I think this is because my devices are newer 2019+ apple and require the newer protocols. I'm going to try to make a video to explain it at some point to show. The problem with the smart devices that require the 2.4G band is a similar issue. (The problem isn't unique to Google Nest devices. It can be any 2.4G WPA2 device, like a Dyson smart device, a Ring door cam, Smart TV, etc). There are a few different steps you have to take:

1. go to your xfinity app and do the following: wifi > wifi details > edit wifi settings > security mode: WPA3 - Personal Transition (NOT PERSONAL ONLY). This is necessary because the older smart devices that require the 2.4G IPv6 protocol will also require a WPA2 security protocol and cannot "see" or find WPA3 networks. When you select transition mode you allow the network and device to automatically communicate with one another based on which one they use, either WPA2 or WPA3. If it is set to WPA3 Only, then the WPA2 devices will not connect, and if set to WPA2 only, the WPA3 devices will not connect. Note that there is a toggle function that says "split bands" -- THIS DOES NOT WORK. It will automatically undo itself no matter how many times you toggle it on and select save. Don't worry about it.
   
2. login to a web browser and type in 10.0.0.1 (from your home network. not remotely)
   
3. under username and password type: username:admin / password: password. This is universal at first. Next you will change your password to whatever you want it to be. The username will always remain "admin." Note: the login is NOT your xfinity login info or your network login info.
   
4. Select: connection > wifi . You will now see a page with the individual bands: 2.4G, 5G, and 6G. Select "edit" next to the 5G band and toggle "disable" > save settings. Do the same to disable the 6G band.
   
5. Next go to: connection > status. You will notice that your 2.4 G band is now the only one "active" and the other two are disabled. You will also see that your security mode was changed to "WPA3 Personal transition" mode. You will notice an indicator count for what devices are connected to what band.
   
6. Select the "firewall" dropdown from the lefthand menu. Select "IPv4" and change this security setting to "minimum security low." Save settings. Now select "IPv6" and change this setting to "custom." Make sure that no additional "Block _" boxes are checked. Save settings.
   

Now you should be able to find your network on your device and connect the device to wifi to finish your setup process! For me, I had to reset the Google Nest Smoke Detector following the reset settings. I also uninstalled the Google Nest app. I turned my phone off and back on. I reinstalled the Nest app. I did not have to uninstall and reinstall the Dyson app. My iPhone and Macbook automatically still joined the network no problem because the login info is the same due to the band steering. I just got a notification on my Macbook saying that the WPA3 protocol was changed and said ok. For my Dyson hot and cool air filter I was able to pair the device and the network finally showed up. I followed the settings in the app and now that the network knows the "MAC address of the device" it is stored in the network's memory and they can find and communicate with each other now. Same with the Google Nest. If it doesn't work right away just try another time and it should work.

Important: the reason they automatically merge the bands and steer them is because the 2.4G is more unstable. This is true. You might notice that the connectivity will drop out occasionally for the devices which could explain why it might take another try to finish your setup. Don't worry about it. It will reconnect on it's own.

Now that your smart devices are connected and setup is finished, and your network knows their MAC addresses, you can revert all the changes you made to your network settings to go back to full functionality (2.4G-6 and increase your firewall security standards back up to your desired level. You just follow the reverse order of what you just did. Keep the 2.4G as is of course, but select: "5G > edit" and toggle enable on. Do the same for 6G. Now all your bands are turned back on and you have full access again. Go back to "firewall" and change the IPV4 and IPV6 settings. You will see on the top menu bar in the right that your security is back to "medium."

Go back to "connection > status." You will notice that all your bands are now active. You can see the device count for how many devices are connected and to which band they are connected. This may drop in and out so don't worry if you don't see the correct total. Sometimes the nest will drop out but it will reconnect itself on it's own in a few minutes. You can verify this on your phone by: Going to the Nest app and seeing that your "Protect" or whatever device you setup is good. You can go to the Dyson app and see that it is connected and get your status updates. You can also go to the xfinity app and see what devices are connected to your network as you usually would. Again, this might drop in and out with the Google nest. But! all your settings are restored and all your devices are now fully functioning and connected to your network :) You also might get notifications from xfinity on your iPhone once the devices are finally successfully paired to your network. Cool!

Important note: you can also use the 10.0.0.1 admin tool to manually add a device's MAC address if, for some reason, you still can't get things to work. I thankfully didn't have to do this because I figured out the solution, but it was going to be my next attempt. Thankfully, the Dyson has the MAC address for the device printed on the inside of the device. However, Google Nest unfortunately does not do this and you have to already be connected in to the app to view the system info. However, you could do a workaround for that by taking your device someplace else and using their wifi (as long as it is 2.4 WPA2 IPV6) to connect and setup the device in the app in order to find the MAC address for the device in the settings in the Nest app. Then you can take the device back home to your network, reset, and try to manually add the MAC address now that you found it (hopefully you took a screenshot or something :) ) Thankfully I didn't have to do this either, but it also would have been my next attempt.

Also, make sure you keep your password settings that you changed in your xfinity app to WPA3 Transition Mode. It'll stay that way for both 2.4G and 5G. This is important because the devices still need to be able to communicate and can only use WPA2. Also if in the future you have this problem again with another product, like perhaps an older Smart TV, you will already have the WPA2 functionality enabled.

I hope this was helpful! It's 3am but I'm so glad I eventually figured it out on my own!

INTRODUCTION
welke commando's kunnen worden ingetikt?
Switch>? __________________________________________________________________________________________________________________________________
Exec Commands:
Connect-Open a terminal Connection
Disable-Turn off privileged commands
Disconnect-Disconnect an existing network Connection.
Enable-Turn on privileged Commands
Exit-Exit From the EXEC
logout-Exit From the EXEC
Ping-Send echo messages
Resume-Resume an active network Connection
Show-Show running System information
SSH-Open a Secure Shell Client Connection
Telnet-Open a telnet Connection
Terminal-Set terminal line parameters
Traceroute-Trace route to destination ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
Naar Priviledged mode (soort administrator)
Switch> enable
Switch# __________________________________________________________________________________________________________________________________
Vraag alle instellingen op:
Switch> enable
Switch# show running-config __________________________________________________________________________________________________________________________________
Bewaar alle instellingen:
Switch# copy running-config startup-config ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
BASIC CONFIGURATION COMMANDS
Plaats een Wachtwoord Voor de console:
Switch> enable
Switch# configure terminal
Switch(config)# line console 0
Switch(config-line)# password hoek
Switch(config-line)# login __________________________________________________________________________________________________________________________________
plaats een wachtwoord Voor priviledge mode:
Switch> enable
Switch# configure terminal
Switch(config)# enable Password Geheim __________________________________________________________________________________________________________________________________
Plaats een banner:
Switch> enable
Switch# configure terminal
Switch(config)# banner motd@ [naam]@ __________________________________________________________________________________________________________________________________
Verander de hostname:
Switch> enable
Switch# configure terminal
Switch(config)# hostname kamer-215
Kamer-215(config)# __________________________________________________________________________________________________________________________________
ip address toekennen aan een interface:
router> enable
router# configure terminal
router(config)# interface gigabitEthernet 0/0/0
router(config-if)# ip address 192.168.0.1 255.255.255.0 __________________________________________________________________________________________________________________________________
Poort activeren:
router> enable
router# configure terminal
router(config)# interface gigabitEthernet 0/0/0
router(config-if)# no shutdown __________________________________________________________________________________________________________________________________
Domain name:
Switch> enable
Switch# configure terminal
Switch(config)# username admin password CCNA
Switch(config)# ip domain name cisco.com
Switch(config)# crypto key generate RSA
How many bits in the module [512]:1024 __________________________________________________________________________________________________________________________________
SSH Configureren:
Switch> enable
Switch# configure terminal
Switch(config)# line vty 0 15
Switch(config-line)# login local
Switch(config-line)# transport input ssh ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
VLAN CONFIGURATION COMMAND:
VLAN Configuratie:
Switch> enable
Switch# configure terminal
Switch(config)# vlan 10
Switch(config-vlan)# name vlan10
Switch(config-vlan)# exit __________________________________________________________________________________________________________________________________
Ip-adressen toewijzen aan VLAN'S en gateway Configuratie instellen:
Switch> enable
Switch# configure terminal
Switch(config) # interface vlan 10
Switch(config-if)# ip addres 192.168.10.1 255.255.255.0
Switch(config-if)# interface range fa0/1-5
Switch(config-if-range)# switchport mode access
Switch(config-if-range)# switchport access vlan 10
Switch(config-if-range)# exit __________________________________________________________________________________________________________________________________
Trunk-poorten definieren:
Switch> enable
Switch# configure terminal
Switch(config)# interface range fa0/1-5
Switch(config-if-range)# switchport mode trunk
Switch(config-if-range)# exit __________________________________________________________________________________________________________________________________
Routering tussen VLAN'S configureren met IEEE802.1Q Encapsulation:
Router> enable
Router# configure terminal
Router(config)# interface gigabitEthernet 0/1.20
Router(config-subif)# encapsulation dot1Q20
Router(config-subif)# ip address 192.168.20.1 255.255.255.0 ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
IP ROUTING AND ROUTE CONFIGURATION COMMAND:
Ip routing Configureren:
Router> enable
Router# configure terminal
Router(config)# interface gigabitEthernet 0/1
Router(config-if)# no Shutdown
Router(config-if)# exit
Router(config)# interface vlan 40
Router (config-if)#ip default-gateway 192.168.0.1 __________________________________________________________________________________________________________________________________
Ip route Configureren:
MIS> enable
MIS# configure terminal
MIS(Config)# interface gigabitEthernet 0/1
MLS(config-if)# no switchport
MLS(config-if)# ip route 0.0.0.0 0.0.0.0 gigabitEthernet 0/1
MLS(config-if)# exit ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
DHCP AND IP HELPER CONFIGURATION COMMAND:
DHCP Configuratie:
MIS> enable
MIS# configure terminal
MLS(config)# interface gigabitEthernet 1/0/24
MLS(config-if)# no switchport
MLS(config-if)# ip add dhcp __________________________________________________________________________________________________________________________________
DHCP Pool:
Router>enable
Router# configure terminal
Router(config)# Ip dhcp excluced-address 10.1.0.1 10.2.0.3
Router(config)# Ip dhcp pool net03
Router(dhcp-config)# network 10.2.0.0 255.255.255.0
Router(dhcp-config)# default-router 10.2.0.1
Router(dhcp-config)# dns-server 8.8.8.8 __________________________________________________________________________________________________________________________________
Ip helper addressen:
Switch> enable
Switch# configure terminal
Switch(config)# interface gigabitEthernet 0/0/1
Switch(config-if)# ip helper-address 10.1.0.1 ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
OSPF CONFIGURATION COMMAND:
OSPF:
Router> enable
Router# Configure terminal
Router(config)# router ospf 10
Router(config-router)# router-id 4.4.4.4
Router (config-router)# network 192.168.30.0 0.0.0.255 area 0
Router(config-router)# default-information origanate
Router(config-router)# passive-interface S0/3/1 ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
ACL AND NAT CONFIGURATION COMMAND:
COMING SOON ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
CDP AND LLDP CONFIGURATION COMMAND:
COMING SOON ____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
welke wildcard hoort bij welk Subnetmask:
32 Subnetmask (255.255.255.255):0.0.0.0
/31 Subnetmask (255.255.255.254):0.0.0.1
/30 Subnetmask (255.255.255.252):0.0.0.3
/29 Subnetmask (255.255.255.248):0.0.0.7
/28 Subnetmask (255.255.255.240):0.0.0.15
/27 Subnetmask (255.255.255.224):0.0.0.31
/26 Subnetmask (255.255.255.192):0.0.0.63
/25 Subnetmask (255.255.255.128):0.0.0.127
/24 Subnet mask (255.255.255.0):0.0.0.255
/23 Subnetmask.(255.255.254.0):0.0.1.255
/22 Subnetmask (255.255.252.0):0.0.3.255
/21 Subnetmask (255.255.248.0):0.0.7.255
/20 Subnetmask (255.255.240.0):0.0.15.255
/19 Subnetmask (255.255.224.0);0.0.31.255
/18 Subnetmask (255.255.192.0):0.0.63.255
/17 Subnetmask (255.255.128.0):0.0.127.255
/16 Subnetmask (255.255.0.0):0.0.255.255
/15 Subnetmask (255.254.0.0);0.1.255.255
/14 Subnetmask (255.252.0.0):0.3.255.255
/13 Subnetmask (255.248.0.0):0.7.255.255
/12 Subnetmask (255.240.0.0):0.15.255.255

Today, a senior member of our company had their email compromised. Another technician is currently handling it, but we're both stumped. We've changed passwords and revoked sessions, but since 9:00 AM, none of his emails have been coming through. A mail trace shows they're being delivered, specifically to the folder: DefaultFolderType:RssSubscription. Searches on this issue show others have faced it, but no one seems to know the cause. This problem affects both local and web-based Outlook, indicating it's likely a server-side issue. We've checked his RSS feed settings—no subscriptions there, as expected. It seems the attackers may have redirected his emails to hide password resets and 2FA notifications, preventing him from noticing unauthorized activities. Unfortunately, they've accessed his bank account, though he became aware of this after the bank contacted him. We now urgently need to restore his email delivery. There are no new sorting rules in Exchange Admin. We plan to inspect his local mail sorting rules once we have direct access to his machine. However, given recent updates to Office 365 that allow sorting rules to sync across devices via the cloud, I suspect the issue might be there. As an Exchange admin, I should be able to view and modify these cloud-based sorting rules per user, but I haven’t found a way to do so yet. Any insights on how to address this or information about how such hacks generally occur would be extremely helpful. I’m not familiar with this specific type of attack, as I typically use Thunderbird and Proton Mail and ensure my passwords are secure. Has anyone experienced something similar?

Hi all, I'm trying to automate an emailing system for OTP verification but am running into some trouble. Below is my code, in it's respective files.
In models.py:

from django.db import models from django.contrib.auth.models import AbstractUser, User from django.db.models.signals import post_save from django.dispatch import receiver # Create your models here. class UserProfile(models.Model): user = models.OneToOneField(User, on_delete=models.CASCADE) otp = models.CharField(max_length=6, blank=True) otp_expiry_time = models.DateTimeField(blank=True, null=True) class AdditionalData(models.Model): user_profile = models.OneToOneField(UserProfile, on_delete=models.CASCADE) firstname = models.CharField(max_length=100, blank=True) lastname = models.CharField(max_length=100, blank=True) dateofbirth = models.DateField(null=True, blank=True) phone_no = models.CharField(max_length=20, blank=True) country_origin = models.CharField(max_length=100, blank=True) city_origin = models.CharField(max_length=100, blank=True) u/receiver(post_save, sender=User) def create_user_profile(sender, instance, created, **kwargs): if created: UserProfile.objects.create(user=instance) @receiver(post_save, sender=User) def save_user_profile(sender, instance, **kwargs): instance.userprofile.save() 

In views.py:

from django.shortcuts import render, redirect, HttpResponse from django.contrib.auth.models import User from django.contrib.auth import authenticate, login from django.contrib.auth.decorators import login_required from datetime import timedelta from django.utils import timezone from django.core.mail import send_mail from rest_framework import status from rest_framework.decorators import api_view, permission_classes from rest_framework.permissions import AllowAny from rest_framework.response import Response from .serializers import UserProfileSerializer from .models import UserProfile, AdditionalData from rest_framework_simplejwt.tokens import RefreshToken from .generate_random_digits import generate_random_digits def sign_up(request): if request.method == 'POST': username = request.POST.get('username') email = request.POST.get('email') pass1 = request.POST.get('password1') pass2 = request.POST.get('password2') User.objects.create_user(username, email, pass1).save() return redirect('login') return render(request, 'main/signup.html') def login1(request): if request.method == "POST": username = request.POST.get('username') pass1 = request.POST.get('pass') user = authenticate(request, username=username, password=pass1) if user is not None: if user.last_login is None: user.last_login = timezone.now() user.save() login(request, user) return redirect('firstlogin') else: user_profile = UserProfile.objects.get(user=user) verification_code = generate_random_digits() user_profile.otp = verification_code user_profile.otp_expiry_time = timezone.now() + timedelta(minutes=15) user_profile.save() send_mail( 'Verification Code', f'Your verification code is: {verification_code}', 'from@gmail.com', [request.user.email], fail_silently=False, ) return redirect('otp') else: error_message = "Invalid username or password" return render(request, 'main/login.html', {'error_message': error_message}) return render(request, 'main/login.html') def verify(request): username = request.data.get('username') password = request.data.get('password') otp = request.data.get('otp') user = authenticate(request, username=username, password=password) if user is not None: user_profile = UserProfile.objects.get(user=user) if ( user_profile.verification_code == otp and user_profile.otp_expiry_time is not None and user_profile.otp_expiry_time > timezone.now() ): login(request, user) refresh = RefreshToken.for_user(user) access_token = str(refresh.access_token) user_profile.otp = '' user_profile.otp_expiry_time = None user_profile.save() return Response({'access_token': access_token, 'refresh_token': str(refresh)}, status=status.HTTP_200_OK) return Response({'detail': 'Invalid verification code or credentials.'}, status=status.HTTP_401_UNAUTHORIZED) @login_required def firstlogin(request): if request.method == "POST": user = request.user try: additional_data = AdditionalData.objects.get(user_profile__user=user) except AdditionalData.DoesNotExist: additional_data = AdditionalData.objects.create(user_profile=UserProfile.objects.get(user=user)) additional_data.firstname = request.POST.get('FirstName') additional_data.lastname = request.POST.get('LastName') date_str = f"{request.POST.get('dob-year')}-{request.POST.get('dob-month')}-{request.POST.get('dob-day')}" try: additional_data.dateofbirth = date_str except ValueError: return HttpResponse('Invalid date format') additional_data.phone_no = request.POST.get('PhoneNumber') additional_data.country_origin = request.POST.get('Country') additional_data.city_origin = request.POST.get('City') additional_data.save() return HttpResponse('WORKED') return render(request, 'main/firstlogin.html') @login_required def home(response): return render(response, 'main/landing_page.html') def otp(response): return render(response, 'main/otp.html') 

In settings.py:

""" Django settings for mysite project. Generated by 'django-admin startproject' using Django 4.2.6. For more information on this file, see https://docs.djangoproject.com/en/4.2/topics/settings/ For the full list of settings and their values, see https://docs.djangoproject.com/en/4.2/ref/settings/ """ from pathlib import Path import os # Build paths inside the project like this: BASE_DIR / 'subdir'. BASE_DIR = Path(__file__).resolve().parent.parent # Quick-start development settings - unsuitable for production # See https://docs.djangoproject.com/en/4.2/howto/deployment/checklist/ # SECURITY WARNING: keep the secret key used in production secret! SECRET_KEY = '#####...' # SECURITY WARNING: don't run with debug turned on in production! DEBUG = True ALLOWED_HOSTS = [] # Application definition INSTALLED_APPS = [ 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.messages', 'django.contrib.staticfiles', 'main.apps.MainConfig', ] MIDDLEWARE = [ 'django.middleware.security.SecurityMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', ] ROOT_URLCONF = 'mysite.urls' TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [os.path.join(BASE_DIR, 'templates')], 'APP_DIRS': True, 'OPTIONS': { 'context_processors': [ 'django.template.context_processors.debug', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', ], }, }, ] EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' EMAIL_HOST = 'smtp.gmail.com' EMAIL_PORT = 587 EMAIL_USE_TLS = True EMAIL_HOST_USER = 'from@gmail.com' EMAIL_HOST_PASSWORD = '############' WSGI_APPLICATION = 'mysite.wsgi.application' # Database # https://docs.djangoproject.com/en/4.2/ref/settings/#databases DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': BASE_DIR / 'db.sqlite3', } } # Password validation # https://docs.djangoproject.com/en/4.2/ref/settings/#auth-password-validators AUTH_PASSWORD_VALIDATORS = [ { 'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator', }, { 'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator', }, { 'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator', }, { 'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator', }, ] # Internationalization # https://docs.djangoproject.com/en/4.2/topics/i18n/ LANGUAGE_CODE = 'en-us' TIME_ZONE = 'UTC' USE_I18N = True USE_TZ = True # Static files (CSS, JavaScript, Images) # https://docs.djangoproject.com/en/4.2/howto/static-files/ STATIC_URL = 'static/' # Default primary key field type # https://docs.djangoproject.com/en/4.2/ref/settings/#default-auto-field DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField' 

otp.html:

TLDR:
The problems are as follows:

• 4 verification codes were sent b2b2b2b on the first try
• No longer receiving any emails
• The otp.html redirect after entering the code doesn't work

Hi guys, after losing brain cells trying to find information on how to install the Guppy screen, I wanted to show y'all how to do it on your own if you choose to. I may be wrong on some parts, but these are the things that worked for me. Thanks to wolfie_the_king_574 for telling me some of the steps on how to do it, but some of it didn't work for me. I also used Wiki for Creality Helper Script (guilouz.github.io) and ballaswag/guppyflo: GuppyFLO is a self-hosted service that enables local/remote management of multiple Klipper printers using Moonraker (github.com) and ballaswag/guppyscreen: A native Touch UI for 3D Printers running KlippeMoonraker. (github.com) on the steps for some of it and will be summarizing most of it. I will also be adding in the common downloads needed here for easy access as I was jumping all around to find it. [I'm not sure if you have to keep rebooting your printer during this process, but I'll take the safe way and do it anyways]
[Edit: I'm not sure why upon posting, that the numbers are all 1. but I can't change it so bare with me]

1. [1] Reset your entire Nebula Pad

• Download and unzip this file: Creality_K1_Reset_Utility.zip
• Open the file Creality_K1_Reset_Utility.html in your Internet browser.
• Make sure your printer is on, and put in your IP address and click reset.
• Reboot to make sure it has reset.
• Turn off your printer now.

1. [2] Reinstall the firmware for the Nebula Pad

• Download this Ender 3 V3 SE Firmware.
• Add the Ender3V3SE_firmware.bin file into your SD card and plug it into the printer.
• Choose the Ender 3 V3 SE logo on the next page. Put in your settings and update to the latest version.
• Turn off your printer.

1. [3] Now you want to root your Nebula Pad

• Click on this Destinal Root and download the first link in the description.
• There should be a white usb that came with the Nebula Pad. Plug that into your computer and format it in FAT32 with 4096 allocation size.
• Now copy the file into the usb and insert it into the side of the Nebula Pad.
• Turn on the printer and there should be a popup to upgrade.
• After it finishes upgrading, take the usb out or else it will keep having that popup.
• You can reboot if you want, I don't think you have to right now.

1. [4] Install PuTTY and go into Helperscript

• Click on this PuTTY Download and download the right one for you and install it.
• Next, when you open up PuTTY, enter the IP address for your printer and press enter. The IP address can be found where your wifi settings are on the Nebula Pad.
• It's going to say login as: and type in root
• Now it'll ask for the password which is creality
• Next, type in ./installer.sh to enter Helperscript

1. [5] Uninstall Moonraker, Fluid, Mainsail, and the Creality OS

• Type in 2 to get into the remove screen.
• Go one by one and type in 1 2 3 to remove each one respectively
• Type in b to go back to the main screen
• Type in 4 to enter the Customize screen and type in 3 to remove Creality OS
• Reboot

1. [6] Update Helperscript

• ssh back into the Nebula Pad using PuTTY
• Type in git config --global http.sslVerify false to avoid encountering an issue, I'm not sure what.
• Type in git clone --depth 1 https://github.com/Guilouz/Creality-Helper-Script.git /usdata/helper-script to install the script in the usdate folder.
• Type in sh /usdata/helper-script/helper.sh to run the script.
• There's two different way to now update the Helper Script
  • Go through the PuTTY, go through the user and password and enter ./installer.sh again and it should pop up with the update OR
  • When you access Fluidd or Mainsail, update it directly there.
  • You can access Fluidd by http://xxx.xxx.xxx.xxx:4408/ (replacing xxx.xxx.xxx.xxx by your local IP address).
    • Go in the Settings tab and go into Software Updates and click Update for Creality-Helper-Script.
  • You can access Mainsail by http://xxx.xxx.xxx.xxx:4409/(replacing xxx.xxx.xxx.xxx by your local IP address).
    • Go in the Machine tab and it should be there as well.
• Reboot

1. [7] Reinstall Moonraker, Fluid and/or Mainsail

• Go back into PuTTY, go back in the ./installer.sh, type in 1 to the installation screen and follow along for the installation of those. I don't think I have to baby steps that now.
• Reboot

1. [8] Update Everything

• Depending on if you use Fluidd or Mainsail, go back into those websites and update everything in the update section if it's not already updated.

1. [9] Install Anything Else + Guppy [FINALLY]

• Go back through PuTTY and into the Helper Script. Now you can also install anything you wanted to during. If you're unsure of what these mean, click on this Installer Definitions and look to the left side under "Install Menu" and look through whatever you want to.
• Some of these you won't have since this is meant for a different printer.
• You have to exit out of the Helper Script now by typing in q
• Now type in, to install GuppyFLO wget -O - https://raw.githubusercontent.com/ballaswag/guppyflo/main/installer.sh sh
• Now type in, to install the Guppy Screen and it should change your Nebula Pad to horizontal format and have you calibrate it touching cursors.sh -c "$(wget --no-check-certificate -qO - https://raw.githubusercontent.com/ballaswag/guppyscreen/main/installer.sh)"

1. [10] How to Connect to it on the Internet (I copied this straight this)

• Create a Tailscale account: Create Tailscale Account
• Install Tailscale application depending device(s) you want to use for remote access: Download Tailscale App
• Search up http://xxx.xxx.xxx.xxx:9873 (by replacing xxx.xxx.xxx.xxx by your printer's local IP address) to access the GuppyFLO Web interface
• Then, click on authenticate link to register GuppyFLO instance to Tailscale
• You will be redirected to the Tailscale website to connect device by clicking on Connect button
• Go to to your Tailscale Admin console here: Tailscale Admin Console
• There you will see the connected devices and their respective IP addresses:
  • guppyflo → Your printer
  • IP address assigned to your printer
  • The devices you have connected to Tailscale (here my mobile phone)
  • The IP addresses assigned to the devices you have connected
• Go to Tailscale DNS settings tab and enable MagicDNS feature
• Go back to GuppyFLO Web interface and click on Add Printer button
• Configure settings and click on Save button
• You can now connect to GuppyFlo Web interface remotely with http://guppyflo URL

Now this should be everything! Be sure to visit this Website or Demo Video or Website to understand how the screen works, how to connect to it with pictures, and whatnot.
Let me know if I did anything wrong, but these are the steps that worked for me.

Hi guys, so today we received a bunch of emails from "support@ecoconcern.com" saying "an informational alert has been triggered" and warned of an email redirect. Email asks you to put in your creds and you get hacked.
That clearly being a phishing attempt, I blocked the domain and moved on. Now at about 4:30 one of my users has their inbox flooded with over 1000 spam emails from gibberish domains. Exchange is detecting some of it, but notifications are still coming through.
I logged that user out, reset their password, and had them create a new password. I have since also followed the guide here: https://techcommunity.microsoft.com/t5/microsoft-defender-for-office/responding-to-targeted-mail-attacks-with-microsoft-365-defendeba-p/3819185
I'm also blocking domains at a tenant level that appear to keep showing up.
I also ran message traces to confirm that our org is not sending out any malicious emails and confirmed that to be true. We do not appear to have a breach and I suspect a client of ours was compromised and got ahold of some of our email addresses and are trying to spoof our addresses to compromise others.
I'm just a solo tech running an 8 person team, this isn't my full time position nor am I exactly certified to be a real M365 admin.
Looking for any tips.

I currently have a WHfB policy as a Device assignment and it works great.
We use our secondary Admin accounts when required for troubleshooting issues, and their passwords rotate every 12 hours. Unfortunately these accounts get prompted to setup Windows Hello upon login.
Is there a way to keep the WHfB device assignment but exclude the administrative users? I tried to exclude their AAD group, but it didn't exclude them.
The device assignment is nice because post-autopilot it forces the new user to setup WHfB immediately instead of waiting for the policy posy logon.