[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
Thanks to everyone who reported/looked at this issue. ipac-ng is no longer included in any supported release of Ubuntu, so closing this as Won't Fix. ** Changed in: ipac-ng (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/122090 Title: parse_port undefined when using libipt_tcp.so directly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipac-ng/+bug/122090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
** Changed in: ipac-ng (Ubuntu) Assignee: Soren Hansen (soren) => (unassigned) -- parse_port undefined when using libipt_tcp.so directly https://bugs.launchpad.net/bugs/122090 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
** This bug is no longer flagged as a security issue -- parse_port undefined when using libipt_tcp.so directly https://bugs.launchpad.net/bugs/122090 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
iptables does not export the parse_port symbol anymore, so ipac-ng should not try to use it. ** Changed in: ipac-ng (Ubuntu) Sourcepackagename: iptables => ipac-ng -- parse_port undefined when using libipt_tcp.so directly https://bugs.launchpad.net/bugs/122090 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
K, stupid me. This doesn't affect shorewall. My startup script is as follows.
# start the firewall
shorewall_start () {
echo -n "Starting \"Shorewall firewall\": "
wait_for_pppd
$SRWL start >> $INITLOG 2>&1 && echo "done." || echo_notdone
/usr/sbin/fetchipac -S
return 0
}
and so I was getting the error on startup.
--
parse_port undefined when using libipt_tcp.so directly
https://bugs.launchpad.net/bugs/122090
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
I'm on it. ** Changed in: iptables (Ubuntu) Assignee: (unassigned) => Soren Hansen -- parse_port undefined when using libipt_tcp.so directly https://bugs.launchpad.net/bugs/122090 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
I took a quick peek at the code in Edgy and the current code, and from what I could see, it seems that the parse_port function was included in each of the dependent iptables modules in 1.3.5 (the version in Edgy), but was moved to iptables.c in 1.3.6 (the current version). So, when you're using iptables directly, everything is fine, but when using the libraries directly, parse_port is nohwere to be found. The easy fix is to add parse_port to ipac-ng, but I need to check with upstream to see why this was done. -- parse_port undefined when using libipt_tcp.so directly https://bugs.launchpad.net/bugs/122090 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly
** Visibility changed to: Public -- parse_port undefined when using libipt_tcp.so directly https://bugs.launchpad.net/bugs/122090 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
