News: This forum is now permanently frozen.
Pages: 1 [2]
Topic: 1.8 Beta bugs  (Read 11284 times)
« Reply #15 on: January 30, 2012, 12:45:14 »
Manuel Kasper
Administrator
*****
Posts: 364

I have been testing the new b491 version of monowall and zeroing in on the captive portal features along with the traffic shaping features while performing numerous speed tests. In my findings and my reading I have seen that you must have 'per user bandwidth restrictions' turned on in captive portal in order to effectively traffic shape....is this true?

Depends on what you want to do. If you just want to do some overall traffic shaping (e.g. fair distribution of the available upload bandwidth) and not give a fixed (possibly RADIUS-controlled) limit to a particular user, then the "per user bandwidth restrictions" are not needed and you can simply configure the traffic shaper as normal.

My tests having both traffic shaping turned on and set to a download and upload value in comjunction with the per user restriction set to those same values in CP seem to conflict and cause slower speeds. When I turn off per user restrictions in CP and leave just TS turned on it seem to perform better speed tests and more reliable.

The per-user bandwidth restrictions apply on the captive portal interface; it's a bit like dynamically adding pipes and rules for each user at the top of the list (so if you have per-user restrictions on, then other traffic shaper rules on the captive portal interface won't have any effect). However, if you have traffic shaper rules on your WAN interface, then the traffic will effectively be shaped twice (once on WAN, and once by the per-user bandwidth restriction on the CP interface), leading to reduced performance.

I'd recommend against mixing normal traffic shaping rules and per-user limits.
« Reply #16 on: February 01, 2012, 02:11:15 »
dr01 **
Posts: 79

I tried that and in previous versions 1.31 embedded, that is possible you can have no traffic shaping but have per user turned on....in version 492 you cannot as an error message appears that says you must have TS turned on in order to have CP per user turned on...Huh I think there may be a bug with this in version 492.....please let me know....thank you 
« Reply #17 on: February 01, 2012, 13:01:04 »
Manuel Kasper
Administrator
*****
Posts: 364

You need to enable the traffic shaper in order to use per-user bandwidth limits in m0n0wall 1.8, but you don't have to add any rules/pipes/queues to the traffic shaper.
« Reply #18 on: February 01, 2012, 18:01:35 »
dr01 **
Posts: 79

thank you....i have set to evenly on LAN in TS with no rules and the CP per user limit set....this seems to work good.

Also there seems to be a CP issue in allowing some devices online and handing them out an IP address...it seesm to happy sometimes with Mac laptops getting past the portal page...also some XP machines as well....would you happen to know why this is happerning? We have numerous of these running in the hospitality industry out there and our support line gets a few calls from these types of issues. It seems when I tuen off CP it resolved that persons issues in getting an IP address or past the CP page.

Have you heard of this issue before?

I also can priovide you the remote login credentials if you would like to login in and look at the config...

Thank you manuel....

dr01
« Reply #19 on: April 14, 2012, 17:23:14 »
wjc007 *
Posts: 9

Hello,1.8.503 Firewall: Traffic shaper edit Description or Save
Warning: Invalid argument supplied for foreach() in /etc/inc/scheduler.inc on line 366 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/scheduler.inc:366) in /usr/local/www/firewall_shaper_edit.php on line 347
« Reply #20 on: April 15, 2012, 16:32:29 »
Lennart Grahl ***
Posts: 153

Hello,1.8.503 Firewall: Traffic shaper edit Description or Save
Warning: Invalid argument supplied for foreach() in /etc/inc/scheduler.inc on line 366 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/scheduler.inc:366) in /usr/local/www/firewall_shaper_edit.php on line 347

I've fixed it but I actually don't know how this could have happened in the first place (Jobset without a number of defined jobs). Could you describe your actions? Have you modified the configuration file yourself?

Regards,
Lennart
« Reply #21 on: April 16, 2012, 13:15:25 »
wjc007 *
Posts: 9

Hello
   I fill in description and then click the save will prompt alarm,1.8.504 Have normal。

Thanks



