Unknown column 'ip_lo' NS 2.5.17

Susann · Posted: Wed Apr 30, 2008 6:53 am

In rnlogs I got this entry:

Quote:

Unknown column 'ip_lo' in 'order clause'
SQL was: SELECT * FROM `nuke_nsnst_blocked_ips` ORDER BY ip_lo asc LIMIT 0,50
remote addr: xxx

Could this be from STIPS.php ?

fkelly · Posted: Wed Apr 30, 2008 7:14 am

It looks like it could be. There is no ip_lo column in nsnst_blocked_ips table. The column that is searched is parameterized, so to speak, based on your selection and somehow 'ip_lo' is getting in there. Maybe it comes from doing a range search against the blocked_ips table but Bob would have to look into that.

Susann · Posted: Wed Apr 30, 2008 11:06 am

Its not urgent and I can wait until Bob looked into this but I believe its from modules.php?name=NukeSentinel&op=STIPS

BobMarion · Posted: Wed Apr 30, 2008 7:49 pm

Open modules/NukeSentinel/public/STIPS.php find line 20:

Code:

if ($column != "ip_long" and $column != "reason" and $column != "date") { $column = "ip_lo"; }

Change the "ip_lo" to "ip_long" like so:

Code:

if ($column != "ip_long" and $column != "reason" and $column != "date") { $column = "ip_long"; }

Must have been copied over when updating the ip2country and range pacges Sad

Susann · Posted: Thu May 01, 2008 7:12 am

Thanks ! Older versions like 2.5.16 have the same line with ip_lo there but everybody should always use the current version of NukeSentinel to be really up-to-date and protected.