We recently bought 40 CPE2-12 we have over 100 Legacy DLB2112 in our network, we actually bought the units as soon as they came out with the thought that the units would have at least the same features the Legacy units had (except for AP specific options) but actually Its missing many many features that we consider as very important for a CPE, this are the ones i quickly noticed compared to the Legacy Unit:

HTTP Port,
Ping WatchDog,
Save\Reload Settings,
DMZ,
RADIUS Authentication,
Connecting profile SSID, and
QoS
Site Survey
SNMP

Also the Passphrase of the security mode is not hidden.

For us the most important ones are:

Ping WatchDog,
Save\Reload Settings,
Connecting profile SSID,
Site Survey, and
QoS

We currently have Firmware: WILI-S.WILISOC.v5.23.ar2316.DLB-CPE.20642.080822.164518
and Skin:  DLB-CPE 8.01.20427

Is there a way to get any of This features in the NEW CPE2-12 ?? I was reading the manual and saw that by using a Custom Skin we can Save\Reload settings and also Add\Remove Options from the GUI, is this correct? if so, how can i get information on how to set this up, which files to modify, etc.

 Thanks,

 Roberto Polanco

 

 

 

Hi Roberto,

The CPE devices have an 'Easy to Use' web interface that makes setting up a CPE device simple. :)

For more features you might want to load  the DLB AP 2i firmware, which is compatible with this board. It is more like theolder Deliberant products.

http://wiki.deliberant.com/index.php/DLB_AP_Configuration_Manual

For some of the features, I have comments:

• Ping Watchdog - not built into software, but if you are familiar with shell scripting this can be implemented (we have a sample script)
• RADIUS Authentication - Is available in expert mode
• Currently, there is no connecting profile.
  
• QOS - We have QOS in the form of WMM which automatically prioritizes traffic in 4 categories (Voice, Video, Best effort, and background)

The rest of the features are readily available in the AP 2i firmware.
Yes you can modify the skins on these devices, but I think the web interface on the AP 2i has most of what you're looking for. Maybe you can load that and we can go from there?

-Matt

 How about bandwidth control???

It is possible to setup bandwidth control... Here is an example on the CPE devices:

http://wiki.deliberant.com/index.php/DLB_CPE_Configuration_Manual#Bridge_Mode_2

-Matt

 Ahh ok. I've only had a chance to play with the AP-2i radios, which doesn't seem to have the bandwidth control feature in the firmware ( since its primarily an AP, I would guess)

 

I'm impressed at this point with the new radios, they seem to be fairly sensitive ( connected at this point on my desk to the AP 3/4 mile away thru a brick wall and many trees). Something I couldn't do with any of the legacy units, by the way.

The bandwidth control is also available in the AP products, it just hasn't been exposed in the web interface yet.

It is possible to configure the bandwidth control functions via expert mode, if you have an example of what you're trying to do, we can post a matching config snippet that should accomplish that.

That's a good thing about the new products, the functionality is endless (almost).  If you can't find how to do something with the web interface, it may be possible to do via the configuration file. If you have questions on how to accomplish something, just ask!

-Matt

I am preparing to deploy my first CPE2-12, and want to be able to save its config to a file, for future deployments.  And, one of the features I would like to enable is bandwidht control.

So it sounds link I need to flash the CPE with the AP 2i firmware, and then manually add in a snippet for bandwidth control, test it and then save the config file.  Could you please post a snippet which shows how to enable bandwdith control and specify upstream and downstream limits?  Is there a reference document for this file format?

Thanks,

-chip

Hi Chip,

You can flash the CPE-2's with the AP 2i (which also has client functionality). :)

But yes, to enable bandwidth control on the AP web interface, you will have to add the bandwidth control in expert mode. You can control bandwidth per interface, but it only effectively works on an interface's egress traffic. So in a CPE situation, usually upload traffic is controlled by manipulating bandwidth controls for the wireless interface (ath0), and download bandwidth is controlled by the wired interface (eth0).

So here's an example:

bandwidth.status=enabled                                                       
bandwidth.1.devname=ath0                                                       
bandwidth.1.speed=512                                                          
bandwidth.1.status=enabled                                                     
bandwidth.2.devname=eth0                                                       
bandwidth.2.speed=1024                                                         
bandwidth.2.status=enabled   

This will set your CPE's bandwidth to 512kbps upload, and 1024kbps download.

Also, to see a full list of configurationkeys you can look here:
http://wiligear.com/wiki/index.php/WILI-S_5.23_Reference_Manual#Static_Bandwidth_Control
(Since this is based on the wilibox software suite).

Hope that helps,

-Matt

 Why isn't there a Ping Watchdog available fromt he web interface?

What I mean by that, I know you can drop into the shell and do it, but why not have the feature via the Web UI?  That script does work fine, but I couldn't imagine it could be too tough to put in say an IP, interval, packets to send, packets acceptible to lose prior to an action, then an action ... such as "reboot" ... I think I saw somewhere where you may also be able to do an ath0 down/up to fix it too.

We are looking into it for future releases.

Caleb

Matt,

I flashed a CPE-2 with the AP firmware.  I noticed that the device kept its existing configuration.  In other words, it kept working, and things I configured with its CPE firmware showed up in the expert page's config file (including bandwidth control).

 However, the network configuration, including DHCP modes does not show up in the GUI (but is correctly shown in the config file)

 So, while the ocnfig file shows:

#
# Section: netconf
netconf.1.devname=ath0
netconf.1.ip=0.0.0.0
netconf.1.mode=wan
netconf.1.netmask=255.255.255.255
netconf.1.status=enabled
netconf.1.type=wireless
netconf.1.up=enabled

netconf.2.devname=eth0
netconf.2.ip=192.168.2.1
netconf.2.mode=lan
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.type=ethernet
netconf.2.up=enabled

netconf.status=enabled

AND

#
# Section: dhcpc
dhcpc.1.devname=ath0
dhcpc.1.status=enabled

dhcpc.status=enabled

#
# Section: dhcpd
dhcpd.1.devname=eth0
dhcpd.1.dns.1.server=192.168.2.1
dhcpd.1.dns.1.status=enabled

dhcpd.1.end=192.168.2.199
dhcpd.1.gateway=192.168.2.1
dhcpd.1.lease_time=43200
dhcpd.1.netmask=255.255.255.0
dhcpd.1.start=192.168.2.100
dhcpd.1.status=enabled

dhcpd.status=enabled

The Configuration / Network GUI page settings are blank (with the excption of):

 Operating Mode: Router Mode

WAN interface: eth0

DHCP mode: disable

WAN mode: Static IP

I tired the "Read active" and "Save" buttons on the expert page, but no change.

button the expert page,

Do I need to reset to factory defaults after I flash?  Or should the configurations be comapatable?

Are there synchronization issues if one changes things in the config file, then the GUI?   (Note that I did not change the config file in this case.)

Thanks,

-chip 

 

 

 

Hi Chip,

While those configuration options will still work, they may not be recognized in the AP web interface. The AP web interface uses extra 'fake' keys that help the web interface know exactly what is going on. The CPE does not add these fake keys in when configuring.

In other words, if you're going to be using the AP web configuration menus, I would recommend loading the AP image, resetting to defaults, then configuring.  Then everything should work ok.

Hope that helps...

-Matt