News: This forum is now permanently frozen.
Pages: [1]
Topic: dhcp problem Permission denied (r500)  (Read 5410 times)
« on: May 08, 2012, 11:05:35 »
jstrebel *
Posts: 31

Hi, i experience the following problem, I see the log full with the messages below. Other Clients where able to get a address during this "event". I do not get any meaningful advice with google.
However I see users of pfsense and m0n0 where posting somewhat similar events.

Q: What is the best path to get more info to dig deeper and help to resolve or debug the issue. I
(the box is remote)

Thanks jakob

Apr 27 09:46:47   dhcpd: send_packet: Permission denied
Apr 27 09:46:47   dhcpd: DHCPOFFER on 172.16.5.69 to 34:15:9e:8a:86:7d via vr2
Apr 27 09:46:47   dhcpd: DHCPDISCOVER from 34:15:9e:8a:86:7d via vr2
Apr 27 09:46:39   dhcpd: send_packet: Permission denied
Apr 27 09:46:39   dhcpd: DHCPOFFER on 172.16.5.69 to 34:15:9e:8a:86:7d via vr2
Apr 27 09:46:39   dhcpd: DHCPDISCOVER from 34:15:9e:8a:86:7d via vr2
« Reply #1 on: May 08, 2012, 14:14:22 »
dr01 **
Posts: 79

If this issue is happening when using Captive Portal then I suggest turning off CP, we also have the similar issues at times with the b500 releases. It seems to act up randomly on traveling users at our remote locations.

thx, dr01
« Reply #2 on: May 08, 2012, 17:52:54 »
jstrebel *
Posts: 31

yes it is a issue happen with the CP. But we need the CP function.
BTW. After a restart the same client who got permission denied get a address from DHCP.

Jakob
« Reply #3 on: May 22, 2012, 16:32:37 »
dr01 **
Posts: 79

we have found in our testing at all our clients sites that the CP function inside Monowall has issues with certain Win7 OS and some MacOS laptops....even sometimes WinXP OS.....we tried the r510 latest release and its even worse....we went back to r500 and it seemed to stabilize some however we still have many travelrs that get locked up on the CP page and require the direct login to the CP page in order to get out to the redirect page and internet....sometimes it even locks up after you hit the accept button on the CP sign in page....

we are using simple html code for writing our CP sign in page and graphics....

we would like an answer or a fix to this issue....I also suggest r510 be looked at for bugs related to the CP page and aquiring internet past it....

CP has always had issues at times with different OS models....

thx  dr01
« Reply #4 on: May 23, 2012, 10:13:50 »
jstrebel *
Posts: 31

dr01,
would be interesting to see what you see in the syslog. Do you have a possibility to send this logs to a external syslog server. Without a log or a "procedure" how to reproduce this it will be extremely difficult to find the root cause what is producing this annoying error.
Jakob
« Reply #5 on: May 23, 2012, 15:38:05 »
dr01 **
Posts: 79

