I can confirm this bug in Gutsy. I'm using my Ubuntu box as a home
internet gateway, and uncommenting that line did not set
/proc/sys/net/ipv4/ip_forward to 0 on reboot.
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug n
I'm using Hardy Heron and I don't believe I've been tinkering with
/etc/sysctl.conf.
Found this in the file so I believe this is fixed now?:
# Comment the next two lines to disable Spoof protection (reverse-path filter)
# Turn on Source Address Verification in all interfaces to
# prevent some spo
Sorry was abit quick at clicking "Save Changes".
This is how it looks in /etc/sysctl.conf now:
# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1
removing the # and running sysctl enables forwarding for me:
[EMAIL PROTECTED]:~# cat /proc/sys/net/ipv4/ip_forwar
I have always found that one needs to set both the "all" and the
"default" in order to guarantee the changes affect all interfaces
regardless of when those interfaces are created. In the latest hardy
version here are the options which only specify "all" and not "default"
and "all":
# Do not accep
I have a similar situation:
Running feisty, setting net.ipv4.conf.default.forwarding=1 in
/etc/sysctl.conf consistently does not enable IP forwarding in
/proc/sys/net/ipv4/ip_forward (always zero).
If I add net.ipv4.conf.all.forwarding=1, then it works ok.
--
sysctl.conf, net.ipv4.conf.default.
I have the same problem as well, running feisty latest updates,
init: init (upstart 0.3.8)
kernel:2.6.18-ovz-028stab045.1 (OPENVZ kernel)
if I put the following line
"net.ipv4.conf.all.forwarding=1"
in the "/etc/sysctl.conf" file and run "sysctl -p", forwarding is enabled
reg
To Edmunds Kalniņš, Eelko van Breda:
What happens if you just set
net.ipv4.ip_forward = 1
in /etc/sysctl.conf, and run sysctl -p?
To me, the bug looks like a mistype in default /etc/sysctl.conf (i.e.
wrong setting).
Say, here's the relevant section from Fedora 8:
# Controls IP packet forwar
@Kir Kolyshkin
Adding
net.ipv4.conf.all.forwarding=1
to sysctl.conf solves the problem.
The problem is though that in /ets/sysctl.conf it says :
# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.conf.default.forwarding=1
however uncommenting that line does not enable pac
Hi there,
same problem here on Feisty server using a single network interface with
static IP address.
When I reboot if forwarding is not enabled and I have to enable it
manually using:
echo "1" > /proc/sys/net/ipv4/ip_forward
Do you think upgrading to gutsy will solve the problem? I plan on doi
How is it possible? I can't understand why Canonical (and Debian too)
released an OS with this configuration error... very strange...
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug notification because you are a member
I can also confirm this problem with the default gutsy server install +
OpenVZ kernel (2.6.18-ovz-028stab048.1)
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
In Ubuntu 10.10 the entry in sysctl.conf was changed to
'net.ipv4.ip_forward=1', uncommenting it alone DO enable the ip routing,
and no need to add extra lines.
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug notificati
This is still an issue on Ubuntu Server 10.04
** Changed in: procps (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: procps (Ubuntu)
Assignee: Yves Junqueira (yves.junqueira) => (unassigned)
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launch
Dear friends,
FYI, this bug is mentioned in
https://help.ubuntu.com/community/Internet/ConnectionSharing .
Many blessings.
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug notification because you are a member of Ubunt
Does this bug affects hardy?
Is it fixed in hardy?
I couldn't find any infos about it's status in 8.04, thats why I'm
asking...
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug notification because you are a member of U
This bug report (marked as a duplicate) fixes it for me:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/156017
--
sysctl.conf, net.ipv4.conf.default.forwarding, race condition?
https://bugs.launchpad.net/bugs/84537
You received this bug notification because you are a member of Ubuntu
Bugs,
Hello,
On 5/8/07, Yves Junqueira <[EMAIL PROTECTED]> wrote:
> Do you still use this system where you were having problems? If so, can
> you check if you're using upstart or sysvinit?
I have upgraded the system to the latest Ubuntu, but I can try to
check these details from the backups.
> try run
18 matches
Mail list logo
