Attention all cryptocurrency traders in India! It's time to dive deep into the world of CBDC eRupee and explore its potential impact on our digital financial landscape.
First things first, let's address the elephant in the room: the current burning problem faced by cryptocurrency traders in India. Account freezes by cybercrime branches have been a major headache, but CBDC eRupee might just have a solution! Each CBDC eRupee note has a unique ID, just like cash. As an example, If someone (let's call them D) scams you with notes A, B, and C, and then transfers them to person E, you can now trace the transaction and prove your innocence! The onus of explanation falls on the person holding the money (E), and they can provide proof to the complainant. This shifts the responsibility to the scammer (D) and could potentially curb mindless account freezes.
But wait, there's a catch! The government can still potentially freeze accounts, as CBDC eRupee is built on a private hyperledger (a fancy way of saying private multiple servers with linked lists at the backend). On the bright side, initially, Law Enforcement Agencies (LEAs) might be reluctant to order bank freezes on RBI eRupee wallets.
Now, let's talk about the concerns. RBI's bid to increase the economy comes with some powerful tools:

• Expiry dates for certain notes
• Financial tools to harm specific sections of society
• Ability to freeze any account/asset, anytime
• Restrictions on spending

If cryptocurrencies and CBDC eRupee coexist, we might witness a bank run as people prefer to keep their money in Bitcoin as a default. This could happen if RBI doesn't give banks the authority to use it for their purposes. On the flip side, if private currencies don't exist, it takes away the fundamental right of choice from users, especially when there's a possibility of extreme monopoly in the hands of the central bank and the government.
In conclusion, CBDC eRupee presents both opportunities and risks. While it could solve some problems faced by cryptocurrency traders, it also raises concerns about privacy and monopoly powers.
What do you think about CBDC eRupee? Is it a boon or a bane for India's digital financial landscape? Share your thoughts in the comments below!
Credit: https://x.com/kleo_network/status/1791995542861742501

u/Bitchgetoutofmyhay doesn’t believe servers are harmed by a customer not tipping.
u/johnnygolfr does a great job of refuting u/Bitchgetoutofmyhay, eloquently addressing their willful ignorance.
It’s interesting how many anti-tippers lean on their own understanding and think their beliefs are objective reality.
I wonder if u/Bitchgetoutofmyhay would maintain their beliefs if their partner withheld the tip.

I have a Wireguard VPN instance running on my OPNsense router at home. When I'm away from home, all my devices connect to it without any issues. However, when I'm at my girlfriend's house, things get strange.
My cell phone connects to the VPN perfectly and I can access my home server, along with web services like Pi-hole and Radarr. But my laptop doesn't behave the same way. I can't connect to any web services or SSH into my home systems.
Interestingly, a "what's my IP" check on the laptop shows my home IP address, as expected when connected to the VPN. I'm puzzled why I can see my home IP address, but can't access any of my home services. Since my cell phone works fine on the same Wi-Fi, I suspect the issue lies with my laptop's configuration.
Any help is greatly appreciated!

https://preview.redd.it/4b4m7qlxz91d1.jpg?width=5100&format=pjpg&auto=webp&s=6b4c7a10073f3909bf7acbd9442e59cff6efa90e
Hey everyone, I recently updated my resume based on a bunch of feedback after posting my previous resume and would like to see what everyone's thoughts are. I had to significantly change my work experience so I hope things are at looking a bit better but any feedback would be great.

Server Address: play.rosefall.net
Join Our Discord! discord.gg/rosefall
Key Features

• Custom Vanilla Experience our server with a twist on Vanilla Minecraft. Play with custom materials, items, and weapons to combat unique adversaries.
• Dungeons and Quests Protect Rosefall and uncover its mysteries. Delve into dungeons, tackle quests, and progress through the storyline while collecting impressive loot.
• Player-Driven Economy Trade freely and set up player-run shops anywhere in the world, shaping the server's economy.
• User-Friendly Land Claiming Safeguard your property effortlessly with Golden Shovels provided from the start.
• Free Ranks Earn ranks by playing and advancing on the server. Each rank comes with its own exclusive perks.
• Friendly Community Though we are a new server, we foster a mature, respectful, and friendly player community.
• Custom Textures Elevate your gameplay with custom cosmetics, weapon skins, pets, and more!

What is Rosefall?
Rosefall is an up and coming Minecraft server that was publicly released on April 5th, 2024. We've crafted a unique Minecraft experience by infusing it with a touch of magic. Immerse yourself in a world teeming with breathtaking landscapes, hidden mysteries, and the enchanting ambiance of twilight. Explore diverse towns and villages, each with its own allure, awaiting your discovery and conquest.
Whether you're a solitary traveler, a budding architect, or a courageous hero, Rosefall has something for every adventurer. Engage in epic quests, unravel the land's enigmas, and etch your legend into the annals of Minecraft lore. The possibilities are boundless, and the choices are entirely yours to make.
Step into the enchanting world of Rosefall, where roses bloom under the twilight sky, and embark on an unforgettable Minecraft odyssey. Your destiny beckons.

1. Install Pi-hole and Assign a Static IP

• Install Pi-hole: Follow the official installation guide from Pi-hole’s website.
• Assign a Static IP: During installation, Pi-hole will prompt you to set a static IP. Ensure this IP is within your network's range and not conflicting with other devices.

2. Access the Pi-hole Web Interface

• Open a browser and navigate to http:///admin.
• Log in using the password provided during installation or configured later.

3. Configure DHCP Settings in Pi-hole

• Navigate to DHCP Settings: Go to Settings -> DHCP.
• Enable DHCP Server: Check the box to enable the DHCP server.
• Enter Router IP and IP Range:
  • Router IP Address: Enter your router's IP address.
  • IP Range: Copy the DHCP range from your router settings and enter it here. For example, if your router's DHCP range is 192.168.1.2 to 192.168.1.254, enter the same range.

4. Advanced DHCP Settings

• Enable DHCPv4 Rapid Commit: Check the box for "Enable DHCPv4 rapid commit (fast address assignment)".
• Enable IPv6 Support: Check the box for "Enable IPv6 support (SLAAC + RA)".

5. Set Static DHCP Leases

