Your message dated Thu, 28 Jan 2016 13:53:16 +0100
with message-id
<CAOkSjBhRrt1zSFj+BKcsdfZBTut2oF9=G7mL=9==sq-muf2...@mail.gmail.com>
and subject line iptables: internet sharing not working
has caused the Debian Bug report #639764,
regarding iptables: internet sharing not working
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
639764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639764
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: iptables
Version: 1.4.12-1
Severity: normal
hello,
i use network-manager to share my internet connection from my usb modem
connection to my ethernet connection, before iptables upgraded to 1.4.12
everything was o.k,
after iptables upgrade client from ethernet connection doesn't recieved
data,
then i downgrade iptables to 1.4.11.1-3 everything back to normal.
finnaly i found that iptables-1.4.12 didn't create this rules :
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
MASQUERADE all -- 10.42.43.0/24 !10.42.43.0/24
-- System Information:
Debian Release: wheezy/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing'),
(200, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages iptables depends on:
ii libc6 2.13-16 Embedded GNU C Library:
Shared lib
ii libnfnetlink0 1.0.0-1 Netfilter netlink library
iptables recommends no packages.
iptables suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.6.0-2
Hi,
I think the problem was with the inversion of the range.
This is very similar to #739251
Fortunately, iptables 1.6.0 doesn't seem to have this issue.
Also, version 1.4.12-1 is no longer in the archive.
I think we can close this bug. Please, feel free to reopen if you find
any issue.
best regards.
--
Arturo Borrero González
--- End Message ---
