Ip forward - Revision history

Smoofra at 04:27, 2 March 2010

2010-03-02T04:27:19Z

Smoofra at 04:26, 2 March 2010

2010-03-02T04:26:55Z

Smoofra at 00:04, 2 March 2010

2010-03-02T00:04:45Z

Smoofra at 00:02, 2 March 2010

2010-03-02T00:02:15Z

Smoofra at 23:58, 1 March 2010

2010-03-01T23:58:08Z

Smoofra at 21:05, 1 March 2010

2010-03-01T21:05:16Z

Smoofra: New page: You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0. If you go into /etc/network/options and change the line ip_forward=no to ip_forward=yes, the problem se...

2010-03-01T21:04:23Z

New page: You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0. If you go into /etc/network/options and change the line ip_forward=no to ip_forward=yes, the problem se...

New page

You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0. If you go into /etc/network/options and change the line ip_forward=no to ip_forward=yes, the problem seems to go away.

@@ Line 35: / Line 35: @@
 Another way to solve this problem is to make /proc/sys/net/ipv4/ip_forward innaccessable.  As PuffTheMagic_ put it:
 <pre>
-&lt;PuffTheMagic_gt; smoofra: mount -o bind /dev/null over ip_forward
+&lt;PuffTheMagic_&gt; smoofra: mount -o bind /dev/null over ip_forward
-&lt;PuffTheMagic_gt; then mount proc in a new directory
+&lt;PuffTheMagic_&gt; then mount proc in a new directory
-&lt;PuffTheMagic_gt; and set it to 1 from that new dir
+&lt;PuffTheMagic_&gt; and set it to 1 from that new dir
-&lt;PuffTheMagic_gt; ;)
+&lt;PuffTheMagic_&gt; ;)
 </pre>

@@ Line 31: / Line 31: @@
 stop PmNetConfigManager
 start PmNetConfigManager
 </pre>

@@ Line 20: / Line 20: @@
 <pre>
 mount -o remount,rw /
-mkdir /media/cryptofs/fake/sys/net/ipv4/ip_forward
+mkdir-p /media/cryptofs/fake/sys/net/ipv4
 ln -s /media/cryptofs/fake /fake
 mount -o remount,ro /
 </pre>

← Older revision		Revision as of 00:02, 2 March 2010
Line 25:		Line 25:
	</pre>		</pre>

−	Next, patch /usr/bin/PmNetConfigManager so it writes to /fake/sys/net/ipv4/ip_forward instead of /proc/sys/net/ipv4/ip_forward. Just open it up in a hex editor, find that path, and change "proc" to "fake". Make sure you only change those four bytes.	+	Next, patch /usr/bin/PmNetConfigManager so it writes to /fake/sys/net/ipv4/ip_forward instead of /proc/sys/net/ipv4/ip_forward. Just open it up in a hex editor, find that path, and change "proc" to "fake". Make sure you only change those four bytes. You should probably also make sure you have a backup of the original binary. After you replace PmNetConfigManager, restart it.
		+
		+	<pre>
		+	stop PmNetConfigManager
		+	start PmNetConfigManager
		+	</pre>

← Older revision		Revision as of 21:05, 1 March 2010
Line 1:		Line 1:
−	You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0. If you go into /etc/network/options and change the line ip_forward=no to ip_forward=yes, the problem seems to go away.	+	You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0. If you go into
		+	/etc/network/options and change the line
		+	<pre>ip_forward=no
		+	</pre> to
		+	<pre>
		+	ip_forward=yes
		+	</pre> the problem seems to go away.

@@ Line 1: / Line 1: @@
-You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0.  If you go into
+You might have noticed that /proc/sys/net/ipv4/ip_forward keeps getting reset to 0.
 /etc/network/options and change the line
 <pre>ip_forward=no
 </pre> to
 <pre>
 ip_forward=yes
-</pre> the problem seems to go away.
+</pre>