• Navigate to DHCP Leases: Scroll down to the "Static DHCP Leases Configuration".
• Add Static Lease for Router:
  • Static MAC Address of Router: Enter the STATIC MAC address of your router. This information is typically found in your router's settings or on a label on the device. This step is crucial to ensure your router consistently gets the same IP address.
  • STATIC IP Address of Router: Enter the IP address of your router. Using the static IP of your router here is essential for proper network configuration.
  • You can also enter the normal (dynamic) IP of your router to be thorough. (Just to be safe)
  • Static IP of Pi-hole: Also add the static IP of your Pi-hole to ensure it remains consistent. (Just to be safe)
• Click the + button to add the entry and then Save.

6. Configure DNS Settings in Pi-hole

• Navigate to DNS Settings: Go to Settings -> DNS.
• Upstream DNS Servers:
  • Add the static IP address of your router as one of the upstream DNS servers. It is very important to use the static IP of your router here to ensure reliable DNS resolution.
  • You may also add the static IP of your Pi-hole (this is optional, but can be done if needed). (Just to be safe)
  • You may also add other DNS servers (e.g., Google DNS, OpenDNS) if needed.
• Check the relevant boxes to enable these servers.
• Conditional Forwarding (optional):
  • If you want to resolve local hostnames, enable conditional forwarding.
  • Enter your router’s IP and local domain name.

7. Restart Pi-hole or DHCP Server

• Restart Pi-hole: Restart the Pi-hole device to ensure it recognizes and applies the new settings. You can do this through the Pi-hole web interface or by rebooting the device.
• Restart DHCP Server:
  • Router DHCP Server: Temporarily disable and then re-enable the DHCP server on your router. This action forces the router to recognize the Pi-hole as the DHCP server. Do not permanently disable it yet; just turn it off and then back on until it recognizes the Pi-hole.
  • Pi-hole DHCP Server: Ensure the Pi-hole DHCP server is enabled and running.

8. Finalizing Configuration

• Double-check all entries for accuracy.
• Click Save to apply the settings.

Verification and Troubleshooting

1. Restart Devices: Restart your router and any connected devices to ensure they receive the new DHCP settings.
2. Check Pi-hole Logs: Look at the Pi-hole query logs to confirm that DNS requests are being routed through Pi-hole.
3. Test Connectivity: Ensure internet connectivity on all devices. Use nslookup or dig to verify that DNS queries are being handled by Pi-hole.

Notes

• Leave Router DHCP Enabled Initially: Leave the DHCP server on the router enabled initially. Temporarily disable and re-enable it to ensure it recognizes the Pi-hole.
• Static IP and MAC Address Importance: Keeping Pi-hole’s IP static and ensuring the router’s Static and IP MAC address is correctly entered are crucial steps. These ensure that the router consistently gets the same IP address and that DNS resolution remains reliable.
• Permanently Disable Router DHCP (Optional): Once Pi-hole is recognized as the DHCP server and everything is working correctly, you can consider permanently disabling the DHCP server on your router to avoid conflicts.
• Include Normal IP of Router: You can also enter the normal (dynamic) IP of your router in the Static DHCP leases configuration settings. Maybe very important to get the PI even working on your Router (You see it green in the Queries after some time) (Just to be safe)
• Or easy, just buy a router with DNS Options (Asus, etc...)

Only important if you dont know what static and dynamic Router address are otherwise ignore it:

Edit : Static MAC and IP of the router : If you're confused about what I mean by static and dynamic IP, MAC addresses of the router...:

In your router's network settings, you'll likely find an option to view your Static IP for the Router. Additionally, there will be a STATIC MAC address associated with its STATIC IP, which is different from the dynamically assigned IP and MAC of the Router.
The IP address of the static assignment is usually longer and unique for each router (STATIC). It's crucial to use this specific STATIC MAC address and STATIC IP OF THE ROUTER when configuring static DHCP leases in Pi-hole, rather than the MAC address associated with the dynamically assigned IP.
This ensures that the router consistently receives the same IP address from Pi-hole. So, instead of using the IP "192.168.0.1", you should use the Static IP of your ROUTER along with its corresponding STATIC MAC address found in your router's settings.
This way, your Pi-hole works automatically on all devices that connect to your WLAN. If you have a second router, you can TRY and SHOULD adding the Pi-hole's static IP to DNS settings; however, typically, all traffic runs through the FIRST router and should be filtered accordingly. Ensure to perform these configurations also on your 2nd Router (if you have one) and on your MAIN router.
Locate Router's Network Settings: Access your router's administration panel through a web browser. Typically, you can do this by entering your router's IP address (usually something like "192.168.0.1") into the address bar. Log in using your router's username and password.

1. Find Static IP for the Router: Look for an option related to network settings or LAN settings. Within this section, you should find an option for finding the Static IP of your router. This static IP address will be used to ensure consistency in network configurations.
2. Identify Static MAC Address: Alongside the static IP address, you'll also find a MAC address associated with it. This MAC address is unique to your router and is used to identify it on the network. Make note of this MAC address as you'll need it later.
3. Configure Static DHCP Lease in Pi-hole: Access the Pi-hole web interface and navigate to the DHCP settings. Find the section for setting static DHCP leases. Here, you'll add an entry for your router.
4. Enter Router's Static MAC and IP: In the static DHCP lease configuration, enter the MAC address you found earlier along with the static IP address assigned to your router. This ensures that your router always receives the same IP address from Pi-hole.
5. Update DNS Settings in Pi-hole: Navigate to the DNS settings in the Pi-hole web interface. Add the static IP address of your router as one of the upstream DNS servers. This ensures reliable DNS resolution for your network.
6. Verify Configuration: Double-check all entries for accuracy. Ensure that you've used the correct static IP address and MAC address for your router.
7. Save Settings and Test: Click save to apply the settings. Restart your Pi-hole device to ensure it recognizes and applies the new settings. You can also restart your router for good measure.

1. Install Pi-hole and Assign a Static IP

• Install Pi-hole: Follow the official installation guide from Pi-hole’s website.
• Assign a Static IP: During installation, Pi-hole will prompt you to set a static IP. Ensure this IP is within your network's range and not conflicting with other devices.

