PDA

View Full Version : [Fixed] Hosts.Rules not allowing hostnames


Mouton
11-10-2003, 03:44 PM
POLICY DENY

CLASS TEST 5

ACCEPT I 216.239. TEST 5
ACCEPT H ip216-239- TEST 5
ACCEPT H .net TEST 5My IP: 216.239.x.x
My hostname (reported by error.log): ip216-239-x-x.vif.net

I can connect with this Hosts.Rules, but if I remove the "ACCEPT I 216.239. TEST 5" line, I can't connect, even though the two other H lines should allow me to.

Anyone else could confirm that hostnames doesn't work in Hosts.Rules ?

tozz
11-10-2003, 03:52 PM
Confirmed here

POLICY DENY

CLASS USERS 10

Works.
ACCEPT H subhost.host.tld USERS 2

Does not work.
ACCEPT H .host.tld USERS 2

Should mention I use 5.2.15r with no additional scripts exept for ioZS

Harm
11-10-2003, 03:54 PM
I can confirm that they don't work with DENY either.

I used the following settings to test it:

POLICY ACCEPT 2
DENY H .nl "Test"


A few minutes later, someone from .nl logs in.

11-10-2003 21:46:19 LOGIN: "ioB_Service" "xx" "donators" "Vote ioFTPD for president" "xx@xx.gelen1.lb.home.nl"

darkone
11-10-2003, 04:59 PM
You need to restart daemon once you change that file... + hostnames are matched from the end of hostname, while ips are matched from the beginning:

I 192.168. = 192.168.*.*
H .home.net = *.home.net

Harm
11-10-2003, 05:08 PM
I did restart the daemon after the modifications and before the user's login.

tozz
11-10-2003, 06:40 PM
I restarted every time I did a modification and I've tried with both .host.tld and *.host.tld and neither of them works.

Mouton
11-10-2003, 06:41 PM
Originally posted by darkone
You need to restart daemon once you change that file... + hostnames are matched from the end of hostname, while ips are matched from the beginning:"ACCEPT H .net TEST 5" would work if that's so. It doesn't.

darkone
11-15-2003, 04:33 AM
Fixed