search for: ip_local_port_rang

Forwarding just in case anyone is familiar with this on CentOS, thanks! -- Hello, Just found that net.ipv4.ip_local_port_range has different behavior between RHEL releases: until v6 although you have multiple source IPs you can only use a fixed number of local ports, seems that "ip_local_port_range" is a global configuration or limitation. On RHEL-6 kernel (testing with 2.6.32-279) you can bind() to N local port...

Thanks, but my current settings are: net.ipv4.ip_local_reserved_ports = 30000-32767 net.ipv4.ip_local_port_range = 32768 60999 meaning the reserved ports are already in the short int range, so maybe I misunderstood something? or is it a different issue? From: Atin Mukherjee [mailto:amukherj at redhat.com] Sent: Thursday, June 15, 2017 10:56 AM To: Guy Cukierman <guyc at elminda.com> Cc: gluster-use...

+Gaurav, he is the author of the patch, can you please comment here? On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > Thanks, but my current settings are: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > net.ipv4.ip_local_port_range = 32768 60999 > > meaning the reserved ports are already in the short int range, so maybe I > misunderstood something? or is it a different issue? > > > > *From:* Atin Mukherjee [mailto:amukherj at redhat.com] > *Sent:* Thursday, June 15, 2017 10:56 AM > *To:* Guy Cuk...

Hello, First let me say how much I appreciate Shorewall. I just downloaded shorewall-1.3.14.tgz, built and installed it without error, and had it working with only minimal fiddling with the config files. I''m having trouble getting NFS to work with Shorewall. I followed the info on the "Ports required for Various Services/ Applications" page but I couldn''t get it to

https://review.gluster.org/#/c/17494/ will it and the next update of 3.10 should have this fix. If sysctl net.ipv4.ip_local_reserved_ports has any value > short int range then this would be a problem with the current version. Would you be able to reset the reserved ports temporarily to get this going? On Wed, Jun 14, 2017 at 8:32 PM, Guy Cukierman <guyc at elminda.com> wrote: >

...client to connect to an iperf server (running either CentOS or Debian) requesting N parallel TCP connections. I notice that the local ephemeral ports used are not consecutive and are always even ports numbers. This can change to "only odd ports numbers" depending on the setting net.ipv4.ip_local_port_range, but basically, the idea is the Centos kernel does "+2" when finding a local port for socket, not doing +1. Doing a netstat, generally speaking, only even (or odd) local ports are used so this does not seem application dependent. It's possible, however, to request both odd and even...