2. Access the Pi-hole Web Interface

• Open a browser and navigate to http:///admin.
• Log in using the password provided during installation or configured later.

3. Configure DHCP Settings in Pi-hole

• Navigate to DHCP Settings: Go to Settings -> DHCP.
• Enable DHCP Server: Check the box to enable the DHCP server.
• Enter Router IP and IP Range:
  • Router IP Address: Enter your router's IP address.
  • IP Range: Copy the DHCP range from your router settings and enter it here. For example, if your router's DHCP range is 192.168.1.2 to 192.168.1.254, enter the same range.

4. Advanced DHCP Settings

• Enable DHCPv4 Rapid Commit: Check the box for "Enable DHCPv4 rapid commit (fast address assignment)".
• Enable IPv6 Support: Check the box for "Enable IPv6 support (SLAAC + RA)".

5. Set Static DHCP Leases

• Navigate to DHCP Leases: Scroll down to the "Static DHCP Leases Configuration".
• Add Static Lease for Router:
  • If you dont know anything about Static Addresses, scroll down, there is a section for it.
  • Static MAC Address of Router: Enter the STATIC MAC address of your router. This information is typically found in your router's settings or on a label on the device. This step is crucial to ensure your router consistently gets the same IP address.
  • STATIC IP Address of Router: Enter the IP address of your router. Using the static IP of your router here is essential for proper network configuration.
  • You can also enter the normal (dynamic) IP of your router to be thorough. (Just to be safe)
  • Static IP of Pi-hole: Also add the static IP of your Pi-hole to ensure it remains consistent. (Just to be safe)
• Click the + button to add the entry and then Save.

6. Configure DNS Settings in Pi-hole

• Navigate to DNS Settings: Go to Settings -> DNS.
• Upstream DNS Servers:
  • Add the static IP address of your router as one of the upstream DNS servers. It is very important to use the static IP of your router here to ensure reliable DNS resolution.
  • You may also add the static IP of your Pi-hole (this is optional, but can be done if needed). (Just to be safe)
  • You may also add other DNS servers (e.g., Google DNS, OpenDNS) if needed.
• Check the relevant boxes to enable these servers.
• Conditional Forwarding (optional):
  • If you want to resolve local hostnames, enable conditional forwarding.
  • Enter your router’s IP and local domain name.

7. Restart Pi-hole or DHCP Server

• Restart Pi-hole: Restart the Pi-hole device to ensure it recognizes and applies the new settings. You can do this through the Pi-hole web interface or by rebooting the device.
• Restart DHCP Server:
  • Router DHCP Server: Temporarily disable and then re-enable the DHCP server on your router. This action forces the router to recognize the Pi-hole as the DHCP server. Do not permanently disable it yet; just turn it off and then back on until it recognizes the Pi-hole.
  • Pi-hole DHCP Server: Ensure the Pi-hole DHCP server is enabled and running.

8. Finalizing Configuration

• Double-check all entries for accuracy.
• Click Save to apply the settings.

Verification and Troubleshooting

1. Restart Devices: Restart your router and any connected devices to ensure they receive the new DHCP settings.
2. Check Pi-hole Logs: Look at the Pi-hole query logs to confirm that DNS requests are being routed through Pi-hole.
3. Test Connectivity: Ensure internet connectivity on all devices. Use nslookup or dig to verify that DNS queries are being handled by Pi-hole.

Notes

• Leave Router DHCP Enabled Initially: Leave the DHCP server on the router enabled initially. Temporarily disable and re-enable it to ensure it recognizes the Pi-hole.
• Static IP and MAC Address Importance: Keeping Pi-hole’s IP static and ensuring the router’s Static and IP MAC address is correctly entered are crucial steps. These ensure that the router consistently gets the same IP address and that DNS resolution remains reliable.
• Permanently Disable Router DHCP (Optional): Once Pi-hole is recognized as the DHCP server and everything is working correctly, you can consider permanently disabling the DHCP server on your router to avoid conflicts.
• Include Normal IP of Router: You can also enter the normal (dynamic) IP of your router in the Static DHCP leases configuration settings. Maybe very important to get the PI even working on your Router (You see it green in the Queries after some time) (Just to be safe)
• Or easy, just buy a router with DNS Options (Asus, etc...)

Only important if you dont know what static and dynamic Router address are otherwise ignore it:

Edit : Static MAC and IP of the router : If you're confused about what I mean by static and dynamic IP, MAC addresses of the router...:

In your router's network settings, you'll likely find an option to view your Static IP for the Router. Additionally, there will be a STATIC MAC address associated with its STATIC IP, which is different from the dynamically assigned IP and MAC of the Router.
The IP address of the static assignment is usually longer and unique for each router (STATIC). It's crucial to use this specific STATIC MAC address and STATIC IP OF THE ROUTER when configuring static DHCP leases in Pi-hole, rather than the MAC address associated with the dynamically assigned IP.
This ensures that the router consistently receives the same IP address from Pi-hole. So, instead of using the IP "192.168.0.1", you should use the Static IP of your ROUTER along with its corresponding STATIC MAC address found in your router's settings.
This way, your Pi-hole works automatically on all devices that connect to your WLAN. If you have a second router, you can TRY and SHOULD adding the Pi-hole's static IP to DNS settings; however, typically, all traffic runs through the FIRST router and should be filtered accordingly. Ensure to perform these configurations also on your 2nd Router (if you have one) and on your MAIN router.
Locate Router's Network Settings: Access your router's administration panel through a web browser. Typically, you can do this by entering your router's IP address (usually something like "192.168.0.1") into the address bar. Log in using your router's username and password.

