1. Compile Barrier Breaker with patch fixed rxbuf_size issue:
https://gist.github.com/leleobhz/61cd38 ... 76c07dd4f4
The final image I used:
http://oli.denq.us/content/images/2015/ ... tfs.tar.gz
2. Create metarouter with 64M ram and 40000KB disk size for the virtualisation environment on a RB2011UiAS-2HnD .
3. Import and the image, and add 2 physical ports to the newly created virtual Openwrt:
- ether1 as wan port, which is connected to a optical broadband modem
- ether5 as lan port, which is connected to a downstream network device
- ether1 and ether5 does not belong to any bridge in host Router OS
- the configuration details for openwrt network:
4. The whole setup works! WAN is connected with pppoe link, and when the downstream router connected to ether5 gets IP through DHCP service on virtualized openwrt, it can connect to internet do all the things as expected.
Code: Select all
config interface 'lan' option ifname 'eth1' option type 'bridge' option proto 'static' option ipaddr '192.168.2.1' option netmask '255.255.255.0' option ip6assign '60' config interface 'wan' option ifname 'eth0' option proto 'pppoe' option username 'xxxxx' option password 'xxxx'
The problem is stability, after every around 1.5 hours, the whole routerboard rebooted:
The resource status with Router OS is some thing like below when openwrt is still running correctly:router was rebooted without proper shutdown by watchdog timer
The interesting thing is if the 2 assigned ports to metarouter openwrt are disabled, the stability will improve, so far more than 3 hours are observed without reboot. But that will make the virtualized openwrt meaningless.
Code: Select all
uptime: 1h22m44s version: 6.31 build-time: Aug/14/2015 15:42:51 free-memory: 27.3MiB total-memory: 128.0MiB cpu: MIPS 74Kc V4.12 cpu-count: 1 cpu-frequency: 650MHz cpu-load: 49% free-hdd-space: 61.2MiB total-hdd-space: 128.0MiB write-sect-since-reboot: 702 write-sect-total: 702 bad-blocks: 0% architecture-name: mipsbe board-name: RB2011UiAS-2HnD platform: MikroTik
I think this is clearly a bug for Router OS metarouter, which was discussed a lot I believe, but so far still no solution?