Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Help Please
#1
Can you guys tell me what wrong here:

SB5100MoD by ToM - Embedded Telnet Server

login:
password:
Welcome to the Broadcom CLI (command-line interpreter).
To access the native VxWorks shell, type 'shell'.
0x0000164e ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsSyncO
k: (CmDocsisCtlThread) downstream time sync acquired...
0x0000164e ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread:Big GrinsSyncOkRes
umeUsInit: (CmDocsisCtlThread) pre-REG upstream target case...starting initial
ranging.
Beginning initial ranging...
Using stored initial upstream power = 51.0 dBmV
0x0000164e ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsSyncO
k: (CmDocsisCtlThread) rx unexpected kDsSyncOk indication...
Not logging event ID 2223898630, control for level 7 is 0.
RNG-RSP Adj: tim=1934 power=1 freq=0 Stat=Continue
0x000018c4 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::ConfigStati
onMaint: (CmDocsisCtlThread)
config is kStationMaintenance mode.
RNG-RSP Adj: tim=0 power=1 freq=0 Stat=Continue
RNG-RSP Adj: tim=0 power=0 freq=0 Stat=Success
0x00002698 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::ConfigStati
onMaint: (CmDocsisCtlThread)
config is kPeriodicRanging mode.

******************************************
UPSTREAM STATUS
******************************************
Upstream Status = UP
Upstream Channel = 20
Upstream Frequency = 38800000 Hz
Upstream Power = 51 dBmV
Ranging SID = 0x1962
Upstream Symbol Rate = 2560000 sym/sec
******************************************

Starting IP Initialization with DHCP...
DHCPc: Waiting 1 seconds before sending Discover; client id htype=1, value=00:1
1:1a:22:46:3a
Not logging event ID 2223898629, control for level 7 is 0.
CM> DHCPc: Sending Discover packet; client id htype=1, value=00:XX:XX:XX:XX:XX
DHCPc: Received an Offer from DHCP server 00:XX:XX:XX:XX:XX(10.70.128.1); leas
e client id htype=1, value=00:XX:XX:XX:XX:XX
CM> DHCPc: Timed out waiting for offers for lease with client id htype=1, value
=00:XX:XX:XX:XX:XX
DHCPc: Sending Request packet; client id htype=1, value=00:XX:XX:XX:XX:XX
DHCPc: Received an Ack from DHCP server 00:XX:XX:XX:XX:XX (10.70.128.1); lease
client id htype=1, value=00:XX:XX:XX:XX:XX
Current IP address is default 169.0.0.1; removing existing route...
0x000032a0 ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::ConfigureLeaseImpl
: (IP Stack1 HalIf)
Configuring IP stack 1:
IP Address = 10.54.99.120
Subnet Mask = 255.255.224.0
Router = 10.54.96.1

DHCP completed successfully!

DHCP Settings:
Client Id = htype=1, value=00:XX:XX:XX:XX:XX
State = Bound (4)
Static Lease = false
AutoConfig Mode = IP, Subnet and Router
XID = 0x5a0d
Number of Tries = 0
Max Discover Tries = 6
Max Request Tries = 6
DHCP server MAC addr = 00:XX:XX:XX:XX:XX
My offered IP address = 10.54.99.120
(1) Subnet Mask = 255.255.224.0
(3) Router IP address = 10.54.96.1
(54) DHCP Server IP address = 24.29.137.56
(82) Relay Agent IP address = 10.70.128.1
TFTP Server IP address = 24.29.158.50
CM Configuration file = '?BBgdiTgAERoiRjoKNmN4@CjZjeLTek2EYlSm6_FIJvZVp
K8MSoxmZ'
(2) UTC Time Offset = -18000 seconds
(4) Time Server IP address = 24.29.158.50
(7) Log Server IP address = 24.29.99.57
(51) Lease time = 1121170 seconds
(58) T1 (renew) = 560585 seconds
(59) T2 (rebind) = 981023 seconds
Lease is infinite = false


