similar to: ADMINISABSENTMINDED=No misbehaviour according to the manual

On Wed, 24 Apr 2019 at 06:01, likun <kun.li at ucarinc.com> wrote: > Hi?guys. > > There is a wierd problem with iptables recently, hopes somebody can help > me. > > I have installed Centos 7.2.1511 on a bare metal Dell server these days, > disabled firewalld and enabled iptables.services, and setup a group of very > simple rules, as the following: > > I believe

Hi?guys. There is a wierd problem with iptables recently, hopes somebody can help me. I have installed Centos 7.2.1511 on a bare metal Dell server these days, disabled firewalld and enabled iptables.services, and setup a group of very simple rules, as the following: # iptables-save # Generated by iptables-save v1.4.21 on Tue Apr 23 09:15:14 2019 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT

Hello, Stephen, thank you for input. Yes, these servers have the same firewall rules, and both of them have the same problem from time to time, most of time they are good. Actually, these servers are newly installed to be used as the Glusterfs storage server, so not much data flowing at this time. >From the sysctl output, I suppose it can't be a conntrack table overflow :

I'm running a Linksys WRT54GL router from my CentOS-7 home server. Every now and then (maybe once every 2 days) the router's WiFi cuts out, and I've found no way to solve this except to disconnect the power from the router, wait 10 seconds and then re-connect. This always works. The router is running under dd-wrt. My question is - which makes it a tiny bit CentOS-related - does anyone

On 05/11/2016 03:05 AM, Timothy Murphy wrote: > does anyone with such a router know of a way > to wake the router up in such a case through the computer? Enable ssh? ssh root at dd-wrt reboot

Hello, >From the doc, it says: "isOpen returns a logical value, whether the connection is currently open." But actually it seems to die on closed connections: > con <- file() > isOpen(con) [1] TRUE > close(con) > isOpen(con) Error in isOpen(con) : invalid connection Is it expected ? Tested on R-3.0.2 and R version 3.1.0 Patched (2014-06-11 r65921) on linux x86_64

Folks, I am finding problems with using "dse": > library(dse1) Loading required package: tframe Error: c("package '%s' required by '%s' could not be found", "setRNG", "dse1") > library(dse2) Loading required package: setRNG Error: package 'setRNG' could not be loaded In addition: Warning message: there is no package called

Hi, I just found out something strange. Try it out for yourselves. Here goes. Search for any directories under /boot: # find /boot/ -type d /boot/ /boot/grub /boot/lost+found So far so good. Now execute a detailed listing on the results: # find /boot/ -type d -exec ls -l \{} \; total 6203 -rw-r--r-- 1 root root 68663 sep 3 2009 config-2.6.18-164.el5 drwxr-xr-x 2 root root 1024 avr 6

My Linux workstation (Mandrake 10.1 kernel 2.6.8.1) is dual-homed to two ADSL Internet providers. Card eth0 (192.168.9.250) is the default route and leads to an SMC router (192.168.9.254). Card eth1 (192.168.1.250) leads to a Linksys router (192.168.1.1). I''m not doing any NAT or PPPoE in the workstation - the SMC and Linksys handle it all. I know four commands that let you set an IP

After doing some system work, including upgrading the Samba server to 3.0.28a from 3.0.24, upgrading the kernel to 2.6.24, and changing the firewall rulesk, the XP workstations which belong to that domain, the right click "run as ..." option is slow to bring up a dialog. The phenotype is this: right click some program (for instance, a shortcut to the "command prompt")

Hi Guys, I have tried every single rule I could into iptables but I can't register this VPS to a provider Spikko. Finally I did an iptable accept on INPUT, OUTPUT, and FORWARD, for ports 0:65000 just to test things and still I can't register to the provider. I can easily register to another provider which uses port 5060 and I can make calls. But sip show registry only show Request Sent

I'm running a Linksys WRT54GL router from my CentOS-7 home server. Every now and then (maybe once every 2 days) the router's WiFi cuts out, and I've found no way to solve this except to disconnect the power from the router, wait 10 seconds and then re-connect. This always works. The router is running under dd-wrt. My question is - which makes it a tiny bit CentOS-related - does anyone

Hi everyone, For some reason MixMonitor doesn't record when it should; It actually shows the MixMonitor line just fine on the CLI. How can MixMonitor be debugged for things like privilege issues or filename issues? **I had this working at one point and then stopped working. Not sure what I changed. System Info: Asterisk 1.4.21.2 Queuemetrics 1.6.3.0 [queuedial] ; this piece of dialplan is

Greetings *`s, I am manually creating call files and dropping them into /var/spool/asterisk/outgoing to be picked up by *. Presently, when I use local/internal parameters using SIP it works..ie I make an internal call from device to device. However, when I try dial an outside number which I have set up in a custom conf file, it bombs out with the following message :

I don't know whether this is specific to (my installation of) SUSE 10.1, or is more general. With R 2.6.0, I am finding that some widgets made through the tcltk package are having problems which become evident through scrollbar activity. An example is demo(tkfaq) -- see below. To reproduce the problem, I do the following: after the tk window appears, hold down the

hi, while stopping shorewall 4.5.21.2 on a debian7 box with the ADMINISABSENTMINDED set to no in shorewall.conf, the connections on vlan tagged interfaces that were active before the shorewall stop command was executed are not terminated as it is for the firewall and other interfaces! when the firewall is stopped as expected new connections on vlan tagged interface are refused but even

I''m using W2K2 32bit on a 3.2.1 Lenny-amd64 host. While the pv disk driver works as expected, I encounter problems with the network driver. I tried several installation scenarios, all with the same result. My test looks like this: I install gplpv, but without letting the networking driver install. After reboot I RTL8139 ist still active and working, and gplpv devices manage the disks.

http://shorewall.net/pub/shorewall/Snapshots ftp://shorewall.net/pub/shorewall/Snapshots Problems Corrected since version 1.4.6: 1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was being tested before it was set. 2) Corrected handling of MAC addresses in the SOURCE column of the tcrules file. Previously, these addresses resulted in an invalid iptables command. 3)

Hi, I have a default class for my un-marked traffic (prio 5) and a prio 0 class for the important stuff, but I do not understand why my download traffic is duplicated in both. It work fine for my upload traffic (same setting except the red class but I have the same result if I create an esfq instead). Any comments/information will be appreciated. Below my config : tc commands from my scirpt :

http://shorewall.net/pub/shorewall/Snapshots ftp://shorewall.net/pub/shorewall/Snapshots Problems Corrected since version 1.4.6: 1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was being tested before it was set. 2) Corrected handling of MAC addresses in the SOURCE column of the tcrules file. Previously, these addresses resulted in an invalid iptables command.