/proc/sys/net/ipv4/ip_local_port_range suse 10.1 not set at boot

PredatorX · 11-25-2006, 09:53 AM

I am trying to install Oracle 10g / AS on Opensuse 10.1 .
1 of the requirements is setting the port range, found in
/proc/sys/net/ipv4/ip_local_port_range .
Among other settings that do work, is put the line
net.ipv4.ip_local_port_range = 1024 65000
in /etc/sysctl.conf .

When rebooting and doing a
cat /proc/sys/net/ipv4/ip_local_port_range
i get
1024 29999
.
When doing a sysctl -d i do get the right ports.
Does anyone know if this is a bug?
Or maybe a Suse specific thing messing this up?

Any info very welcome?

nuxrl · 11-26-2006, 07:42 PM

Quote:

sysctl -d

Did you mean

Code:

#sysctl -a

Change

Quote:

net.ipv4.ip_local_port_range = 1024 65000

to

Code:

net.ipv4.ip_local_port_range=1024 65000

and do a

Code:

#/sbin/sysctl -p /etc/sysctl.conf

to see what happens.

PredatorX · 11-27-2006, 04:49 AM

thanks for the quick response.
with the -d i meant -p (sorry), so setting the settings from /etc/sysctl.conf.
I tried your advice, it did not work.
Seems like a bug to me?

i'll wait for a while if anyone can solve it, else I'll report a bug.
Does it work on your pc?
any1 can try it on suse 10.1?
thanks

nuxrl · 11-27-2006, 07:04 AM

PredatorX,

I tried in my system, Ubuntu 6.10, and it worked. I don't use Suse so I can't say if Suse does something specially. One thing you might try is to see if there's another line in /etc/sysctl.conf with the same key net.ipv4.ip_local_port_range, but I doubt about that.

I will keep my eyes on this thread. It would be interesting to see what comes out.

Good luck!

-n

PredatorX · 11-29-2006, 01:54 AM

It seems it does not work.
There is no other line that conflicts with the settings.
I've installed the orarun package form Novell, which is fo SLES, but works for Suse 10.1.
I saw the approach there is putting the setting in /etc/sysconfig/oracle ,
but that has no effect either.
Found on google that SLES has a command for explicitly using sysctl.conf :
chkconfig boot.sysctl on
That did not fix it either.
Guess I'll have to file a bug report, I'll post the number if it's done.