CmSnmpAgent::IpAddressAcquiredEvent for SB5100 CM Agent
IP addr = 10.54.99.120
SB5100 CM Agent ConfigIp: Ip=10.54.99.120, Subnet=255.255.224.0, Gateway=10.54.9
6.1
CM> Starting Time Of Day...
0x00003692 ['CmDocsisIpThread' id=0x807c3b50] BcmDocsisTimeOfDayThread::SetTodSe
rverIpAddress: (Time Of Day Thread) ToD servers: 24.29.158.50
Connecting to ToD server 24.29.158.50...
Sending UDP ToD request to server...
Logging event: DHCP WARNING - Non-critical field invalid in response.
Not logging event ID 2223898627, control for level 7 is 0.
Waiting 2000 ms before trying this server again...
Logging event: ToD request sent- No Response received
Starting Tftp of configuration file...
Opening file '?BBgdiTgAERoiRjoKNmN4@CjZjeLTek2EYlSm6_FIJvZVpK8MSoxmZ' on 24.29.1
58.50...
tftpInit: Tftp outbound interface flag (1024)
Connected to 24.29.158.50 [69]
mode set to octet.
getting from 24.29.158.50:?BBgdiTgAERoiRjoKNmN4@CjZjeLTek2EYlSm6_FIJvZVpK8MSoxmZ
[octet]
tftpSend: Attempt #(1) Backoff (2) tickCount (1429) blkReply (1)
1.69.1.6.4.1.2.26 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.26 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.26 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.26 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.7.26 to 68.168.70.0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.8.26 to 255.255.254.0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.27 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.27 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.27 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.27 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.9.27 to 68.168.70.0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.10.27 to 255.255.254.0 OK.
99 TLV-11's OK.
MAX CPE per CM is being set to 2
Sending a REG-REQ to the CMTS...
* SB5100MoD Save cmConfig ?BBgdiTgAERoiRjoKNmN4@CjZjeLTek2EYlSm6_FIJvZVpK8MSox
mZ (3915 bytes) to RAM Memory
Tftp read ZERO bytes, may have reached end of file.
Config file was read! IP Initialization completed...
Set 1.3.6.1.2.1.69.1.2.1.2.16 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.3.16 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.4.16 to XXXXXXXXXXXXX.
Set 1.3.6.1.2.1.69.1.2.1.5.16 to 3 OK.
Set 1.3.6.1.2.1.69.1.2.1.6.16 to 40 00 OK.
Set 1.3.6.1.2.1.69.1.2.1.7.16 to 4 OK.
Set 1.3.6.1.2.1.69.1.2.1.2.18 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.3.18 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.4.18 to yZaK4E8l OK.
Set 1.3.6.1.2.1.69.1.2.1.5.18 to 2 OK.
Set 1.3.6.1.2.1.69.1.2.1.6.18 to 40 00 OK.
Set 1.3.6.1.2.1.69.1.2.1.7.18 to 4 OK.
Set 1.3.6.1.2.1.69.1.2.1.2.19 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.3.19 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.4.19 to 4lPH+OTIIBI43is OK.
Set 1.3.6.1.2.1.69.1.2.1.5.19 to 2 OK.
Set 1.3.6.1.2.1.69.1.2.1.6.19 to 40 00 OK.
Set 1.3.6.1.2.1.69.1.2.1.7.19 to 4 OK.
Set 1.3.6.1.2.1.69.1.2.1.2.20 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.3.20 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.2.1.4.20 to 9ZOuw1C4gA2UA1U OK.
Set 1.3.6.1.2.1.69.1.2.1.5.20 to 3 OK.
Set 1.3.6.1.2.1.69.1.2.1.6.20 to 40 00 OK.
Set 1.3.6.1.2.1.69.1.2.1.7.20 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.1.0 to 1 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.2.20 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.3.20 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.4.20 to 1 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.5.20 to 2048 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.2.22 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.3.22 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.4.22 to 1 OK.
Set 1.3.6.1.2.1.69.1.6.2.1.5.22 to 2054 OK.
Set 1.3.6.1.2.1.69.1.6.3.0 to 1 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.10 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.10 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.10 to 1 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.11.10 to 17 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.12.10 to 68 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.13.10 to 68 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.14.10 to 67 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.15.10 to 67 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.11 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.11 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.11 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.11 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.11.11 to 17 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.12.11 to 67 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.13.11 to 68 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.14.11 to 67 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.15.11 to 68 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.20 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.20 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.20 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.20 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.7.20 to 24.28.193.96 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.8.20 to 255.255.255.248 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.21 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.21 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.21 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.21 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.9.21 to 24.28.193.96 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.10.21 to 255.255.255.248 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.22 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.22 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.22 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.22 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.7.22 to 24.28.193.6 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.8.22 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.23 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.23 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.23 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.23 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.9.23 to 24.28.193.6 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.10.23 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.24 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.24 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.24 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.24 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.7.24 to 71.74.42.240 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.8.24 to 255.255.255.255 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.2.25 to 4 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.3.25 to 2 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.4.25 to 0 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.5.25 to 3 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.9.25 to 71.74.42.240 OK.
Set 1.3.6.1.2.1.69.1.6.4.1.10.25 to 255.255.255.255 OK.
Set 1.3.6.1.2.Not logging event ID 2223898626, control for level 7 is 0.
Received a REG-RSP message from the CMTS...
0x00003c00 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::RegRspMsgEv
ent: (CmDocsisCtlThread) We registered with a DOCSIS 1.1 config file!
Registration complete!
Process CVC
Co-signer CVC verified
CVC's validated
DOCSIS CoS/QoS rate shaping enable is now true
CmSnmpAgent::CmOperationalEvent for SB5100 CM Agent
CmSnmpAgent operating in 1.1 mode, including docsQos, excluding docsBpi
+++ No DH kickstart profiles or snmpCommunityTable entries installed.
We will operate in NMACCESS mode.
SB5100 CM Agent setting V1/V2 view to docsisNmAccessView
SB5100 CM Agent enabling management.
SB5100 CM Agent sending deferred traps...
Done w/ deferred traps.
SB5100 CPE Agent disabling management.
SB5100 CPE Agent defering traps.
SB5100 CPE Agent setting V1/V2 view to docsisNmAccessView
0x00003c5a ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaun
chBpkm: (CmDocsisCtlThread) BPKM enabled. starting BPKM key requests.
SB5100 CM Event Log sending deferred async messages...
Sending syslog message from IF 1 to 24.29.99.57:
<131> CABLEMODEM [DOCSIS]: <68000403> ToD request sent- No Response received
Done w/ deferred msgs
Logging event: Auth Reject - Permanent Authorization Failure
Sending syslog message from IF 1 to 24.29.99.57:
<131> CABLEMODEM [DOCSIS]: <66030108> Auth Reject - Permanent Authorization Fa
ilure MAC addr: 00 XX XX XX XX XX
CM> Connecting to ToD server 24.29.158.50...
Sending UDP ToD request to server...
CM> UTC returned by ToD server 3582315582; UTC offset -18000
Current system time -> MON JUL 08 18:39:42 2013

