New answers tagged

1

When your interfaces file has something like address 192.0.2.1/24, that specifies the address and the "netmask" (in the form of the /n network prefix length) all in one go. Previously, the interfaces file would have had separate address 192.0.2.1 and netmask 255.255.255.0 entries in that same situation. It's simply a modernization to consistently ...


1

In simple terms, 10.0.2.1/32 means that you set 10.0.2.1 on your network interface but you are alone, the whole network is just your IP. On the other hand, setting 10.0.2.1/24 means that your IP is 10.0.2.1 and the IP range 10.0.2.0-10.0.2.255 is a known, familiar, reachable block of IPs; no gateway (that is, another network device) needed to reach it. One ...


0

Thanks to the help of Wesley, I figured it out. That VPS was configured to use SystemdNetworkd so files in /etc/systemd/network instead of /etc/network/interfaces. Also, thanks to Michael, I learned that interface aliases are a thing of the past. See How to configure interface aliases using Systemd-Networkd?.


0

The file debian/control lists all the packages that should be installed as build-dependencies. If (for whatever reason) you have installed some of the required software without the apt system, then just remove respective lines from the debian/control file, so dpkg-buildpackage will not know about these packages and not check on them. Another trick is to ...


1

As Michael pointed out, you don’t. Instead, you add additional Address= and Gateway= lines to the interface. Example: $ cat /etc/systemd/network/eth0.network [Match] Name=eth0 [Network] Address=2a0a:3840:1337:126::b9c1:7ecb:1337/64 Gateway=2a0a:3840:1337:126::1 IPv6AcceptRA=no Address=185.193.126.203/24 Gateway=185.193.126.1 DNS=95.215.19.53 [DHCP] ...


0

When a domain doesn't match a virtual host, one of two locations will be used. First possibility is the base config, i.e. what you specify in the default config outside any virtual host. So check the DocumentRoot in the base config (try grep DocumentRoot /etc/apache2/* if you don't know where to look). Second, if you want an "all vhost" config, ...


0

Figured it out! cat << "EOF" >> /etc/systemd/network/10-strongswan0.netdev [NetDev] Name=strongswan0 Kind=dummy EOF cat << "EOF" >> /etc/systemd/network/20-strongswan0.network [Match] Name=strongswan0 [Network] Address=10.0.2.1/24 EOF


2

You probably can't configure eth0 as it's a container, not a real VM, and the host controls the network. In a real VM you could create a dummy interface and use that. Since you have a container, this depends on whether the container host has loaded the dummy module (and the chance is pretty close to 100% that they have not). iface dummy0 inet static ...


0

Your host is probably using NetPlan and CloudInit. /etc/network/interfaces is old and deprecated, so... don't use it. Check for the existence of /etc/netplan/config.yaml Have a plan for netplan


1

Your "virtual machine" is actually a container, not a virtual machine, and it appears your container host is configuring networking for you.


1

It's a typo. ipv6 should be in lowercase. net.ipv6.conf.all.autoconf=0 net.ipv6.conf.all.accept_ra=0


0

Try with --detail High (or Med). It looks like the http script outputs almost nothing (connection attempts using mod_proxy, detected possible exploits, users successfully logged), when --detail is not set (default to 0) or < 4. You can see it on SourceForge. Samples: my $detail = $ENV{'LOGWATCH_DETAIL_LEVEL'} || 0; # ... if (($detail >4) and $...


0

Many providers (typically consumer ISP’s but also some hosting providers) and most corporate networks have an anti-spam/email policy that is enforced by blocking outgoing mail in their firewall policies. Typically they will block outgoing traffic on the default smtp port, tcp 25, but other common ports for sending mail such as tcp 587 can be blocked too. ...


0

Pass the apt option on the command line which you run to install the package: apt-get install -o Dpkg::Options=--force-confold <package>


0

i found how to correct my problem. My problem was on Dovecot & Postfix configuration. My first problem was on SASL, postfix was unable to connect to SASL folder. To resolve my problem, i installed rsyslog and restart postfix to show logs and i follow each problem to resolve mine. Thanks for who helped me !


2

Using pgrep: pgrep nrpe > /dev/null || /etc/init.d/nagios-nrpe-server start > /dev/null or using a subshell: (pgrep nrpe || /etc/init.d/nagios-nrpe-server start) > /dev/null From the pgrep(1) manpage: pgrep looks through the currently running processes and lists the process IDs which match the selection criteria to stdout. If the process name is ...


3

You need to switch your grep statements. Your second statement to filter out grep will always succeed, because it is always there. So, first filter out grep and then check for the process: ps auxw | grep -v grep | grep nrpe > /dev/null || /etc/init.d/nagios-nrpe-server start According to the Debian package list the binary of the nagios-nrpe-server is ...


1

For some ridiculous reasons the client's upsmon requires the password for readonly operation. Fake passwords don't work (while e.g. nut-monitor will accept it). This could be troubling if passwords are not used / not visible to the user, especially for appliances. Some users will set up the configuration, start the service (often no error reported) and keep ...


1

