DD-WRT X86 Access Restrictions->Access Policy no Work

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> X86 based Hardware
Author Message
lovemygirl
DD-WRT Novice


Joined: 24 Aug 2016
Posts: 7

PostPosted: Tue Aug 30, 2016 15:26    Post subject: DD-WRT X86 Access Restrictions->Access Policy no Work Reply with quote
I set up the DD-WRT X86 virtual machine on Vmware 10, but the connection limit does not work, but set up in Oracle VirtualBox virtual machine, it works fine, I ask what is the solution? I can only understand a little English, please forgive me.

Vmware 10 DD-WRT X86
Access Restrictions->Access Policy time Not working

After the need to manually Apply Settings, working

But,reboot after Not working

Oracle Virtualbox VM Work
Sponsor
lovemygirl
DD-WRT Novice


Joined: 24 Aug 2016
Posts: 7

PostPosted: Tue Aug 30, 2016 15:49    Post subject: Reply with quote
This is youtube my test video link
https://youtu.be/0BiFIJgcZX8
BrainSlayer
Site Admin


Joined: 06 Jun 2006
Posts: 7038
Location: Dresden, Germany

PostPosted: Thu Sep 01, 2016 8:52    Post subject: Reply with quote
i need to know more about your setup. especially your wan / internet setup configuration. if i understand corrent, the same setup works on VirtualBox, but not on VMWare. correct?
_________________
"So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
lovemygirl
DD-WRT Novice


Joined: 24 Aug 2016
Posts: 7

PostPosted: Thu Sep 01, 2016 12:36    Post subject: Reply with quote
BrainSlayer wrote:
i need to know more about your setup. especially your wan / internet setup configuration. if i understand corrent, the same setup works on VirtualBox, but not on VMWare. correct?


Yes, I tested all possible settings, as a result, any DDWRT version is also tested, as in the case to the test I almost give up the DDWRT X86.
lovemygirl
DD-WRT Novice


Joined: 24 Aug 2016
Posts: 7

PostPosted: Thu Sep 01, 2016 12:48    Post subject: Reply with quote
2014 year to 2016 year (08-24-2016-r30471)

test Not Working

My Vmware ver 10.0 (Traditional Chinese Language)

HDD: VMware SATA/IDE 1GB
RAM: 256MB RAM
LAN1 (WAN): Host Mode
LAN2 (LAN): Bridged


lovemygirl
DD-WRT Novice


Joined: 24 Aug 2016
Posts: 7

PostPosted: Thu Sep 01, 2016 13:57    Post subject: Reply with quote
This is Syslog



2016-09-01 21:56:17 cron.info cron[3579]: (CRON) STARTUP (fork ok)\n
2016-09-01 21:56:35 user.warning igmpproxy[3580]: select() failure; Errno(4): Interrupted system call\n
2016-09-01 21:56:17 user.info : igmprt : multicast daemon successfully started\n
2016-09-01 21:56:17 user.info : cron : cron daemon successfully started\n
2016-09-01 21:56:17 user.info : klogd : klog daemon successfully started\n
2016-09-01 21:56:17 kernel.notice kernel: klogd started: BusyBox v1.24.2 (2016-08-24 14:46:25 CEST)\n
2016-09-01 21:56:17 user.info : wland : WLAN daemon successfully started\n
2016-09-01 21:56:17 user.info : syslogd : syslog daemon successfully started\n
2016-09-01 21:56:17 user.warning igmpproxy[3387]: select() failure; Errno(4): Interrupted system call\n
2016-09-01 21:56:17 user.info : igmprt : multicast daemon successfully stopped\n
2016-09-01 21:56:17 user.info : syslogd : syslog daemon successfully stopped\n
2016-09-01 21:56:17 kernel.notice kernel: klogd: exiting\n
2016-09-01 21:56:17 user.info : klogd : kernel log daemon successfully stopped\n
2016-09-01 21:56:17 user.info : wland : WLAN daemon successfully stopped\n
2016-09-01 21:56:17 user.info : vpn modules : vpn modules successfully unloaded\n
2016-09-01 21:56:16 kernel.emergency kernel: nvram_commit: 65536 bytes written\n
2016-09-01 21:56:16 kernel.emergency kernel: commit\n
2016-09-01 21:56:16 user.info : cron : cron daemon successfully stopped\n
2016-09-01 21:56:16 kernel.emergency kernel: nvram_commit: 65536 bytes written\n
2016-09-01 21:56:16 kernel.emergency kernel: commit\n
2016-09-01 21:56:12 kernel.emergency kernel: nvram_commit: 65536 bytes written\n
2016-09-01 21:56:12 kernel.emergency kernel: commit\n
2016-09-01 21:56:12 kernel.emergency kernel: nvram_commit: 65536 bytes written\n
2016-09-01 21:56:12 kernel.emergency kernel: commit\n
2016-09-01 21:55:45 user.info : udpxy : UDP-to-HTTP multicast traffic relay daemon stopped\n
2016-09-01 21:55:45 user.info : igmprt : multicast daemon successfully started\n
2016-09-01 21:55:45 user.info : dhcpfwd : dhcp forwarder daemon successfully started\n
2016-09-01 21:55:45 user.info : WAN is up. IP: 61.231.109.11\n
2016-09-01 21:55:45 user.info : wland : WLAN daemon successfully started\n
2016-09-01 21:55:45 daemon.info process_monitor[3380]: set timer: 3600 seconds, callback: ntp_main()\n
2016-09-01 21:55:45 daemon.debug process_monitor[3380]: We need to re-update after 3600 seconds\n
2016-09-01 21:55:45 user.info : wland : WLAN daemon successfully stopped\n
2016-09-01 21:55:45 user.info : process_monitor successfully started\n
2016-09-01 21:55:44 user.info : vpn modules : vpn modules successfully unloaded\n
2016-09-01 21:55:44 daemon.notice pppd[3295]: pppd 2.4.7 started by root, uid 0\n
2016-09-01 21:55:43 user.info : pppd : PPP daemon successfully stopped\n
2016-09-01 21:55:43 user.info : pppd : PPP daemon hanging, send SIGKILL\n
2016-09-01 21:55:41 kernel.info kernel: device br0 left promiscuous mode\n
2016-09-01 21:55:41 user.info : pppd : PPP daemon successfully stopped\n
2016-09-01 21:55:41 daemon.info mstpd: set_br_up: Set bridge br0 up\n
2016-09-01 21:55:41 daemon.info mstpd: set_br_up: br0 was up\n
2016-09-01 21:55:41 user.info : udpxy : UDP-to-HTTP multicast traffic relay daemon stopped\n
2016-09-01 21:55:41 kernel.info kernel: device br0 entered promiscuous mode\n
2016-09-01 21:55:41 daemon.info mstpd: set_br_up: Set bridge br0 up\n
2016-09-01 21:55:41 daemon.info mstpd: set_br_up: br0 was up\n
2016-09-01 21:55:41 daemon.info mstpd: set_br_up: Set bridge br0 up\n
2016-09-01 21:55:41 daemon.info mstpd: set_br_up: br0 was up\n
2016-09-01 21:55:32 kernel.info kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.\n
2016-09-01 21:55:30 kernel.info kernel: [ 8451.110000] br0: topology change detected, propagating\n
2016-09-01 21:55:30 kernel.info kernel: [ 8451.100000] br0: port 1(vlan1) received tcn bpdu\n
2016-09-01 21:55:29 kernel.info kernel: [ 8450.160000] br0: topology change detected, propagating\n
2016-09-01 21:55:29 kernel.info kernel: [ 8450.160000] br0: port 1(vlan1) neighbor 8000.00:24:a5:f0:13:a6 lost\n





2016-09-01 21:59:04 user.info : udpxy : UDP-to-HTTP multicast traffic relay daemon stopped\n
2016-09-01 21:59:04 user.info : igmprt : multicast daemon successfully started\n
2016-09-01 21:59:04 user.info : dhcpfwd : dhcp forwarder daemon successfully started\n
2016-09-01 21:59:04 daemon.info process_monitor[3377]: set timer: 3600 seconds, callback: ntp_main()\n
2016-09-01 21:59:04 daemon.debug process_monitor[3377]: We need to re-update after 3600 seconds\n
2016-09-01 21:59:04 user.info : WAN is up. IP: 61.231.112.109\n
2016-09-01 21:59:04 user.info : wland : WLAN daemon successfully started\n
2016-09-01 21:59:04 user.info : wland : WLAN daemon successfully stopped\n
2016-09-01 21:59:04 user.info : process_monitor successfully started\n
2016-09-01 21:59:04 user.info : vpn modules : vpn modules successfully unloaded\n
2016-09-01 21:59:03 daemon.notice pppd[3292]: pppd 2.4.7 started by root, uid 0\n
2016-09-01 21:59:03 user.info : pppd : PPP daemon successfully stopped\n
2016-09-01 21:59:03 user.info : pppd : PPP daemon hanging, send SIGKILL\n
2016-09-01 21:59:01 kernel.info kernel: device br0 left promiscuous mode\n
2016-09-01 21:59:01 user.info : pppd : PPP daemon successfully stopped\n
2016-09-01 21:59:01 daemon.info mstpd: set_br_up: Set bridge br0 up\n
2016-09-01 21:59:01 daemon.info mstpd: set_br_up: br0 was up\n
2016-09-01 21:59:01 user.info : udpxy : UDP-to-HTTP multicast traffic relay daemon stopped\n
2016-09-01 21:59:01 kernel.info kernel: device br0 entered promiscuous mode\n
2016-09-01 21:59:01 daemon.info mstpd: set_br_up: Set bridge br0 up\n
2016-09-01 21:59:01 daemon.info mstpd: set_br_up: br0 was up\n
2016-09-01 21:59:01 daemon.info mstpd: set_br_up: Set bridge br0 up\n
2016-09-01 21:59:01 daemon.info mstpd: set_br_up: br0 was up\n
2016-09-01 21:58:50 kernel.info kernel: [ 8651.110000] br0: topology change detected, propagating\n
2016-09-01 21:58:50 kernel.info kernel: [ 8651.100000] br0: port 1(vlan1) received tcn bpdu\n
2016-09-01 21:58:49 kernel.info kernel: [ 8650.160000] br0: topology change detected, propagating\n
2016-09-01 21:58:49 kernel.info kernel: [ 8650.160000] br0: port 1(vlan1) neighbor 8000.00:24:a5:f0:13:a6 lost\n
2016-09-01 21:58:19 kernel.info kernel: [ 8620.480000] br0: topology change detected, propagating\n
2016-09-01 21:58:19 kernel.info kernel: [ 8620.480000] br0: port 1(vlan1) neighbor 8000.00:0c:29:c0:54:12 lost\n
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> X86 based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum