You need to add a statement to explicitly allow those prefixes after denying the default-route, so the final prefix-list becomes:
ip prefix-list no-default-route seq 5 deny 0.0.0.0/0
ip prefix-list no-default-route seq 10 permit 0.0.0.0/0 le 32
From your comments I understand you want to log into your Cisco Unity Express (CUE) via CLI session to do password recovery.
Next is a sample configuration for NME with CUE:
!
interface GigabitEthernet0/0
description LAN
ip address 10.10.10.5 255.255.255.0
duplex auto
speed auto
media-type rj45
!
!
!
interface Integrated-Service-Engine2/0
ip unnumbered GigabitEthernet0/0
service-module ip address 10.10.10.10 255.255.255.0
!Application: CUE Running on NME
service-module ip default-gateway 10.10.10.1
no keepalive
!
!
ip route 10.10.10.10 255.255.255.255 Integrated-Service-Engine2/0
!
You can access router´s CLI in 10.10.10.5 and CUE GUI in 10.10.10.10. Also, to log into CUE CLI you can do it from router CLI by running the following command:
router#service-module Integrated-Service-Engine 2/0 session
Trying 10.10.10.10, 2130 ... Open
From your comments I think you are reaching this point. Once there, press enter twice and you should get the the CUE prompt:
router#service-module Integrated-Service-Engine 2/0 session
Trying 10.10.10.10, 2130 ... Open
UnityExpress#
UnityExpress#
UnityExpress#
Just in case you need it, the process to do password reset in CUE GUI is documented here:
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unity-express/64234-cue-gui-pw.html
In brief, you have to create a new user, assign a password to it and add this user to group "Administrators", using the following commands:
UnityExpress>
UnityExpress>user Administrator create
UnityExpress>
UnityExpress>user Administrator group Administrators
UnityExpress>
UnityExpress>user Administrator password cisco
UnityExpress>
Best Answer
To name a few things: development, maintenance testing and support of software and hardware and of course: marketing and profit. Also, these vendors use dedicated ASICs so packet forwarding (amongst other things) are done in hardware instead of software. Basically, you buy a box which is optimized for one task: routing, which means all code and hardware has been tested for that.
Software routers are often ok, especially if you don't have a large budget or just need to build a lab setup. However, if you run into problems there's a chance you're either on your own figuring out if it's the routing software, your hardware, the kernel or something else. I'm not saying this is a bad thing (some of these projects have many active users), it's just something to consider.
A full BGP feed is almost 450K IPv4 prefixes by now by the way, and nearly 13K IPv6. If I'd be building a software router, I'd do some research on which NICs to use and how to optimize them and put a lot more than 2G of RAM in the box.