To get interface-related info, you need IF-MIB. Specifically, poll IF-MIB::ifPhysAddress OID to get MAC addresses, for example: snmpwalk -v 2c -c public localhost IF-MIB::ifPhysAddress That should return one or a bunch of lines, depending on how many interfaces are present on the box. They may look something like this: IF-MIB::ifPhysAddress.1 = STRING: 01:...


2

Do you want your PHP code to be able to access a MySQL (or MariaDB) database? If yes, then you need this package. It provides the necessary PHP functions.


0

In my opinion you're overthinking this a bit since docker comes with some sane default configuration which it also manages automatically. E.g. in the default setup containers are not accessible via external network but they can connect to the internet themselves. Therefore you should just EXPOSE the relevant ports of your containers on the host's external IP ...


0

From https://linux.die.net/man/5/ipsec.conf : leftprotoport allowed protocols and ports over connection, also called Port Selectors. The argument is in the form protocol, which can be a number or a name that will be looked up in /etc/protocols, such as leftprotoport=icmp, or in the form of protocol/port, such as tcp/smtp. Ports can be defined as a number (...


0

The last output is actually telling you something is using the port so the slapd service is probably in limbo. Kill the slapd process manually, you can use suggestions in this answer or just plain pgrep slapd will give you pid of the process which you gonna kill. Command lsof +L1 or lsof -c slapd may show you slapd is touching some file (means it's in limbo)...


0

I removed openvpn and openvpn-as packages, reload apache2 and problem solved.


1

As the error says, you should specify the socket. The mandatory configuration parameter can be found on opendkim.conf documentation: Socket (string) Specifies the socket that should be established by the filter to receive connections from sendmail(8) in order to provide service. socketspec is in one of two forms:  local:path, which creates a UNIX domain ...


0

Once you logged into maintenance mode, You should open vim /etc/fstab and uncomment # all the lines except UUID line. then run below commands $systemctl daemon-reload $systemctl default


1

Use source nat instead, because wrong source ip goes into tunnel while masquarade: tun_ip=$(ip a | grep tunsnx | grep inet | awk '{print $2;}') iptables -t nat -A POSTROUTING -o tunsnx -s y.y.y.y/24 -j SNAT --to $tun_ip


0

Thanks to the diagnosis in the e2fsprogs bug report GCE team was able to fix this issue in GCE Debian 10 image and now Debian 10 VM creation with large boot disks as fast as was with Debian 9. This fix included starting from the debian-10-buster-v20200714 GCE Debian 10 image.


0

From your question, I assume that these iptables-rules are supposed to be installed on the docker-host. You a missing a central point here: the firewall-rules are only valid for the host itself, not the containers! Let's assume, your docker0 interface has the ip range 172.16.0.0/16. The host interface address is 172.16.0.1, and your first container might ...


0

I think I found a working solution, but I'm not sure if there is a better way. With the things I tried I had to also declare the established connections for the DOCKER-USER set adding this two lines in comparison with my question: iptables -A DOCKER-USER -i docker0 -j ACCEPT > iptables -A DOCKER-USER -o docker0 -j ACCEPT > iptables -A DOCKER-USER -m ...


0

I wouldn't worry too much about it. I'm seeing virtually no malicious traffic on IPv6 that would trigger fail2ban anyway, over a variety of public hosts. All the banactions will eventually get IPv6 support, but if you know any Python you can consider helping by adding the missing support yourself and submitting patches. That said, the most performant ...


2

Googling PHP 7.2 on Debian 10 gives several tutorials, but it's not recommended to just follow the first one you can find i.e. Don't blindly follow bad advice. Currently it's DEB.SURY.ORG that is providing fresh PHP packages for Debian, with multiple different PHP versions. The README.txt has a script for adding the repository to Debian. Managing Multiple ...


1

You can decrease the verbosity of wpa_supplicant by using -q or even -qq. See: https://linux.die.net/man/8/wpa_supplicant


0

You're not starting cron anywhere in dockerfile. Also containers don't use init.d and systemd, they aren't virtual machines and they don't have own systemd/init.d. That's why you see following error: [FAIL] cron is not running ... failed! My solution is to write simple bash script (or just change whole CMD) which starts crond and other things you want to ...


1

At least for Debian 10 this should work: # update-alternatives --set iptables /usr/sbin/iptables-legacy # update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy # update-alternatives --set arptables /usr/sbin/arptables-legacy # update-alternatives --set ebtables /usr/sbin/ebtables-legacy See also: https://wiki.debian.org/nftables


1

Install the binary properly in /usr/bin, as it should have been installed, and try again. The systemd unit does a lot of confining of the service, and one thing that is denied is access to user home directories. It's not expected that it will need to access a user home directory when running as a system service.


2

Cron jobs can only start when the cron daemon is running, and of course systemd starts the cron daemon like every other service. If it is important to run a specific job before or after something else, consider using a systemd timer/service to schedule it.


0

Well, short answer is to just change port on which embedded nginx is listening and forward via apache all connections


0

I eventually found a solution to this.... It seems that I may have put a public key file in the wrong format into the instance data. I was able to use the gcloud shell to remove the file (ssh-keys remove), upload a properly formatted file to the gcloud shell, and then do ssh-keys add --file-name=<my_key_file> to install it. Then it worked on RHEL. ...


Top 50 recent answers are included