bad client ip format

33 views
Skip to first unread message

codcodoe

unread,
Mar 26, 2025, 9:01:03 PMMar 26
to Event-Driven Servers
Hi Marc,

  We try to limit client ip, but for some NAS, we get wrong ip format like below.
port=tty1 nac=192.168.213.27 00:00:00:00:00:00

Does it possible to filter the bad format in config
            rule restrict_rinos_access {
                enabled = true
                script {
                    if (user == XX) {
                        if (client != rinos_clients) {
                            deny
                        }
                    }
                }
            }

Marc Huber

unread,
Mar 27, 2025, 12:15:12 PMMar 27
to event-driv...@googlegroups.com

Hi,

looks like your device adds something similar to a MAC address to the TACACS+ packet's remote address field. Your best way of matching that would be with a regular expression, e.g..

  if (client !~ /^192\.168\ .213´/) deny

There's currently no way to sanitize device input. What vendor and product does cause that issue?

Cheers,

Marc

--
You received this message because you are subscribed to the Google Groups "Event-Driven Servers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to event-driven-ser...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/event-driven-servers/d7e7e69d-f9f2-4749-a677-2391c8283dcen%40googlegroups.com.

codcodoe

unread,
Mar 30, 2025, 8:56:29 PMMar 30
to Event-Driven Servers
Hi  Marc,

Thank you for your reply.
The NAS is ZyXEL GS3700,  it is an older device.
We  would be with a regular expression to solve this problem.

Regards,
Marc Huber 在 2025年3月28日 星期五凌晨12:15:12 [UTC+8] 的信中寫道:

Marc Huber

unread,
Apr 1, 2025, 3:18:55 PMApr 1
to event-driv...@googlegroups.com

Hi,

with commit 95148ce1343f698530e0ea3106161a00e38a8dfb, setting "bug compatibility = 16" at host level might help, too.

Cheers,

Marc

Reply all
Reply to author
Forward
0 new messages