« Reply #22 on: April 16, 2012, 14:19:30 »
Lennart Grahl ***
Posts: 153

Hello
   I fill in description and then click the save will prompt alarm,1.8.504 Have normal。

Thanks

Thanks, I've located the problem. The temporary fix in 504 will do no harm so I'll leave it that way for now.
« Reply #23 on: April 24, 2012, 16:40:00 »
wjc007 *
Posts: 9

Hello, Wlan(Atheros5212)Mode: AP ,Bridge with LAN.The client uses the wireless internet access for a period of time will break,Once again the normal,Repeated emergence.ping Lan IP normal.
Log:Apr 24 21:23:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 21:33:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 21:43:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 21:53:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 22:03:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 22:13:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 22:23:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
Apr 24 22:33:27   hostapd: wlan0: STA 00:25:22:32:50:ed WPA: group key handshake completed (RSN)
« Reply #24 on: April 24, 2012, 17:16:42 »
wjc007 *
Posts: 9

Every time WPA: group key handshake completed  The online game disconnection
« Reply #25 on: April 24, 2012, 17:54:23 »
Lennart Grahl ***
Posts: 153

Revision 506: I've added the possibility to change the wpa_group_rekey interval manually via config.xml.

You have to backup your configuration file, open it in an editor, then search for "</psk>" and add another line below:
<grouprekey>600</grouprekey>

Of course you can change the value to whatever value you'd like. The interval is specified in seconds. wjc007 in your case you probably want to set it to 0.
Save the file and then restore it in the webinterface.

Be aware that I wasn't able to test it with a wireless card so please provide me with some feedback.
« Last Edit: April 24, 2012, 17:59:18 by Lennart Grahl »
« Reply #26 on: April 25, 2012, 15:22:57 »
wjc007 *
Posts: 9

Thanks,Edit configuration file ,add to <grouprekey>0</grouprekey>
There are network disconnection phenomenon ,at intervals of 1hours.

« Reply #27 on: April 25, 2012, 19:42:58 »
Lennart Grahl ***
Posts: 153

Thanks,Edit configuration file ,add to <grouprekey>0</grouprekey>
There are network disconnection phenomenon ,at intervals of 1hours.

Anything in the log that could be related to your problem?
« Reply #28 on: April 26, 2012, 01:39:37 »
wjc007 *
Posts: 9

hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:13 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:13 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-00000015
Apr 26 07:29:13 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:13 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:17 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:19 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:19 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-00000016
Apr 26 07:29:19 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:19 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:23 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:24 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:24 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-00000017
Apr 26 07:29:24 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:24 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:33 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:34 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:34 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-00000018
Apr 26 07:29:34 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:34 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:35 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:36 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:36 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-00000019
Apr 26 07:29:36 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:36 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:37 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:38 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:38 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-0000001A
Apr 26 07:29:38 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:38 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:39 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:39 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:39 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-0000001B
Apr 26 07:29:39 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:39 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:43 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:44 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:44 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-0000001C
Apr 26 07:29:44 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:44 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:45 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:50 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:50 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-0000001D
Apr 26 07:29:50 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:50 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Apr 26 07:29:51 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: deassociated
Apr 26 07:29:51 hostapd: wlan0: STA 00:1f:3c:ad:85:0a IEEE 802.11: associated
Apr 26 07:29:51 hostapd: wlan0: STA 00:1f:3c:ad:85:0a RADIUS: starting accounting session 4F97CE28-0000001E
Apr 26 07:29:51 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: pairwise key handshake completed (WPA)
Apr 26 07:29:51 hostapd: wlan0: STA 00:1f:3c:ad:85:0a WPA: group key handshake completed (WPA)
Network disconnection no log.
« Reply #29 on: April 27, 2012, 14:32:21 »
wjc007 *
Posts: 9

Hello
  I am currently using 1.8.0b515,WAN interface Display errors,no In/out packets,MAC address is 363583 ,In/out errors  is 0/16805450 ,IPv4 gateway is Modem ,network normal .

« Last Edit: October 02, 2012, 04:01:57 by wjc007 »
 
Pages: 1 [2]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines