[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2011-12-21 Thread Clint Byrum
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,

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2009-03-20 Thread Rick Clark
** 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. --

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2007-12-11 Thread Jamie Strandboge
** 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

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2007-07-10 Thread Soren Hansen
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

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2007-06-25 Thread Soren Hansen
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

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2007-06-25 Thread Soren Hansen
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

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2007-06-25 Thread Martin Pitt
** 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

[Bug 122090] Re: parse_port undefined when using libipt_tcp.so directly

2007-06-25 Thread wayne
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 21 echo done. || echo_notdone /usr/sbin/fetchipac -S return 0 } and so I was getting the