similar to: IPV6 warnings/errors

Hi, I'm running Plesk 11.0.9 on a Centos 5.5. A website on that box got hacked last week and malicious code got inserted into some html/php files. So I went to find out what happened... I found no back doors by using rkhunter or manually searching for suspicious files in /tmp, etc. No activity at all in the php logs at the time of the attack. I also analysed of course the system logs

I am using proftpd with my first Centos 5 box. Although it appears to be working, I see the following errors in my logwatch reports. Deprecated pam_stack module called from service "proftpd" pam_unix(proftpd:session): session opened for user steve by (uid=0) Deprecated pam_stack module called from service "proftpd" Deprecated pam_stack module called from service

http://bugzilla.netfilter.org/show_bug.cgi?id=742 Summary: ip6tables "-m iprange" ipv6 range detection Product: netfilter/iptables Version: linux-2.6.x Platform: x86_64 OS/Version: SuSE Linux Status: NEW Severity: critical Priority: P5 Component: ip6_tables (kernel) AssignedTo:

Package: logcheck-database Version: 1.2.49 Severity: normal Tags: patch Hi, with "UseReverseDNS off" in /etc/proftpd/proftpd.conf the IP is used instead of the hostname: ... (::ffff:aaa.bbb.ccc.ddd[::ffff:aaa.bbb.ccc.ddd]) ... The rules in /etc/logcheck/ignore.d.server/proftpd do not support colons in the hostname. The attached patch fixes this. Greetings, Gregor -- System

Package: logcheck-database Version: 1.2.54 Severity: normal It would appear that proftpd is now logging IP addresses in IPv6 form, even the v4 ones. I got a bunch of these last week: Aug 7 04:00:11 goretex proftpd: (pam_unix) authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:58.60.237.66 user=mysql Simply adding a ":" to the rhost character class did the

https://bugzilla.netfilter.org/show_bug.cgi?id=851 Summary: IPv6 SNAT target with --random doesn't work Product: netfilter/iptables Version: unspecified Platform: x86_64 OS/Version: All Status: NEW Severity: normal Priority: P5 Component: NAT AssignedTo: netfilter-buglog at lists.netfilter.org

I have been experiencing a problem with using X11 forwarding on an IPv6 enabled host (both CentOS 4.3 and Feddora Core 5 in x86) when X11UseLocalhost is off. Having looked at the code and the previous discussion regarding http://bugzilla.mindrot.org/show_bug.cgi?id=164 I think the problem is due to the IPV6_V6ONLY code interacting poorly with the DONT_TRY_OTHER_AF hack. Basically, on current

Hello list! Well I have delved back into my proftpd config in the hopes of resolving my issues and having a working server. :) I believe I have the passive mode issue that I was expereriencing last time mostly worked out. But there are still a couple of things going on with this config that I was hoping to run by you in hopes of finding a solution. If I execute an ftp session on localhost

Hello, how do achieve this: how must files /etc/sysconfig/network-scripts/ look like to be the same as entering the following two commands ... ip -f inet6 rule add fwmark 1 lookup 100 ip -f inet6 route add local ::/0 dev lo table 100 is there the localhost device lo correct, or does it have to be br0? e.g. a file route-br0 with 192.168.1.0/24 via 10.10.10.1 dev br0 does the routing to the

https://bugzilla.netfilter.org/show_bug.cgi?id=1221 Bug ID: 1221 Summary: "fib" produces strange results with an IPv6 default route Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5

Hi, I''m trying to use HTB for IPv6 packets. In the LARTC archive I found a thread on this issue where a solution was described. The idea is to mark a user-defined chain then use the fwmark for filtering. However my attempt wasn''t successful. I''m thinking of trying my luck with the u32 filter. This is what I did, any comment is greatly appreciated. Thank you all. tc

https://bugzilla.netfilter.org/show_bug.cgi?id=1342 Bug ID: 1342 Summary: IPv6 NAT translates to addresses outside of specified range Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: normal Priority: P5

Hi I don''t quite understand the new xen networking. We use network-bridge! Everything works fine except that an iptables firewall on dom0 blocks all my domU. In my firewall settings i use eth0. I figured out that eth0 is the bridge but where is the interface for dom0? I want my firewall setting to only apply to dom0 interface! Since there is not anything like vif0.0 i don''t know

https://bugzilla.netfilter.org/show_bug.cgi?id=940 Summary: ip6tables-save output invalid rule when using D/SNPT Product: iptables Version: 1.4.x Platform: x86_64 OS/Version: All Status: NEW Severity: normal Priority: P5 Component: ip6tables AssignedTo: netfilter-buglog at lists.netfilter.org

Simple police filter below works for IPv4 traffic, but not for IPv6 traffic. Tested with 2.4.26 and 2.6.6 kernel. Am I doing something wrong or is it bug? Same filter logic works with imq+htb for both IPv4 and IPv6 traffic. iptables -A PREROUTING -i eth1.101 -t mangle -j MARK --set-mark 0x101 ip6tables -A PREROUTING -i eth1.101 -t mangle -j MARK --set-mark 0x101 tc qdisc add dev eth1.101

https://bugzilla.netfilter.org/show_bug.cgi?id=1116 Bug ID: 1116 Summary: Can't create Ipv6 NAT entries with conntrack Product: conntrack-tools Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: conntrack Assignee:

http://bugzilla.netfilter.org/show_bug.cgi?id=761 Summary: Bug in ICMPv6 type and code fields processing Product: ipset Version: unspecified Platform: i386 OS/Version: Gentoo Status: NEW Severity: major Priority: P5 Component: default AssignedTo: netfilter-buglog at lists.netfilter.org

CentOS 5.5, fully patched. I have a HE tunnel (tunnelbroker.net) IPv6 tunnel. This works pretty well and is simple to setup. Everything works fine. Until I try to set up an ip6tables firewall. eg if I try to view https://dnssec.surfnet.nl/?p=464 then the page never displays and the firewall shows kernel: IN=sit1 OUT=eth0 SRC=2001:0610:0001:40cd:0145:0100:0186:0033 DST=my.machine LEN=80 TC=0

I discovered that IPv6 is sort of working when I got an email rejection from Comcast for not having an IPv6 PTR record. I discovered I could telnet to port 25 on their MX server over IPv6! I then found I could tracroute6 to them, but I couldn't to my Linode VPS in Fremont. It gets to the data center and stops. Going the other way, my Linode can traceroute6 almost to my AT&T-hosted

hi It was not working when i applied the rules on the vpn card. But I wondered if maybe bridging of vpn and eth0 was messing this up. I thought it was enough to only apply it to the vpn card root at JOTVPN:~# brctl show bridge name bridge id STP enabled    interfaces bridge 8000.000c29638a7e no           eth0                                                                   vpn so I tried the