Oddity with /proc/sys/net/ipv4/conf/all

• Next message: Mike Fedyk: "[Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming routes]"
• Previous message: Jens Axboe: "Re: report bug: System reboots when accessing a loop-device over a second loop-device with 2.4.2-ac7"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

According to Documentation/networking/ip-sysctl.txt:

conf/all/* is special and changes the settings for all interfaces.

However, I did this:

mercury:~# echo 1 >/proc/sys/net/ipv4/conf/all/log_martians
mercury:~# cat /proc/sys/net/ipv4/conf/all/log_martians
1
mercury:~# cat /proc/sys/net/ipv4/conf/lo/log_martians
0
mercury:~# cat /proc/sys/net/ipv4/conf/eth0/log_martians
0

So it looks like the changes are not reflected in the individual
interfaces. What's going on?

Also, can anyone tell me how to test whether these options are
working? (For instance, how can I send myself a martian packet, to
see if it is logged?) I considered the possibility that the option
really is on, and sysctl just doesn't report it, but I didn't know how
to find out.

This is kernel 2.4.2-ac7.

-- 
Nate Eldredge
neldredge@hmc.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

• Next message: Mike Fedyk: "[Fwd: [LARTC] 1 adsl + 1 sdsl + masq + simultaneous incomming routes]"
• Previous message: Jens Axboe: "Re: report bug: System reboots when accessing a loop-device over a second loop-device with 2.4.2-ac7"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:13 EST