System start time -> MON JUL 08 18:39:27 2013

Time Of Day completed...
BcmSnmpAgent::SystemTimeChangeEvent for SB5100 CM Agent
BcmCmDocsisStatusEventCodes::kCmIsOperational
Not logging event ID 2223898625, control for level 7 is 0.
CM>
Reply
#2
Logging event: Auth Reject - Permanent Authorization Failure
Sending syslog message from IF 1 to 24.29.99.57:
<131> CABLEMODEM [DOCSIS]: <66030108> Auth Reject - Permanent Authorization Fa


fix this...
Reply
#3
no, this...


Logging event: Auth Reject - Permanent Authorization Failure
Sending syslog message from IF 1 to 24.29.99.57:
<131> CABLEMODEM [DOCSIS]: <66030108> Auth Reject - Permanent Authorization Fa
ilure MAC addr: 00 XX XX XX XX XX

The HFC MAC is banned
Knowledge=Power
Reply
#4
LOL

NO, Fix this first!

SB5100MoD


Make it this...

5101 Haxorware...


Just kidding. 5100 is getting along in years now, maybe you could try something a little more modern. Change is good!


Try playing around with a setup that isn't public for a change...do something off the path like oh, IDK, maybe play around with telnet a little...see what it does...

Just a thought!
Reply
#5
(09-07-2013, 04:08 AM)ABMJR Wrote: no, this...


Logging event: Auth Reject - Permanent Authorization Failure
Sending syslog message from IF 1 to 24.29.99.57:
<131> CABLEMODEM [DOCSIS]: <66030108> Auth Reject - Permanent Authorization Fa
ilure MAC addr: 00 XX XX XX XX XX

The HFC MAC is banned

Thank you. You confirmed what I thought.

(09-07-2013, 04:36 AM)southernyankey1970 Wrote: LOL

NO, Fix this first!

SB5100MoD


Make it this...

5101 Haxorware...


Just kidding. 5100 is getting along in years now, maybe you could try something a little more modern. Change is good!


Try playing around with a setup that isn't public for a change...do something off the path like oh, IDK, maybe play around with telnet a little...see what it does...

Just a thought!

Good one. Lol
Yeah, I know 5100 is getting old. I have 5101 haxoware and running good. I just get bored sometimes and I figured "Let me see if I can get the ole 5100 back up and running". I want to really learn and practice this so I have a better understanding. This way I can be better prepared for the upcoming security.
Yeah, Playing with telnet is my next step.
Reply
#6
Haxorware sb5101 mod fercsa whaever,are only interface gui nothing moore
Reply
#7
(09-07-2013, 03:11 PM)dragonlord7791 Wrote: Haxorware sb5101 mod fercsa whaever,are only interface gui nothing moore

Yeah, I understand that but then why is SB5101 with Hax better? The telnet commands are already set and easier to do certain functions easier, right? Is the SB5101 better? I thought I heard SB5100 has a better chip and tuner.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)