I've been seeing these errors intermittently for a while now. Here's an example from the logs: dovecot: Jul 12 15:59:05 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable The error is EAGAIN. Sometimes it will resolve itself after a few minutes and sometimes it needs to be restarted (it may fix itself, I usually get a phone call if it goes

Good day, I'd just like a bit of information about the source ports that hpa-tftp uses for its TFTP file transfers. We're using it to transfer files across a network that we have heavily firewalled. So, we'd like to know which ports the TFTP server might use as the source port for its data transfers and/or any ways to configure a range that it can use. I dug through the man page,

Ralf Baechle wrote: > I'd like to point those who you need to use these crude workarounds: > > echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc > echo 4096 32767 > /proc/sys/net/ipv4/ip_local_port_range > > at a new version of tftp-hpa which solves the PMTU problem by disabling it > only for the tftp client and introduces a new -R begin:end option which > allows to limit the port number range. The changes are about to become > available in the tftp-hpa git repository at > http...

...0 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_time = 1800 net.ipv4.tcp_low_latency = 1 net.ipv4.tcp_ecn = 0 net.ipv4.conf.all.accept_source_route = 0 net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.all.log_martians = 1 net.ipv4.ip_conntrack_max = 8192 net.ipv4.hashsize = 1023 net.ipv4.ip_local_port_range = "32768 61000" and after this, that linux put in their "/var/log/messages" next: Mar 1 14:08:16 morpheus kernel: host 192.168.212.17/if4 ignores redirects for 192.168.210.98 to 192.168.210.98. Mar 1 14:08:16 morpheus kernel: host 192.168.212.4/if4 ignores redirects for 192...

i all I use linux as GiGE router and have 6 NIC on it Those days the NIC interrupt takes around 100% CPU but the system is 4G memroy and 8 CPU. I can't see any error packet in this NIC interface too After I block the udp, the %CPU drops. but the UDP only takes around 8M in general We use UDP traffic for voice. Do you have any suggestion ? increase the kernel parameter? Thank you so much

...e maximum size of a message, in bytes kernel.msgmax = 65536 # Controls the maximum shared segment size, in bytes kernel.shmmax = 68719476736 # Controls the maximum number of shared memory segments, in pages kernel.shmall = 4294967296 ########### add by operation V1.0 begin ############ net.ipv4.ip_local_port_range = 32768 65000 net.core.rmem_max = 8388608 net.core.wmem_max = 8388608 net.ipv4.tcp_rmem = 4096 87380 8388608 net.ipv4.tcp_wmem = 4096 65536 8388608 net.ipv4.tcp_max_syn_backlog = 8192 net.ipv4.tcp_window_scaling = 0 net.ipv4.tcp_sack = 0 net.ipv4.tcp_timestamps = 0 kernel.panic = 5 vm.swappiness =...

...file => "/etc/sysctl.conf", line => "net.ipv4.tcp_keepalive_time = 300"; "sysctl-port-range": file => "/etc/sysctl.conf", line => "net.ipv4.ip_local_port_range = 1024 65000"; "sysctl-file-max": file => "/etc/sysctl.conf", line => "fs.file-max = 130000"; } rfile { "/etc/rc.d/init.d/FedoraDirectoryServer":...

...seems as if the system cannot create any more outgoing connections. We already optimized: ---- snip ---- net.ipv4.tcp_fin_timeout=5 # down from 30s net.ipv4.tcp_tw_reuse=1 net.ipv4.tcp_tw_recycle=1 # http://redis4you.com/articles.php?id=012&name=Redis+high+traffic+connection+issue net.ipv4.ip_local_port_range=10000 65000 # http://www.fromdual.com/huge-amount-of-time-wait-connections net.ipv4.netfilter.ip_conntrack_max=524288 ---- snip ---- But still we get (once the load is rising beyond some point): # fgrep "Cannot assign requested address" /var/log/dovecot/dovecot.log |awk '{print $N...

In article <1485416344.2047.1.camel at biggs.org.uk>, Pete Biggs <pete at biggs.org.uk> wrote: > > > > > If you are using RAID 1 kernel mirroring, you can do that with /boot too, > > and Grub finds the kernel just fine. I've done it many times: > > > > > Hmm, OK. I wonder why anaconda doesn't do it then. > > Reading various

...he is the author of the patch, can you please comment here? > > > On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > >> Thanks, but my current settings are: >> >> net.ipv4.ip_local_reserved_ports = 30000-32767 >> >> net.ipv4.ip_local_port_range = 32768 60999 >> >> meaning the reserved ports are already in the short int range, so maybe I >> misunderstood something? or is it a different issue? >> >> >> >> *From:* Atin Mukherjee [mailto:amukherj at redhat.com] >> *Sent:* Thursday, June 15,...

...n the other nodes (nginx will only read data, FTP and PHP will write also). I guess the read-rate is about 80%. - The filesystem was online extended 2 times after initial setup. - sysctl.conf parameters are set (for the webserver): -- net.ipv4.ip_nonlocal_bind=1 net.ipv4.tcp_fin_timeout=10 net.ipv4.ip_local_port_range=1024 65535 vm.swappiness=10 net.ipv4.tcp_syncookies = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_tw_recycle = 1 -- Now, the problem: The cluster runs well, but some times a day the systemload grows up from ~0-1 to 40, 500, 2000! CPU is fine, no problems. RAM is free, no problems. "ps -e -o pid...

...> +Gaurav, he is the author of the patch, can you please comment here? > > > > On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > > Thanks, but my current settings are: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > net.ipv4.ip_local_port_range = 32768 60999 > > meaning the reserved ports are already in the short int range, so maybe I > misunderstood something? or is it a different issue? > > > > *From:* Atin Mukherjee [mailto:amukherj at redhat.com] > *Sent:* Thursday, June 15, 2017 10:56 AM > *To:* Guy Cuk...

Configuration: (2) Dual Core Opterons 8GB RAM Apache used to balance 40 mongrel instances We receive Application 500 Errors. Nothing suspect appears in the log, so we are at a lost as to what to do next. Any advice would be welcome and/or an explanation of what types of things cause Application 500 Errors in mongrel. Thanks! - Jared Brown -------------- next part -------------- An HTML

...t.com>> wrote: +Gaurav, he is the author of the patch, can you please comment here? On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com<mailto:guyc at elminda.com>> wrote: Thanks, but my current settings are: net.ipv4.ip_local_reserved_ports = 30000-32767 net.ipv4.ip_local_port_range = 32768 60999 meaning the reserved ports are already in the short int range, so maybe I misunderstood something? or is it a different issue? From: Atin Mukherjee [mailto:amukherj at redhat.com<mailto:amukherj at redhat.com>] Sent: Thursday, June 15, 2017 10:56 AM To: Guy Cukierman <gu...