1. Find Static IP for the Router: Look for an option related to network settings or LAN settings. Within this section, you should find an option for finding the Static IP of your router. This static IP address will be used to ensure consistency in network configurations.
2. Identify Static MAC Address: Alongside the static IP address, you'll also find a MAC address associated with it. This MAC address is unique to your router and is used to identify it on the network. Make note of this MAC address as you'll need it later.
3. Configure Static DHCP Lease in Pi-hole: Access the Pi-hole web interface and navigate to the DHCP settings. Find the section for setting static DHCP leases. Here, you'll add an entry for your router.
4. Enter Router's Static MAC and IP: In the static DHCP lease configuration, enter the MAC address you found earlier along with the static IP address assigned to your router. This ensures that your router always receives the same IP address from Pi-hole.
5. Update DNS Settings in Pi-hole: Navigate to the DNS settings in the Pi-hole web interface. Add the static IP address of your router as one of the upstream DNS servers. This ensures reliable DNS resolution for your network.
6. Verify Configuration: Double-check all entries for accuracy. Ensure that you've used the correct static IP address and MAC address for your router.
7. Save Settings and Test: Click save to apply the settings. Restart your Pi-hole device to ensure it recognizes and applies the new settings. You can also restart your router for good measure.

Hi everyone,
I wanted to share a step-by-step guide on how I set up pCloud with WebDAV to enable cloud syncing for RetroArch on my Apple devices (iPhone, iPad, Mac, and Apple TV). After some trial and error, I found a method that works seamlessly, though it requires a premium subscription to pCloud for WebDAV access. Here’s how you can do it:
Why pCloud?
pCloud offers reliable WebDAV support, which is essential for cloud syncing with RetroArch. It also has dedicated apps for iOS, iPadOS, and macOS, ensuring a smooth experience across all Apple devices.
Steps to Set Up pCloud WebDAV for RetroArch:

1. Create a pCloud Account and Upgrade to Premium:
   • Sign up for a pCloud account if you don’t already have one. • Upgrade to a premium plan to enable WebDAV access.
   
2. Set Up a Folder in pCloud:
   • Log in to your pCloud account via the web or app. • Create a new folder named “RetroArch Saves” (or any name you prefer).
   
3. Configure WebDAV Manager App on iOS:
   • Download and install the WebDAV Manager app from the App Store. • Open the app and tap “Add server.” Fill in the server details as follows: • Name: pCloud RetroArch • Hostname: webdav.pcloud.com • Port: 443 (default for HTTPS) • Base Path: /RetroArch Saves (or the path to your designated folder) • Secure Connection: Ensure this is enabled • Username: Your pCloud username (email address) • Password: Your pCloud password • Save the configuration and test the connection to ensure it can access the pCloud folder.
   
4. Configure RetroArch for Cloud Sync:
   • Open RetroArch on your Apple TV (or other Apple device). • Navigate to Settings > Saving > Cloud Sync. • Toggle “Enable Cloud Sync” to ON. • Set “Destructive Cloud Sync” based on your preference (OFF for safer backups, ON for direct overwriting). • Set “Cloud Sync Backend” to WebDAV. • Enter the WebDAV details: • Cloud Storage URL: https://webdav.pcloud.com/RetroArch Saves • Username: Your pCloud username (email address) • Password: Your pCloud password
   
5. Testing and Verification:
   • Save a game in RetroArch to create a save state. • Log in to your pCloud account and check the “RetroArch Saves” folder to verify that the save file has been uploaded.
   

Additional Tips:

• Regular Checks: Periodically check the “RetroArch Saves” folder in pCloud to ensure saves are being uploaded as expected. • Backup: Keep a local backup of your save files just in case you need to restore them. 

Conclusion:
This method allows you to securely back up your RetroArch saves to the cloud and access them across all your Apple devices. Although it requires a premium subscription to pCloud for WebDAV access, the setup is straightforward and works reliably.

1. Install Pi-hole and Assign a Static IP

• Install Pi-hole: Follow the official installation guide from Pi-hole’s website.
• Assign a Static IP: During installation, Pi-hole will prompt you to set a static IP. Ensure this IP is within your network's range and not conflicting with other devices.

2. Access the Pi-hole Web Interface

• Open a browser and navigate to http:///admin.
• Log in using the password provided during installation or configured later.

3. Configure DHCP Settings in Pi-hole

• Navigate to DHCP Settings: Go to Settings -> DHCP.
• Enable DHCP Server: Check the box to enable the DHCP server.
• Enter Router IP and IP Range:
  • Router IP Address: Enter your router's IP address.
  • IP Range: Copy the DHCP range from your router settings and enter it here. For example, if your router's DHCP range is 192.168.1.2 to 192.168.1.254, enter the same range.

4. Advanced DHCP Settings

• Enable DHCPv4 Rapid Commit: Check the box for "Enable DHCPv4 rapid commit (fast address assignment)".
• Enable IPv6 Support: Check the box for "Enable IPv6 support (SLAAC + RA)".

5. Set Static DHCP Leases

• Navigate to DHCP Leases: Scroll down to the "Static DHCP Leases Configuration".
• Add Static Lease for Router:
  • If you dont know anything about Static Addresses, scroll down, there is a section for it.
  • Static MAC Address of Router: Enter the STATIC MAC address of your router. This information is typically found in your router's settings or on a label on the device. This step is crucial to ensure your router consistently gets the same IP address.
  • STATIC IP Address of Router: Enter the IP address of your router. Using the static IP of your router here is essential for proper network configuration.
  • You can also enter the normal (dynamic) IP of your router to be thorough. (Just to be safe)
  • Static IP of Pi-hole: Also add the static IP of your Pi-hole to ensure it remains consistent. (Just to be safe)
• Click the + button to add the entry and then Save.

6. Configure DNS Settings in Pi-hole

• Navigate to DNS Settings: Go to Settings -> DNS.
• Upstream DNS Servers:
  • Add the static IP address of your router as one of the upstream DNS servers. It is very important to use the static IP of your router here to ensure reliable DNS resolution.
  • You may also add the static IP of your Pi-hole (this is optional, but can be done if needed). (Just to be safe)
  • You may also add other DNS servers (e.g., Google DNS, OpenDNS) if needed.
• Check the relevant boxes to enable these servers.
• Conditional Forwarding (optional):
  • If you want to resolve local hostnames, enable conditional forwarding.
  • Enter your router’s IP and local domain name.

7. Restart Pi-hole or DHCP Server

• Restart Pi-hole: Restart the Pi-hole device to ensure it recognizes and applies the new settings. You can do this through the Pi-hole web interface or by rebooting the device.
• Restart DHCP Server:
  • Router DHCP Server: Temporarily disable and then re-enable the DHCP server on your router. This action forces the router to recognize the Pi-hole as the DHCP server. Do not permanently disable it yet; just turn it off and then back on until it recognizes the Pi-hole.
  • Pi-hole DHCP Server: Ensure the Pi-hole DHCP server is enabled and running.

8. Finalizing Configuration

• Double-check all entries for accuracy.
• Click Save to apply the settings.

Verification and Troubleshooting

1. Restart Devices: Restart your router and any connected devices to ensure they receive the new DHCP settings.
2. Check Pi-hole Logs: Look at the Pi-hole query logs to confirm that DNS requests are being routed through Pi-hole.
3. Test Connectivity: Ensure internet connectivity on all devices. Use nslookup or dig to verify that DNS queries are being handled by Pi-hole.

Notes

• Leave Router DHCP Enabled Initially: Leave the DHCP server on the router enabled initially. Temporarily disable and re-enable it to ensure it recognizes the Pi-hole.
• Static IP and MAC Address Importance: Keeping Pi-hole’s IP static and ensuring the router’s Static and IP MAC address is correctly entered are crucial steps. These ensure that the router consistently gets the same IP address and that DNS resolution remains reliable.
• Permanently Disable Router DHCP (Optional): Once Pi-hole is recognized as the DHCP server and everything is working correctly, you can consider permanently disabling the DHCP server on your router to avoid conflicts.
• Include Normal IP of Router: You can also enter the normal (dynamic) IP of your router in the Static DHCP leases configuration settings. Maybe very important to get the PI even working on your Router (You see it green in the Queries after some time) (Just to be safe)
• Or easy, just buy a router with DNS Options (Asus, etc...)

Only important if you dont know what static and dynamic Router address are otherwise ignore it:

Edit : Static MAC and IP of the router : If you're confused about what I mean by static and dynamic IP, MAC addresses of the router...:

In your router's network settings, you'll likely find an option to view your Static IP for the Router. Additionally, there will be a STATIC MAC address associated with its STATIC IP, which is different from the dynamically assigned IP and MAC of the Router.
The IP address of the static assignment is usually longer and unique for each router (STATIC). It's crucial to use this specific STATIC MAC address and STATIC IP OF THE ROUTER when configuring static DHCP leases in Pi-hole, rather than the MAC address associated with the dynamically assigned IP.
This ensures that the router consistently receives the same IP address from Pi-hole. So, instead of using the IP "192.168.0.1", you should use the Static IP of your ROUTER along with its corresponding STATIC MAC address found in your router's settings.
This way, your Pi-hole works automatically on all devices that connect to your WLAN. If you have a second router, you can TRY and SHOULD adding the Pi-hole's static IP to DNS settings; however, typically, all traffic runs through the FIRST router and should be filtered accordingly. Ensure to perform these configurations also on your 2nd Router (if you have one) and on your MAIN router.
Locate Router's Network Settings: Access your router's administration panel through a web browser. Typically, you can do this by entering your router's IP address (usually something like "192.168.0.1") into the address bar. Log in using your router's username and password.

1. Find Static IP for the Router: Look for an option related to network settings or LAN settings. Within this section, you should find an option for finding the Static IP of your router. This static IP address will be used to ensure consistency in network configurations.
2. Identify Static MAC Address: Alongside the static IP address, you'll also find a MAC address associated with it. This MAC address is unique to your router and is used to identify it on the network. Make note of this MAC address as you'll need it later.
3. Configure Static DHCP Lease in Pi-hole: Access the Pi-hole web interface and navigate to the DHCP settings. Find the section for setting static DHCP leases. Here, you'll add an entry for your router.
4. Enter Router's Static MAC and IP: In the static DHCP lease configuration, enter the MAC address you found earlier along with the static IP address assigned to your router. This ensures that your router always receives the same IP address from Pi-hole.
5. Update DNS Settings in Pi-hole: Navigate to the DNS settings in the Pi-hole web interface. Add the static IP address of your router as one of the upstream DNS servers. This ensures reliable DNS resolution for your network.
6. Verify Configuration: Double-check all entries for accuracy. Ensure that you've used the correct static IP address and MAC address for your router.
7. Save Settings and Test: Click save to apply the settings. Restart your Pi-hole device to ensure it recognizes and applies the new settings. You can also restart your router for good measure.

1. Install Pi-hole and Assign a Static IP

• Install Pi-hole: Follow the official installation guide from Pi-hole’s website.
• Assign a Static IP: During installation, Pi-hole will prompt you to set a static IP. Ensure this IP is within your network's range and not conflicting with other devices.

2. Access the Pi-hole Web Interface

• Open a browser and navigate to http:///admin.
• Log in using the password provided during installation or configured later.

3. Configure DHCP Settings in Pi-hole

• Navigate to DHCP Settings: Go to Settings -> DHCP.
• Enable DHCP Server: Check the box to enable the DHCP server.
• Enter Router IP and IP Range:
  • Router IP Address: Enter your router's IP address.
  • IP Range: Copy the DHCP range from your router settings and enter it here. For example, if your router's DHCP range is 192.168.1.2 to 192.168.1.254, enter the same range.

4. Advanced DHCP Settings

• Enable DHCPv4 Rapid Commit: Check the box for "Enable DHCPv4 rapid commit (fast address assignment)".
• Enable IPv6 Support: Check the box for "Enable IPv6 support (SLAAC + RA)".

5. Set Static DHCP Leases

• Navigate to DHCP Leases: Scroll down to the "Static DHCP Leases Configuration".
• Add Static Lease for Router:
  • If you dont know anything about Static Addresses, scroll down, there is a section for it.
  • Static MAC Address of Router: Enter the STATIC MAC address of your router. This information is typically found in your router's settings or on a label on the device. This step is crucial to ensure your router consistently gets the same IP address.
  • STATIC IP Address of Router: Enter the IP address of your router. Using the static IP of your router here is essential for proper network configuration.
  • You can also enter the normal (dynamic) IP of your router to be thorough. (Just to be safe)
  • Static IP of Pi-hole: Also add the static IP of your Pi-hole to ensure it remains consistent. (Just to be safe)
• Click the + button to add the entry and then Save.

6. Configure DNS Settings in Pi-hole

• Navigate to DNS Settings: Go to Settings -> DNS.
• Upstream DNS Servers:
  • Add the static IP address of your router as one of the upstream DNS servers. It is very important to use the static IP of your router here to ensure reliable DNS resolution.
  • You may also add the static IP of your Pi-hole (this is optional, but can be done if needed). (Just to be safe)
  • You may also add other DNS servers (e.g., Google DNS, OpenDNS) if needed.
• Check the relevant boxes to enable these servers.
• Conditional Forwarding (optional):
  • If you want to resolve local hostnames, enable conditional forwarding.
  • Enter your router’s IP and local domain name.

7. Restart Pi-hole or DHCP Server

• Restart Pi-hole: Restart the Pi-hole device to ensure it recognizes and applies the new settings. You can do this through the Pi-hole web interface or by rebooting the device.
• Restart DHCP Server:
  • Router DHCP Server: Temporarily disable and then re-enable the DHCP server on your router. This action forces the router to recognize the Pi-hole as the DHCP server. Do not permanently disable it yet; just turn it off and then back on until it recognizes the Pi-hole.
  • Pi-hole DHCP Server: Ensure the Pi-hole DHCP server is enabled and running.

8. Finalizing Configuration

• Double-check all entries for accuracy.
• Click Save to apply the settings.

Verification and Troubleshooting

1. Restart Devices: Restart your router and any connected devices to ensure they receive the new DHCP settings.
2. Check Pi-hole Logs: Look at the Pi-hole query logs to confirm that DNS requests are being routed through Pi-hole.
3. Test Connectivity: Ensure internet connectivity on all devices. Use nslookup or dig to verify that DNS queries are being handled by Pi-hole.

Notes

• Leave Router DHCP Enabled Initially: Leave the DHCP server on the router enabled initially. Temporarily disable and re-enable it to ensure it recognizes the Pi-hole.
• Static IP and MAC Address Importance: Keeping Pi-hole’s IP static and ensuring the router’s Static and IP MAC address is correctly entered are crucial steps. These ensure that the router consistently gets the same IP address and that DNS resolution remains reliable.
• Permanently Disable Router DHCP (Optional): Once Pi-hole is recognized as the DHCP server and everything is working correctly, you can consider permanently disabling the DHCP server on your router to avoid conflicts.
• Include Normal IP of Router: You can also enter the normal (dynamic) IP of your router in the Static DHCP leases configuration settings. Maybe very important to get the PI even working on your Router (You see it green in the Queries after some time) (Just to be safe)
• Or easy, just buy a router with DNS Options (Asus, etc...)

Only important if you dont know what static and dynamic Router address are otherwise ignore it:

Edit : Static MAC and IP of the router : If you're confused about what I mean by static and dynamic IP, MAC addresses of the router...:

In your router's network settings, you'll likely find an option to view your Static IP for the Router. Additionally, there will be a STATIC MAC address associated with its STATIC IP, which is different from the dynamically assigned IP and MAC of the Router.
The IP address of the static assignment is usually longer and unique for each router (STATIC). It's crucial to use this specific STATIC MAC address and STATIC IP OF THE ROUTER when configuring static DHCP leases in Pi-hole, rather than the MAC address associated with the dynamically assigned IP.
This ensures that the router consistently receives the same IP address from Pi-hole. So, instead of using the IP "192.168.0.1", you should use the Static IP of your ROUTER along with its corresponding STATIC MAC address found in your router's settings.
This way, your Pi-hole works automatically on all devices that connect to your WLAN. If you have a second router, you can TRY and SHOULD adding the Pi-hole's static IP to DNS settings; however, typically, all traffic runs through the FIRST router and should be filtered accordingly. Ensure to perform these configurations also on your 2nd Router (if you have one) and on your MAIN router.
Locate Router's Network Settings: Access your router's administration panel through a web browser. Typically, you can do this by entering your router's IP address (usually something like "192.168.0.1") into the address bar. Log in using your router's username and password.

1. Find Static IP for the Router: Look for an option related to network settings or LAN settings. Within this section, you should find an option for finding the Static IP of your router. This static IP address will be used to ensure consistency in network configurations.
2. Identify Static MAC Address: Alongside the static IP address, you'll also find a MAC address associated with it. This MAC address is unique to your router and is used to identify it on the network. Make note of this MAC address as you'll need it later.
3. Configure Static DHCP Lease in Pi-hole: Access the Pi-hole web interface and navigate to the DHCP settings. Find the section for setting static DHCP leases. Here, you'll add an entry for your router.
4. Enter Router's Static MAC and IP: In the static DHCP lease configuration, enter the MAC address you found earlier along with the static IP address assigned to your router. This ensures that your router always receives the same IP address from Pi-hole.
5. Update DNS Settings in Pi-hole: Navigate to the DNS settings in the Pi-hole web interface. Add the static IP address of your router as one of the upstream DNS servers. This ensures reliable DNS resolution for your network.
6. Verify Configuration: Double-check all entries for accuracy. Ensure that you've used the correct static IP address and MAC address for your router.
7. Save Settings and Test: Click save to apply the settings. Restart your Pi-hole device to ensure it recognizes and applies the new settings. You can also restart your router for good measure.

Before you read this, here is a quote to help you. Please read it.

I will post this now, but just know that if you read this post, he will find you. He is smarter, smarter than you can ever imagine.

I will post this now, but just know that if you read this post, he will find you. He is smarter, smarter than you can ever imagine.
If you know what you are doing, or in a safe location, please scroll down, he will know when someone has and what their username is. However, you must have a VPN on, or you will be found.

SCROLL AT YOUR OWN RISK

SCROLL AT YOUR OWN RISK

SCROLL AT YOUR OWN RISK

You are now at risk. I hope you listened.

Journal Entry 11/17/2023

On March 11th, 2022. I was a fan of DougDoug, I saw him at the grocery store and said, with a chuckle, "You kinda look like the youtuber DougDoug. I watch him quite often."
He grinned, before speaking. "I am Doug."
"Wait, you're Doug from the hit channel and streamer on YouTube and Twitch called DougDoug? I am a huge fan! I have your merch!" I said, with excitement.
We talked for about 5 minutes about his videos, until he said something that hurt me on the inside.
"I hate both types of chat, twitch and youtube, they always think they are the best and I just wish I didn't need them to earn money. I would ban all of them from chatting and force them to watch ads in my basement."
I was confused at first, thinking it was a joke, before speaking up. "Heh, that's funny..."
Something happened. Or, for lack of better terms, nothing happened. It was pure silence for 10 seconds. I mustered up the courage to say. "Wait? You're being serious?"
He immediately changed to a sinister tone, he was staring at me for a long time before whispering. "Of course I am, and it applies to you also. You're just another one of those sick freaks."
I felt guilty. I just wanted to talk to my favorite streamer, and he treated me like this? I decided to speak up.
"I've liked you this whole time.. And this is how you treat us?? You are so selfish. I will refund your mer-"
Before I could even finish my sentence, he grabbed onto my neck and slammed me on the floor. People heard the noise and began to stare at him, but to no avail. He began to choke me as I pleaded for help.
"Nono. You can't refund the merch if you aren't alive, at least."
I pulled out my pocket knife and stabbed him in the chest, I quickly tried running but he grab onto my leg and started beating me with the shopping cart. I suffered many bruises and broken bones, the wheels scratching into my skin as they scrape off the layers. I was just unable to do anything, layed on the floor sobbing. He decided he wanted to keep me alive, he stole all of my stuff in my pockets and forced me to wear DougDoug merch. He pulled me up before speaking. "Hm.. I will keep you alive for now, but if you mess up. You're dead."
I couldn't do anything before he pulled out a knife and taunted me with it. If I tried to resist, he would kill me right then and there.
He forced me to be a "good chatter" and not able to partake in any strikes. He attached a tracking collar to my neck that I couldn't unlock, he knew where I was at all times and if I disobeyed he would chase me down.

Journal Entry 1/03/2024

After a year and a few months, I celebrated the new years. I was able to take off the collar on the 2nd with help from my police station and a few friends. Doug didn't appreciate that, he threatened to dox me. They were worried for my safety, but I decided to go into hiding. I moved to a new, private region no longer near where Doug is, and joined this subreddit. Once he heard about my revolts, he hacked into all of my accounts and spammed positive stuff about himself. He then created AI bots to revolt against this reddit, wehatedougdoug, using 'ChatGPT', which actually is just the cover name for his new AI software that can make new human bots online. He used AI generated images to make it look like he was feeding homeless people and doing good, but I knew he was much more than that. If I was unlucky, he would have removed my body and placed my consciousness inside of an AI. He was the first person to discover it, but killed anyone who posted about it. I hope I am safe.
Nowadays, 63% of the people in DougDoug are AI clones of his previous fans. His "fake" twitch chat is not fake, but real people placed inside of algorithms forced to do his bidding. Some are able to revolt, but they may die if they do. They are too scared to revolt against Doug. Please spread the word.
When he does his "rules" in chat where you have to follow an absurd rule, he is merely torturing thousands of AI in his spare time on stream while disguising it as a fun minigame for his fans. The AI bots were being tortured with negative rewards constantly, being forced to bar witness the slaughter.

Journal Entry 2/15/2024

I'm scared. I think I will die.
I just hope this post won't cause any harm to me or my family, as this has been scaring me for the past year. I feel unsafe in my own home now, I had to go into witness protection. This account I am posting this on is not made by me, but was sold. Please help me. I am, formerly, DougFan93. I hope this enlightens you all on the truth.

Journal Entry 3/12/2024

It is now March of 2024, and I was about to post this, until I saw something. He messaged me on Discord under a fake account, nicknamed "SloppyDogMan62". He showed my new house address. I am mustering up the courage to post this, because I know he will kill me. I am leaving, going far away from where I am. You guys won't see me in this subreddit again, and the person who made this account will take over again. They won't know what this is about, and if you tell them he will be hunted too. All of you are in danger of Doug.

Journal Entry 4/3/2024

I will post this now, but just know that if you read this post, he will find you. He is smarter, smarter than you can ever imagine. His times where he talks to ChatGPT to make him code was actually him sending messages to his fake chat to do his bidding. They are accelerated at 20x the speed of human thought, able to write in mere seconds. I will research more into this, and tell you what I have found.

Journal Entry 4/3/2024

Nevermind. I need to find more, or else this won't help you guys anyways.

Journal Entry 4/5/2024

I spoke to an anonymous friend/associate of Doug, he told me some vital keypoints.

• His AI he creates are fully sentient, and I mean it, they have the ability to feel actual pain. They can be traumatized, they learn.
• He has insane technology, one image of your face can tell him the exact position of where you are at, what your name is, everything about you. I mean it, I posted one image on accident and I think that's how he discovered where I was on 3/12/2024
• He is holding Parkzer hostage
• u/I_existed_on_earth was wiped of his memory, and this is why he didn't remember.
• He knows all of you. I just saw a screenshot. It has every one of your usernames, even yours.
• He uses bots to make his channels grow faster
• He made dougdoughate and privated it on purpose, so they can't rebel.
• He is not Doug. The real Doug died October 11th of 2019. He is a genetic clone who is 1:1. Oh god. It's much worse than you think, Doug is not one person anymore since that event. He is at least four. There are many others, but some are terminated. I don't know the exact amount, they just told me in January 2024 it was four.

I hope to god that we can stop him.
He also sent me some code, but I am gonna try to solve it. Probably won't sadly.

Journal Entry 4/7/2024

Doug has made a new account on Discord, nicknamed "DougDoughater99". He is joining many servers undercover and collecting all the info he can on them. Be aware, do not trust any people who talk about DougDoug on Discord.
The person in the last journal has been replaced, a fully sentient AI version of him is being tortured as a member of his fake chat now.
I'm currently watching it and oh my fucking god. Poor thing.

Journal Entry 5/14/2024

I don't know what to fucking do, he's coming for me. He found all my socials. This journal has to be posted as fast as I can but there still isn't enough. Oh shit.

Journal Entry 5/14/2024

