| 2007-02-11 13:55:20 |
JS |
bug |
|
|
added bug |
| 2007-02-11 13:58:30 |
JS |
description |
Binary package hint: procps
/etc/sysctl.conf contains the following lines by default:
# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.conf.default.forwarding=1
In my system, uncommenting the line _usually_ does the trick: IPv4 forwarding is enabled on all network interfaces. Unfortunately, this was not the case every time. Sometimes, once in 10 reboots or so, this did not work. IPv4 forwarding was not enabled on some network interfaces.
I am not 100 % sure why this happens, but I think it might be caused if sometimes a network interface gets initialised before sysctl
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.all.forwarding=1
I have two physical network interfaces, "eth0" and "eth1", both of which use the "e100" driver. |
Binary package hint: procps
/etc/sysctl.conf contains the following lines by default:
# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.conf.default.forwarding=1
In my system, uncommenting the line _usually_ does the trick: IPv4 forwarding is enabled on all network interfaces. Unfortunately, this was not the case every time. Sometimes, once in 10 reboots or so, this did not work. IPv4 forwarding was not enabled on some network interfaces.
I am not 100 % sure why this happens, but I think it might be caused if sometimes a network interface gets initialised before sysctl sets the above setting. Thus, I tried to define the following _two_ settings in /etc/sysctl.conf:
net.ipv4.conf.default.forwarding=1
net.ipv4.conf.all.forwarding=1
(I think the first setting tells what happens to the new interfaces that are created after setting the sysctl, and the second setting tells what happens to the interfaces that have already been created?)
Now everything has worked fine for months. Every time IPv4 forwarding gets enabled properly.
I have two physical network interfaces, "eth0" and "eth1", both of which use the "e100" driver.
lspci:
02:02.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08)
02:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (LOM) Ethernet Controller (rev 82)
|
|
| 2007-05-08 01:03:23 |
Yves Junqueira |
procps: status |
Unconfirmed |
Needs Info |
|
| 2007-05-08 01:03:23 |
Yves Junqueira |
procps: assignee |
|
yves.junqueira |
|
| 2007-05-08 01:03:23 |
Yves Junqueira |
procps: statusexplanation |
|
Hi.
Thank you for your report.
Do you still use this system where you were having problems? If so, can you check if you're using upstart or sysvinit?
try running /sbin/init --version and see if it's upstart or else.
Also, was that interface using DHCP or static addresses?
Usually, at least for upstart, rcS is run before networking scripts, but this needs further testing I guess. I'll see if I can reproduce it myself. |
|
| 2010-08-17 06:49:51 |
Christoffer Holmstedt |
bug |
|
|
added subscriber Christoffer Holmstedt |
| 2010-09-13 10:34:52 |
Hew |
procps (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2010-09-13 10:34:52 |
Hew |
procps (Ubuntu): assignee |
Yves Junqueira (yves.junqueira) |
|
|
| 2010-09-15 20:18:15 |
JS |
removed subscriber JS |
|
|
|
| 2011-01-25 11:42:18 |
Sergey Svishchev |
bug |
|
|
added subscriber Sergey Svishchev |
| 2011-12-08 09:04:17 |
Sergey Svishchev |
removed subscriber Sergey Svishchev |
|
|
|
| 2012-02-26 12:01:17 |
Hew |
removed subscriber Hew McLachlan |
|
|
|
| 2012-08-18 12:38:33 |
Christoffer Holmstedt |
removed subscriber Christoffer Holmstedt |
|
|
|
