Wifi on MAC really slow until I reboot

I have a Mac with Mojave 10.14.5.

I have a problem with the home Wi-Fi. I have a 400 Mbps connection. When I start the laptop, the Wi-Fi is fine, but eventually it drops to less than 100 Mbps, and this somehow affects all other devices (phone, TV) that are connected to the Wi-Fi network.

But shortly after I restarted the Mac, the speed returns to 400, both on the Mac and on the other devices.

Proxy – Linux Squid Server denies connection, but works after reboot

I have several Squid servers on Ubuntu. At random, everyone seems to decline connections after about 24 hours. When I restart the computer, it will work again. In my squid.conf file, I have denied cache all thinking, if it was allowed, that may be where the problem is, but it has not solved it.

What happens that would cause this? And how do I fix this?

My configuration file looks like this.

http_port 3128
Cache deny everything
hierarchy_stoplist cgi-bin?

access_log no
cache_store_log no
cache_log / dev / null

refresh_pattern ^ ftp: 1440 20% 10080
refresh_pattern ^ gopher: 1440 0% 1440
refresh_pattern -i (/ cgi-bin / | ?) 0 0% 0
refresh_pattern. 0 20% 4320

acl localhost src 127.0.0.1/32 :: 1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 :: 1

acl SSL_ports port 1-65535
acl Safe_ports port 1-65535
acl CONNECT method CONNECT
acl siteblacklist dstdomain "/etc/squid/blacklist.acl"
http_access allows manager localhost
http_access Deny Manager

http_access deny! Safe_ports

http_access denied CONNECT! SSL_ports
http_access deny siteblacklist
auth_param basic program / usr / lib / squid3 / basic_ncsa_auth / etc / squid / passwd

auth_param basic children 5
auth_param basic realm Squid proxy caching web server
auth_param basic credentialsttl 2 hours
#acl password proxy_auth REQUIRED
http_access allows localhost
#http_access password allow

acl client src WHITE_LISTED_IP_ADDR
Allow http_access client

Allow all http_access
#http_access Deny all

forwarded_for off
request_header_access Allow all
request_header_access Allow all authorization
request_header_access Allow WWW authentication all
request_header_access Allow all proxy authorization
request_header_access all allow proxy authentication
request_header_access Cache-Control allows all
request_header_access Content-Encoding allows all
request_header_access Content-Length all allow
request_header_access Content-Type all allow
request_header_access date allow everything
request_header_access Expires and allows all
request_header_access host all allow
request_header_access If-changed-Allow all
request_header_access Last modified Allow all
request_header_access Place all
request_header_access pragma all
request_header_access Accept Allow All
request_header_access Accept-Charset allow everything
request_header_access Accept-Encoding allows all
request_header_access Accept-Language all allow
request_header_access Content-Language all allow
request_header_access Mime version allow everything
request_header_access Retry-After Allow All
request_header_access title all
request_header_access Allow all connections
request_header_access proxy connection all allow
request_header_access user-agent all allow
request_header_access cookie all allow
request_header_access All deny all

server – Issue hosting HTML page and Apache2 refusing to reboot

While trying to restart Apache to test my website, this error has occurred and I do not know how to fix it.

    systemctl status apache2.service
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preference: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: active (running) (result: exit code) since Tue 2019-06-18 18:10:36 PDT; 43min ago
Docs: man: systemd-sysv-generator (8)
Process: 13037 ExecStop = / etc / init.d / apache2 stop (code = stopped, status = 0 / SUCCESS)
Process: 13821 ExecReload = / etc / init.d / apache2 reload (code = stopped, status = 1 / FAILURE)
Process: 13139 ExecStart = / etc / init.d / apache2 start (code = stopped, status = 0 / SUCCESS)
Group: /system.slice/apache2.service
~ 13154 / usr / sbin / apache2 -k start
~ 13157 / usr / sbin / apache2 -k start
~ 13158 / usr / sbin / apache2 -k start
~ 13159 / usr / sbin / apache2 -k start
├─13160 / usr / sbin / apache2 -k start
└─13161 / usr / sbin / apache2 -k start

June 18 18:53:54 John-John Apache2[13821]: * Reload Apache httpd web server apache2
June 18 18:53:54 John-John Apache2[13821]: *
June 18 18:53:54 John-John Apache2[13821]: * The Apache2 configtest failed. Do nothing
June 18 18:53:54 John-John Apache2[13821]The output of the configuration test was:
June 18 18:53:54 John-John Apache2[13821]: AH00526: Syntax error on line 3 of / etc / apache2 / sit
June 18 18:53:54 John-John Apache2[13821]: ServerAlias ​​only used in 
June 18 18:53:54 John-John Apache2[13821]: Action & # 39; configtest & # 39; failed.
June 18 18:53:54 John-John Apache2[13821]: The Apache error log may contain more information.
June 18 18:53:54 John-John Systemd[1]: apache2.service: Control process finished, code = stopped st

`` `` `` `` ``

Linux – Centos7 iptables still exist after the reboot

I researched and found a lot of consistent information about it.

It still does not work.

I have set up a few iptables rules.
I save it with: sudo service iptables store

I check / etc / sysconfig / iptables and the rules are stored there.

I then restart the system and when it comes back, the new rules are not there.

Look at / etc / sysconfig / iptablesThey are still there.

I will continue then Restart sudo systemctl iptables and the rules show up again.

Each time you restart, the restart command must be run again.

Any hints?

Many Thanks!

Data Recovery – Is there a way to restore my system on reboot?

I want to create a recovery mechanism for my Ubuntu, which means the system always reverts back to its original state on reboot, no matter how I change it while I'm working. For example, I created and removed some files, but after the reboot, the created files should be removed and the removed files should be back.

Is there such a tool?

boot – My Samsung Galaxy S8 has crashed and the reboot will not go through

My Samsung Galaxy S8 has suffered no water or impact damage. It just stopped working. I tried to go through the forced reboot / reboot, ie, holding down the power button and the volume down key. I also tried restarting the recovery mode – hold down power, volume up and Bixby buttons. None of it worked. The phone vibrates occasionally. It also displays the Samsung Galaxy S8 startup screen, but it does not progress. At one point some "code" information was displayed, but not anymore. I managed to take a picture of it, which I attached. There are some photos on the phone that are not secured and that are very important.

The code / error message is:

# Error opening the recovery cause (no such file or directory) #


#Reboot recovery is cause [UNKNOWN]#
Supports SINGLE-SKU


File-based OTA

E: Error mounting / efs: No such file or directory
Supported API: 3
E: Error mounting / efs (no such file or directory)
E: unknown volume for path[/odm]
E: unknown volume for path [/vendor]
dm-verity verification failed ...
E: Mount / Cache Error: No such file or directory
E: Mount / Cache Error: No such file or directory
E: Failed to mount / system: No such file or directory
E: Mount / Cache Error: No such file or directory
E: Mount / Cache Error: No such file or directory
E: Mount / Cache Error: No such file or directory
E: mount / cache / recovery / last_locale not possible

Any help HUGELY appreciated. Many thanks.

ios – Macbook Update MacOS to reboot

Recently, I upgraded my Macbook to SSD and reinstalled the MacOS system. Previously, however, the Macbook Pro 2013 ran with MacOS Mojave. It's finished and I've been trying to switch the Mac to High Sierra right now for Time Machine (Mojave) to run. It is however since 4 days with "Restarting …" with the App Store logo fixed.

Does anyone know what is wrong? Many Thanks!

Authentication – Does the user allow a reboot if his key identification is changed?

The main feature of my app:

  • Two users select themselves via the telephone number
  • Neither of them knows the other at the beginning
  • Based on certain activities over time, an event occurs for both

Due to the answer of Hans-Martin Mosner I give more details.

When the user selects another user, he writes data in an entry with a specific ID to a server. If the other user does not select the first user to read this ID now, he can not read that data. For some time, even if this is the case, nothing more will happen.

It is true that after the first reading, I would theoretically be able to set a new ID for communication, but due to some internal data that would already have the entry with the ID, and restrictions that the server seems to have I would be Unable to do it with a check on the server, though I could do it in the client, but this would be open to malicious users who have at least a little knowledge in dealing with hackers to easily cheat with the server app ,

It is highly undesirable that the server must be changed at this point of development. This would have a very negative impact on the expected behavior of the app as it would need to be changed. So if it's not such a big problem, the problem with the phone number is I have to stick with it, maybe it's also possible that the restriction I mention does not exist, but after a good investigation, I could not prove it I would like to know how impractical it is to expect that one can not continue working with a changed phone number and take that information into account.

problem

If one of the users changes their phone number during the process, in my current solution both users must start over, choose again, and start the whole process from scratch.

The only solution to this problem that I can think of would make my app far more susceptible to manipulation by malicious users.

assumptions

I think changing a phone number is not that common (I have not changed mine in my whole life, and I only know a few people who have changed them in general). Although this may be annoying for some users, it may be the percentage of sufferers. One is low enough not to worry much.

question

I would like to know with trusted data how big that would be a problem.