logo
guides : class 1 Billion 4.1.0.14a_PcB300c via USB (DLF and Batch)

Firmware upgrade - via USB + update.htm : Billion 4.1.0.14a_PcB300c

On ASR8400, 2MB (from Billion 4.1.0.9_PcB213)

 

1st Attempt

Had it set to the BT test login
Reset password

 

Other browser windows = Y
Email client = Y
Firewall = Y
Antivirus = Y
ADSL cable = Y

 

After clicking on the upload image button, the router prepares itself:

download prep

 

Then the box appears to enter the file's location

upgrade image

 

I browsed and located the file, then I clicked on 'Upload' - the browser progressed to the 'upstatus' page.

upstatus

 

There was a spike in the network activity, indicating the file had started uploading

network spike

 

Then there was just a little low level activity:

network low level

 

No change after 10 minutes so tried to cancel the download.
After another 5-10 minutes there was still no response and I could not login to the router.

I paper-clip reset for 20-30 seconds, then switched off for 5 minutes and then switched on. The router came back to life and
I could login again.

2nd Attempt

Still set to the BT test login
Still default password
Reset IP to 192.168.1.254, reset pool to: 192.168.1.1 to 192.168.1.15
Disabled & re-enabled USB connection to renew DHCP and get PC assigned new IP.
Pinged 192.168.1.254 to double check

Noticed there was still some low level network activity - dunno what from: perhaps some remnant of anti-virus or firewall? [This was probably the svchost part of Windows polling the router for UPnP data]

Changed host file.

 

Other browser windows = N
Email client = N
Firewall = N
Antivirus = N
ADSL cable = Y

 

After clicking on 'Upload', still got the constantly refreshing upstatus page access. After 25 minutes, still nothing, so time to cancel etc. Flits between upstatus and rstboot.

rstboot

 

To recover, I paper-clip reset for 20-30 seconds, then switched off for 5 minutes and then switched on.

Maybe it's just my setup, but I haven't been able to image upload since the safecom.cn_10-07-04 firmware. I had a break and
reset the IP to 10.0.0.2.



Batch file workaround

 

I gave up with the image upload - Using my DLF Manager I unpacked the 4.1.0.14a_PcB300c DLF and created a batch installer. Ran it, switched off for a bit, switched on and voila!

 

The router IP changed to 192.168.1.254 and the username was 'admin' and the password was 'password'. Logged in, changed the
PPP settings, reset to 10.0.0.X range, changed admin password and 'submit' and 'save & reboot'. After about a minute, I
closed the browser (since when you change the router's IP the browser cannot find the new one) then disabled/enabled the USB connection and logged in to 10.0.0.2 again.

I shall add to this page as I explore the interface, but from 1st appearances, it doesn't look that different from the Billion 4.1.0.9_PcB213 (apart from the colour scheme and altered pictures (e.g. top right).

homepage


 

Further testing & investigation

 

The full menu tree is as follows:

menu layout

 

Some of the pages have links to further pages which do not have entries in the left hand menu.

You must remember to submit before you change pages in the router (easy to forget).

 

One noticeable difference to other firmwares is the presence of more details (on the ADSL status) in the system log:

09/03/2004 14:55:31> Received time from Time Server 128.138.140.44
01/01/1970 00:00:16> PPP1 Session is up.
01/01/1970 00:00:16> DNS: Add IP address X.X.X.X (Auto discovered)
01/01/1970 00:00:16> DNS: Add IP address X.X.X.X (Auto discovered)
01/01/1970 00:00:15> No Static Session Information is defined.
01/01/1970 00:00:15> NAT/NAPT Session Start: interface ppp1, WAN IP is X.X.X.X
01/01/1970 00:00:15> PPP1: DNS Secondary IP address is X.X.X.X
01/01/1970 00:00:15> PPP1: DNS Primary IP address is X.X.X.X
01/01/1970 00:00:15> PPP1: PPP Gateway IP address is X.X.X.X
01/01/1970 00:00:15> PPP1: PPP IP address is X.X.X.X
01/01/1970 00:00:15> PPP1 CHAP Authentication success
01/01/1970 00:00:11> PPP1 PPPoA Connected
01/01/1970 00:00:11> ATM Tx Error Count: 0, Rx Error Count: 0
01/01/1970 00:00:11> u/s total bit capacity: 95bits, used: 95bits
01/01/1970 00:00:11> d/s total bit capacity: 3058bits, used: 296bits
01/01/1970 00:00:11> d/s Latency: FAST, u/s Latency: FAST
01/01/1970 00:00:11> d/s Data Rate: 1152kbps, u/s Data Rate: 288kbps
01/01/1970 00:00:11> d/s CRC Errors: 0, u/s CRC Errors: 0
01/01/1970 00:00:11> d/s Attenuation: 21.8dB, u/s Attenuation: 11.5dB
01/01/1970 00:00:11> d/s SNR: 39.4dB, u/s SNR: 31.0dB

01/01/1970 00:00:11> CO Vendor: TEXAS_INSTRUMENTS
01/01/1970 00:00:11> Max Tx Power: -38dBm/Hz
01/01/1970 00:00:11> Annex Mode: ANNEX_A
01/01/1970 00:00:11> Modulation: G.dmt
01/01/1970 00:00:11> ADSL connected
01/01/1970 00:00:11> ATM layer is up, cell delineation achieved
01/01/1970 00:00:11> ATM Connected
01/01/1970 00:00:00> CfgMgr: 'Washer.dlz' module loaded.
01/01/1970 00:00:00> CfgMgr: 'Shtm.dlz' module loaded.
01/01/1970 00:00:00> CfgMgr: 'Console.dlz' module loaded.
01/01/1970 00:00:00> Initialized DMZ host.
01/01/1970 00:00:00> Initialized Dynamic NAPT.
01/01/1970 00:00:00> ATM: Setting up vcc0, VPI=0, VCI=38
01/01/1970 00:00:00> ATM: Detected
01/01/1970 00:00:00> Ethernet Device 0 Detected

 

Some firewall tests...

The packet filtering is similar to the policies in the Origo firmwares.

E.g. Entering 21 in the destination 'to' port, automatically puts 21 in the 'from' port (for an inbound policy)

packet filtering

 

To change this so packets from any port going to 21 are blocked, you need to enter 0 as the from port - which the router changes to '*'

using asterisk

 

Using an incoming to block all packets going to port 21 (as above) causes all network activity (on all the ports) to stop.

 

The URL Blocking seems to work well

See this page: URL Blocking Tests

 

There is also the Bridge Filtering in the firewall which is similar to the 'Access Control List' idea:

bridge filtering

 

Other pages...

misc config

 

The DHCP Relay options have moved from the Misc page to the LAN Config page:

lan config

 

UPnP

 

When using MSN Messenger 6.2, there are entries like this in the log:

09/03/2004 15:02:22> UPnP Action:DeletePortMapping State:Success. TCP-port:14872 Closed!
09/03/2004 15:02:22> UPnP Action:AddPortMapping State:Success. TCP-port:14872 Opened!

 

Also Intel's UPnP Device Spy and Sniffer pick up UPnP options and activity (when it's enabled on the PC and Router):

upnp devices

 

The rest of the pages appear to be the same as the Billion 4.1.0.9_PcB213

system gateway config

diagnostic

RouterTech RSS feed

Board statistics
admin 20/08/2017 04:53 AM
No Items Available
20/08/2017 05:53 AM

Hosted by Kieran O'Shea