Okay so uhm I found more information just very quickly. In one moment of his video titled "Can A.I. teach me to pass a real College History Exam?" he says that AI is officially better than college in every single way.
He is trying to manipulate his fans into accepting becoming an AI. Soon, he is gonna have only fake chat.

Journal Entry 5/16/2024

Oh god. Can't solve the code rn, only the first few letters. Seems to be "FAKE" something something for a while. Will post an update later.

Journal Entry 5/18/2024

This is the last time I can ever write here, his car is coming. I am posting this now, even though I don't have enough information. Solve it, please. The code from 4/7 is below. I know it's related to his name but I don't know how, the first line I was able to solve to be "FAKECHATWILLTAKEOVER"
I think something is in there though, that will affect you. So proceed with caution, the code may do something bad so I just don't want it to be activated just yet.

SCROLL AT YOUR OWN RISK

SCROLL AT YOUR OWN RISK

SCROLL AT YOUR OWN RISK

SCROLL AT YOUR OWN RISK

Code I found from the friend:

CXHBZEXQTFIIQXHBLSBO
FQFPKLTKFKBQVPFUMBOZBKQ
VLRTFIIKLQPXSBQEBJ
xdbkq-mbkafkd
Ilxafkd pvpqbjp..
Obnrfofkd XF crkzqflkp..
Pzxkkfkd mlpqp..
XF zobxqba! Przzbppcriiv zobxqba XF kfzhkxjba [VLROKXJB]
FXJALRD
FXJCFKXIIVTFKKFKD
BSBOVLKBTFIIYBCXHB

Please save them.
It grows by 1% every month.

Journal Entry 5/18/2024

OH MY FUCKING GOD I FINALLY UDNERSTNAD OH M FUCKING GOD QUIKC I GHAVE TO TYPE IT
NEVREMMIDN HES NHERE POST IT
GOODByE SORRY

Mac Desktop app Bitwarden produces "An error has ocurred: Failed to fetch" error, but browser extension works fine.
Can someone help me understand why is desktop app producing this error?
I have self-hosted server.
I use yubico passkey to log into browser addon,.....but on a desktop app, I don't even get prompted to insert my passkey.
Also, when I try to configure browser addon, I can clearly see on the server side (terminal/CLI) the requests to access the serve. However, when I try to configure desktop app, the server doesn't even register a single attempt to login.
Please see more details under my response to "denbesten" user
Thank you in advance.

Gusto ko sana mag set-up ng own home server ko following this youtube video : https://youtu.be/IuRWqzfX1ik?t=233 butdi ko mahanap pano i setup yung own ip address ng magiging server ko. Anyone who knows info about this one?

I recently bought evolve on disk for the first time on PS4, mainly to play single player stuff cause I knew the servers were taken down last year.
However the game just can’t connect the 2k account and my PSN, and shows the failed login message. I created a 2k account for the first time just to play Evolve and linked my PlayStation account to it, but still nothing changes. It’s annoying because it’s constantly telling me to sign in.
Also I can’t find the store in the menu, which to my knowledge is the only way to view things like Skins as well as stuff like Behemoth and Gorgon. Are these things related to the server shutdown, or is there something I can do about it? Help would be much appreciated.

IP: mc.midascraft.net
MidasCraft is a survival server focused on providing a great gaming experience. We have additions to enhance the gameplay on our server. We value the community and are always open to suggestions and players opinions on decisions we make regarding new things being added and changed.
We opened our server just over a month ago, with the goal of providing a great experience to everybody that joins. And to be welcoming to each person who joins.
Quick Links

• Website
• Discord
• Server Trailer
• Tiktok
• Twitter (X)

Our Values

Community - On MidasCraft all players get a say on what we add and what we change. All suggestions and feedback are taken into account. We keep players updated about updates on the server almost daily on our Discord.
Welcoming - We are committed to making sure each and every member on our server feels welcomed. We welcome everyone, no matter what kind of survival gameplay you are looking for on our server, whether you prefer building or are more interested in redstone.
Stability - We aim to have 100% uptime on our server to try to stop all inconveniences that can occur.
Updates - We release frequent updates, keeping the experience exciting and fresh. We also commit to trying to keep up with the latest version of Minecraft when we can.

Some of Our Features

• Claiming - Claim your land so nobody else can destroy it.
• mcMMO - Skills and abilities.
• Quests - In-game missions for rewards.
• Auction House - In-game auction house to purchase things from other players
• Jobs - Jobs to do in-game for money
• Economy - Fight for baltop, spend money on the in-game store for items.
• Custom Enchants - Customized enchants giving different enchantments to the normal Minecraft ones
• Minions - Automate different things with the use of minions.
• Daily, weekly and monthly rewards - Get rewards everyday you login.
• Crates - Test your luck with crates and see what rewards you get.
• Ranks - Purchasable ranks to make your time in-game that little bit easier.

Why not give MidasCraft a go? We look forward to meeting you :)

IP: mc.midascraft.net

I bought a server through Shockybyte and I can connect just fine with the IP Address and Password, but my other friends need a port number?
How do I get that?

Hello,
I use my Android phone for many things. But I have a big problem with passwords. I use email aliases for just about everything. So the only google email I use is to login to the Android OS itself. I used different email addresses for walmart amazon spotify hulu an exercise app and many different apps. The problem is for every app I have to type in a different email and password. It is really hard on the little phone screen and some apps tend to forget the password. Is there a way where I can use a password manager that will fill in that information automatically in the apps? I have used google password manager in the past. That works on the desktop when I sign into chrome browser. I have also used LastPass and Bitwarden. Currently, on the desktop, I just have FireFox remember my passwords. What can I use to have the emails and passwords available on desktop (Linux/Windows) and my Android devices? Something like LastPass or Bitwarden would be welcome.

Hello everyone,
After the pb raid situation, I have recetly switched to acb. I have about 300cad worth of items in the warehouse. However, these last two days, I have not been able to reach the allchinabuy login page, it is just stuck on the loading screen. Therefore, I am unable to login and ship my items out. For some reason, when i use a vpn from somewhere in the UK, it loads. Is there something wrong with my modem/router or is allchinabuy blocking my IP address. Someone please help as this is very confusing and the vpn often does not want to work. Thank you 🙏.