Modify

Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#905 closed defect (fixed)

/etc/sysctl.conf references invalid tcp/udp timeout meta keys - has no effect

Reported by: db90h Owned by: florian
Priority: low Milestone: Kamikaze 7.06
Component: base system Version:
Keywords: Cc:

Description

These two meta keys are NOT valid in OpenWrt and have NO effect:

net.ipv4.ip_conntrack_tcp_timeouts
net.ipv4.ip_conntrack_udp_timeouts

You should switch to individual timeout keys. Even though 'sysctl -p' verifies these keys are invalid (see below), I also did a fresh reboot to verify that the meta-keys had no effect. I came across this while adding common conntrack settngs support to webif2.

.. Example of the problem: ..

$cat /etc/sysctl.conf
net.ipv4.conf.default.arp_ignore=1
net.ipv4.conf.all.arp_ignore=1
net.ipv4.ip_forward=1
net.ipv4.icmp_echo_ignore_broadcasts=1
net.ipv4.icmp_ignore_bogus_error_responses=1
net.ipv4.tcp_fin_timeout=30
net.ipv4.tcp_keepalive_time=120
net.ipv4.tcp_syncookies=1
net.ipv4.tcp_timestamps=0
net.ipv4.ip_conntrack_tcp_timeouts="300 43200 120 60 120 120 10 60 30 120"
net.ipv4.ip_conntrack_udp_timeouts="60 180"

$ sysctl -p
root@OpenWrt:~# sysctl -p
kernel.panic = 3
net.ipv4.conf.default.arp_ignore = 1
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.ip_forward = 1
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.icmp_ignore_bogus_error_responses = 1
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_keepalive_time = 120
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_timestamps = 0
sysctl: error: 'net.ipv4.ip_conntrack_tcp_timeouts' is an unknown key
sysctl: error: 'net.ipv4.ip_conntrack_udp_timeouts' is an unknown key

Attachments (0)

Change History (8)

comment:1 Changed 11 years ago by db90h

Bleh, fucking formatting, here you go:

http://pastebin.ca/235268

comment:2 Changed 11 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Confirmed, removed in [5413]

comment:3 Changed 11 years ago by anonymous

  • Resolution fixed deleted
  • Status changed from closed to reopened

The same problem exists in kamikaze :

# sysctl net.ipv4.ip_conntrack_tcp_timeouts net.ipv4.ip_conntrack_udp_timeouts
sysctl: error: 'net.ipv4.ip_conntrack_tcp_timeouts' is an unknown key
sysctl: error: 'net.ipv4.ip_conntrack_udp_timeouts' is an unknown key

but there is also net.ipv4.tcp_syncookies

# sysctl net.ipv4.tcp_syncookies
sysctl: error: 'net.ipv4.tcp_syncookies' is an unknown key

I couldn't find if this one is also deprecated.

It was also reported here : http://forum.openwrt.org/viewtopic.php?pid=44937

comment:4 Changed 11 years ago by florian

  • Milestone changed from 0.9/rc6 to Kamikaze Milestone 1
  • Priority changed from high to low

comment:5 Changed 11 years ago by John (j5483@…

'net.ipv4.tcp_syncookies' is not deprecated. The kernel config does not have it selected. You can add it in yourself with:

$ make kernel_menuconfig
Networking --->
  Networking options --->
    [*] IP: TCP syncookie support (disabled per default)

Then save the kernel config and the entry will work as expected.

comment:6 Changed 11 years ago by florian

  • Owner changed from developers to florian
  • Status changed from reopened to new

comment:7 Changed 11 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [7042]

comment:8 Changed 11 years ago by anonymous

Ah ok, this feature was just missing from the kernel.
Also, I'm afraid I forgot an important info, I'm using the brcm 2.4 target.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.