May 22 21:08:55 ACCEPT: unauthenticated, 00:22:5f:c9:89:70, 172.20.1.75
May 22 21:05:40 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:05:30 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:05:20 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:05:10 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:05:00 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:04:50 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:04:40 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 22 21:04:30 ERROR: unauthenticated, noclientmac, 172.20.1.75
May 23 00:07:18 TIMEOUT: unauthenticated, 10:40:f3:17:4d:a7, 172.20.1.53
May 22 23:59:33 ACCEPT: unauthenticated, 4c:0f:6e:67:a7:0b, 172.20.1.89
May 22 23:45:16 TIMEOUT: unauthenticated, b8:8d:12:32:d0:18, 172.20.1.52
May 22 23:29:56 ACCEPT: unauthenticated, 34:51:c9:58:c8:a5, 172.20.1.39
May 22 23:22:14 TIMEOUT: unauthenticated, 20:10:7a:11:3c:bd, 172.20.1.49
May 22 23:21:14 TIMEOUT: unauthenticated, c4:17:fe:ba:52:f5, 172.20.1.43
May 22 23:20:14 TIMEOUT: unauthenticated, 7c:c5:37:2a:16:40, 172.20.1.48
May 22 23:17:14 TIMEOUT: unauthenticated, d8:9e:3f:55:f4:35, 172.20.1.47
May 22 23:17:14 TIMEOUT: unauthenticated, 18:e7:f4:fc:ba:fb, 172.20.1.46
May 22 23:15:41 ACCEPT: unauthenticated, 18:20:32:d8:c9:c6, 172.20.1.88
May 22 23:08:13 TIMEOUT: unauthenticated, 68:a8:6d:69:70:ac, 172.20.1.45
May 22 23:06:13 TIMEOUT: unauthenticated, 70:de:e2:23:6f:ac, 172.20.1.44
May 22 23:04:18 ACCEPT: unauthenticated, 18:20:32:e0:e3:71, 172.20.1.86
May 22 22:50:05 ACCEPT: unauthenticated, 00:23:4e:25:75:d0, 172.20.1.85
May 22 22:28:11 TIMEOUT: unauthenticated, 00:26:bb:10:ae:4a, 172.20.1.42
May 22 22:28:11 TIMEOUT: unauthenticated, 28:cf:da:68:27:4f, 172.20.1.41
May 22 22:16:10 TIMEOUT: unauthenticated, d0:df:9a:7f:51:43, 172.20.1.40
May 22 22:07:09 TIMEOUT: unauthenticated, 34:51:c9:58:c8:a5, 172.20.1.39
May 23 09:36:00 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:36:00 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:34:47 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:34:47 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:32:51 dhcpd: DHCPACK on 172.20.1.226 to 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:32:51 dhcpd: DHCPREQUEST for 172.20.1.226 from 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:32:24 dhcpd: DHCPACK on 172.20.1.226 to 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:32:24 dhcpd: DHCPREQUEST for 172.20.1.226 from 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:32:19 dhcpd: DHCPACK on 172.20.1.248 to 00:1d:e0:03:5e:5b (01SCNB23) via xl0
May 23 09:32:19 dhcpd: DHCPREQUEST for 172.20.1.248 from 00:1d:e0:03:5e:5b (01SCNB23) via xl0
May 23 09:32:19 dhcpd: Wrote 109 leases to leases file.
May 23 09:32:19 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 23 09:32:19 dhcpd: Wrote 0 deleted host decls to leases file.
May 23 09:29:07 dhcpd: DHCPACK on 172.20.1.62 to 10:f9:6f:b4:cd:8d (android_7d17f175921b0e3f) via xl0
May 23 09:29:07 dhcpd: DHCPREQUEST for 172.20.1.62 (172.20.1.1) from 10:f9:6f:b4:cd:8d (android_7d17f175921b0e3f) via xl0
May 23 09:29:07 dhcpd: DHCPOFFER on 172.20.1.62 to 10:f9:6f:b4:cd:8d (android_7d17f175921b0e3f) via xl0
May 23 09:29:06 dhcpd: DHCPDISCOVER from 10:f9:6f:b4:cd:8d (android_7d17f175921b0e3f) via xl0
May 23 09:28:03 dhcpd: DHCPACK on 172.20.1.226 to 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:28:03 dhcpd: DHCPREQUEST for 172.20.1.226 from 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:27:31 dhcpd: DHCPACK on 172.20.1.41 to 28:cf:da:68:27:4f (meR) via xl0
May 23 09:27:31 dhcpd: DHCPREQUEST for 172.20.1.41 from 28:cf:da:68:27:4f (meR) via xl0
May 23 09:27:29 dhcpd: DHCPACK on 172.20.1.41 to 28:cf:da:68:27:4f (meR) via xl0
May 23 09:27:29 dhcpd: DHCPREQUEST for 172.20.1.41 from 28:cf:da:68:27:4f (meR) via xl0
May 23 09:27:03 dhcpd: DHCPACK on 172.20.1.226 to 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:27:03 dhcpd: DHCPREQUEST for 172.20.1.226 from 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:26:28 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:26:28 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:26:28 dhcpd: Wrote 109 leases to leases file.
May 23 09:26:28 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 23 09:26:28 dhcpd: Wrote 0 deleted host decls to leases file.
May 23 09:19:44 dhcpd: DHCPACK on 172.20.1.246 to 00:16:16:02:89:db via xl0
May 23 09:19:44 dhcpd: DHCPREQUEST for 172.20.1.246 from 00:16:16:02:89:db via xl0
May 23 09:18:59 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:18:59 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:18:59 dhcpd: Wrote 109 leases to leases file.
May 23 09:18:59 dhcpd: Wrote 0 new dynamic host decls to leases file.
May 23 09:18:59 dhcpd: Wrote 0 deleted host decls to leases file.
May 23 09:17:48 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:17:48 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:17:42 dhcpd: DHCPACK on 172.20.1.226 to 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:17:42 dhcpd: DHCPREQUEST for 172.20.1.226 from 04:54:53:d8:fd:dc (iPad) via xl0
May 23 09:16:23 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:16:23 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:15:11 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:15:11 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:14:00 dhcpd: DHCPACK on 172.20.1.235 to 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:14:00 dhcpd: DHCPREQUEST for 172.20.1.235 from 70:de:e2:b7:fd:be (Marilyn-J-Willl) via xl0
May 23 09:13:06 dhcpd: DHCPACK on 172.20.1.41 to 28:cf:da:68:27:4f (meR) via xl0
May 23 09:13:06 dhcpd: DHCPREQUEST for 172.20.1.41 from 28:cf:da:68:27:4f (meR) via xl0
May 23 09:13:06 dhcpd: Wrote 109 leases to leases file.


will this help?  dr01
« Reply #6 on: May 23, 2012, 21:23:16 »
brushedmoss ****
Posts: 446

Jaystrbel

Your issue looks like a firewall config issue or a bug in the rules.

Can you pm me the output of status.php anonymising as you see fit, though anonymising inconsistently means I cant debug
« Reply #7 on: May 24, 2012, 18:47:50 »
dr01 **
Posts: 79

is the status.php output located in the GUI interface? I cannot seem to find that to export...
thx
dr01
« Reply #8 on: May 25, 2012, 00:16:25 »
brushedmoss ****
Posts: 446

dr01,  see http://doc.m0n0.ch/handbook/config-status.html

, your logs don't have the same problem as Jaystrbel, I don't know what your issue might be as you don't give me enough hints.

Unless you have the same problem as the subject of this thread, would you start a new thread instead and give more detail of the problems you have (i.e. do your users get an ip address but can't get to the CP page, or they don't get an IP etc. etc.)

Thanks !
« Reply #9 on: May 25, 2012, 17:34:55 »
jstrebel *
Posts: 31

is the status.php output located in the GUI interface? I cannot seem to find that to export...
thx
dr01

Look at this:
http://m0n0.ch/wall/notes.php
« Reply #10 on: May 29, 2012, 17:41:18 »
dr01 **
Posts: 79

OK we have narrowed down the issue to a trait, when the CP is fully loaded up with like 40-50 signed in users then at random it will not let users past the sign in page but give out an IP through dhcp....sometimes the users in a heavy use condition dont even get the CP sign in page....

does that help?
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines