Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Trouble connecting to Internet- DPC2100R2
#21
Quote:You are in BPI + with tftp enforce now. So you cannot anymore force your own faster config. I believe what you have now is just your normal tier that is sub to that modem mac address, if it's even your own sub. If you want to have faster speed , then you need to pay more to have faster speed or you need to look for faster prov cert not from your node but near you.

Ok so you mean to say that the certs are assigned with respect to the speed ..If I need to go for 21Mbps I need to take a cert from someone who has 21Mbps ...right ?? .. ...please do let me know more about these incase you find something more...

I also need to take into consideration about what Drew and ABMJR thinking about I have to work on these too

anyways my sincere thanks to all who are contributing to my help ...I will keep trying..so let me know
Reply
#22
Certificates are associated with an HFC MAC address. All they are are Verisigns Root Server validating that the HFC MAC you have has its correct "born-at-birth" Verisign made certificates. in the old days, users could just "sniff" a network and grab some HFC MACs that were buzzing along between the cable modem and the CMTS..The problem was, when BPI +, and the "+" is critical here, was enforced, these HFC MAC's were asked to send their certificates which were made at the time the modem had its non-vol injected at the factory. When you sniff for MACs you dont get these specific certificates, thus when the CMTS asks for them, the HFC MAC will fail verification as the certs that are in the one you have do not match since you used a MAC you sniffed on the network...

Kapisch?
Knowledge=Power
Reply
#23
(24-01-2012, 10:26 PM)ABMJR Wrote: Certificates are associated with an HFC MAC address. All they are are Verisigns Root Server validating that the HFC MAC you have has its correct "born-at-birth" Verisign made certificates. in the old days, users could just "sniff" a network and grab some HFC MACs that were buzzing along between the cable modem and the CMTS..The problem was, when BPI +, and the "+" is critical here, was enforced, these HFC MAC's were asked to send their certificates which were made at the time the modem had its non-vol injected at the factory. When you sniff for MACs you dont get these specific certificates, thus when the CMTS asks for them, the HFC MAC will fail verification as the certs that are in the one you have do not match since you used a MAC you sniffed on the network...

Kapisch?

Hello ABMJR thank U very much for this great explanation ... So I have to find a way out and I am working on it ... Its my stupidity and I regret I made a sub(flashed haxor )without thinking about the certs and now I regret ... So I now have a sub without any certs Sad

And self signed certs are of no use ..its illogical to think about existence of any cert editors or using a cert of different modem and then trying to change the values of the MAC it contains to the one of sub ..it would be encrypted by some algorithm ....

Damm AngryHuh..I should have been more careful Half knowledge is always dangerous

I do kapisch ..
I am working hard for alternatives ..so lets hope.....my sincere thanks again
Reply
#24
Hello Drewmerc & ABMJR ..I tried uploading the extracted certs from the original modem to the sub...but inspite of this I couldn't manage to connect any more ideas apart from the above posts thanks and heres the log just for your reference thanks again

Code:
CM>
CM> Attempting Downstream FEC lock @ freq= 567000000 Hz, QAM256
0x000b2ca0 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain:  (DHCP Server T
hread) Callback request expired:
timerDuration secs = 1
current time secs = 732
elapsed time secs = 1
CM> Attempting Downstream FEC lock @ freq= 573000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 579000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 585000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 591000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 597000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 603000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 609000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 615000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 621000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 627000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 633000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 639000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 645000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 651000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 657000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 663000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 669000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 675000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 681000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 687000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 693000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 699000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 705000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 711000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 717000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 723000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 729000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 735000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 741000000 Hz, QAM256
0x000b57ac [DHCP Server Thread] BcmDhcpServerThread::ThreadMain:  (DHCP Server T
hread) Callback request expired:
timerDuration secs = 1
current time secs = 743
elapsed time secs = 1
CM> Attempting Downstream FEC lock @ freq= 747000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 753000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 759000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 765000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 771000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 777000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 783000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 789000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 795000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 801000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 807000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 813000000 Hz, QAM256
Favorite[0].freq = 441000000
Attempting Downstream FEC lock @ freq= 441000000 Hz, QAM64/256
0x000b6dd2 [CmDocsisCtlThread] BcmCmDocsisCtlThread::StartUsInit:  (CmDocsisCtlT
hread) Locked on the downstream.  Waiting for UCDs...

******************************************
            DOWNSTREAM STATUS
******************************************
  Tuner Frequency = 441000000 Hz
   Carrier Offset = -3 Hz
      Symbol rate = 5360537 sym/sec
              SNR = 37 dB
         QAM Mode = QAM256
        Tuner AGC = 0xfff00000
           IF AGC = 0x100250d4
      Power Level = 20 dB
              QAM = LOCKED
              FEC = LOCKED
******************************************

CM> Selecting UCD for Us Channel 4

0x000b7764 [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync:  (
CmDocsisCtlThread) starting ds time sync acquisition...
0x000b79e4 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk:  (CmDocsisCtl
Thread) downstream time sync acquired...
0x000b79e4 [CmDocsisCtlThread] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit:  (CmD
ocsisCtlThread) pre-REG upstream target case...starting initial ranging.
Beginning initial ranging...
Using stored initial upstream power = 30.0 dBmV
0x000b79ee [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk:  (CmDocsisCtl
Thread) rx unexpected kDsSyncOk indication...
Not logging event ID 2307948724, control  for level 7 is 0.
RNG-RSP  Adj: tim=1435 power=0 freq=0  Stat=Continue
0x000b7afc [CmDocsisCtlThread] BcmCmDocsisCtlThread::RngRspMsgEvent:  (CmDocsisC
tlThread) WARNING - Calling PreRegUsChanChange!  Appendix H stuff...
Deleting DOCSIS 1.0 CoS Settings for SID 0
0x000b7bc4 [CmDocsisCtlThread] BcmDocsisCmHalIf::DeleteAllServiceFlows:  (DOCSIS
CableModem HalIf) Deleting all Upstream and Downstream Service Flows, along wit
h associated Classifiers and PHS rules...
Stopping DHCP/ToD/TFTP (client requested)...
  DefaultSnmpAgentClass::RestartPendingEvent for SB5102 CM Agent w/ BRCM Factory
Support
SB5102 CM Agent w/ BRCM Factory Support resetting to default state.
SB5102 CM Agent w/ BRCM Factory Support destroying users...
Pausing trap thread
SB5102 CM Agent w/ BRCM Factory Support destroying notifies...
Resuming trap thread
SB5102 CM Agent w/ BRCM Factory Support destroying views...
SB5102 CM Agent w/ BRCM Factory Support sending deferred traps...
Done w/ deferred traps.
SB5102 CM Event Log w/ BRCM Factory Support sending deferred async messages...
Done w/ deferred msgs
SB5102 CM Agent w/ BRCM Factory Support defering traps.
SB5102 CM Agent w/ BRCM Factory Support setting V1/V2 view to unrestricted
SB5102 CPE Agent w/ BRCM Factory Support setting V1/V2 view to docsisCpeView
Non-Vol Settings successfully written to the device.
0x000b7bd8 [CmDocsisCtlThread] BcmCmDocsisCtlThread::ResetRngState:  (CmDocsisCt
lThread)

@@@@@ In ResetRngState, fRemainingInitRngPowerSteps 17
NonVolDeviceDriver::NonVolDriverWrite:  WARNING - Current segment size < buffer
size!  Increasing the segment size!
CM> 0x000b82b8 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain:  (DHCP Serv
er Thread) Callback request expired:
timerDuration secs = 1
current time secs = 754
elapsed time secs = 1
CM> Selecting UCD for Us Channel 3

0x000b86fa [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync:  (
CmDocsisCtlThread) starting ds time sync acquisition...
0x000b8984 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk:  (CmDocsisCtl
Thread) downstream time sync acquired...
0x000b8984 [CmDocsisCtlThread] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit:  (CmD
ocsisCtlThread) pre-REG upstream target case...starting initial ranging.
Beginning initial ranging...
Using stored initial upstream power = 30.0 dBmV
0x000b8984 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk:  (CmDocsisCtl
Thread) rx unexpected kDsSyncOk indication...
Not logging event ID 2307948724, control  for level 7 is 0.
RNG-RSP  Adj: tim=1946 power=0 freq=0  Stat=Continue
RNG-RSP  Adj: tim=0 power=0 freq=0  Stat=Success

******************************************
            UPSTREAM STATUS
******************************************
       Upstream Status = UP
      Upstream Channel = 3
    Upstream Frequency = 38000000 Hz
        Upstream Power = 30 dBmV
           Ranging SID = 0x367
  Upstream Symbol Rate = 1280000 sym/sec
******************************************

Starting IP Initialization with DHCP...
DHCPc:  Waiting 4 seconds before sending Discover; client id htype=1, value= aa:bb:cc:dd:ee:ff
Not logging event ID 2307948624, control  for level 7 is 0.
CM> DHCPc:  Sending Discover packet; client id htype=1, value=aa:bb:cc:dd:ee:ff
DHCPc:  Received an Offer from DHCP server ww:ee:rr:tt:yy:uu (io:lm:0.1); lease
client id htype=1, value=aa:bb:cc:dd:ee:ff
CM> DHCPc:  Timed out waiting for offers for lease with client id htype=1, value
=aa:bb:cc:dd:ee:ff
DHCPc:  Sending Request packet; client id htype=1, value=aa:bb:cc:dd:ee:ff
DHCPc:  Received an Ack from DHCP server ww:ee:rr:tt:yy:uu (io:lm:0.1); lease c
lient id htype=1, value=aa:bb:cc:dd:ee:ff
Current IP address is default 0.0.0.0.
0x000ba694 [DHCP Client Thread] BcmEcosIpHalIf::ConfigureLeaseImpl:  (IP Stack1
HalIf)
Configuring IP stack 1:
  IP Address = io:lm:ol:pp(primary IP address)
   Subnet Mask = loi:ujh:tyg:uuj
   Router = io:lm:0.1
   IsPrimaryInterface = 1

ARPing for default GW IP = io:lm:0.1
MAC = ww:ee:rr:tt:yy:uu
DHCP completed successfully!

DHCP Settings:
                     Client Id = htype=1, value=aa:bb:cc:dd:ee:ff
                         State = Renewing (5)
                  Static Lease = 0
               AutoConfig Mode = IP, Subnet and Router
                           XID = 0x7b05e3d3
               Number of Tries = 0
            Max Discover Tries = 6
             Max Request Tries = 6
          DHCP server MAC addr = ww:ee:rr:tt:yy:uu
                   Ignore NAKs = 0
         My offered IP address = io:lm:ol:pp(primary IP address)
               (1) Subnet Mask = loi:ujh:tyg:uuj
         (3) Router IP address = io:lm:0.1
   (54) DHCP Server IP address = km:ki:ju:oi
   (82) Relay Agent IP address = io:lm:0.1
        TFTP Server IP address = km:ki:ju:oi
         CM Configuration file = '~wajd8382hfasjdYuhj8hhkjsdfk8hJKHJSHKDF7989jhsjhjh+SK'
           (2) UTC Time Offset = 19800 seconds
    (4) Time Server IP address = km:ki:ju:oi
        (6) Domain Name Server = km:ki:ju:ox; km:ki:ju:ot
     (7) Log Server IP address = km:ki:ju:oi
               (51) Lease time = 604800 seconds
               (58) T1 (renew) = 302400 seconds
              (59) T2 (rebind) = 529200 seconds
             Lease is infinite = 0


SB5102 CM Agent w/ BRCM Factory Support IpStackEvent: Ip=AZX.DEF.RFT.JUI, Subnet=255
.255.0.0, Gateway=io:lm:0.1
  CmSnmpAgent::IpAddressAcquiredEvent for SB5102 CM Agent w/ BRCM Factory Suppor
t
    IP addr = AZX.DEF.RFT.JUI
Starting Time Of Day...
0x000ba748 [CmDocsisIpThread] BcmDocsisTimeOfDayThread::SetTodServerIpAddress:
(Time Of Day Thread) ToD servers:  km:ki:ju:oi
Connecting to ToD server km:ki:ju:oi...
Sending UDP ToD request to server...
SNMP Agent Binding to AZX.DEF.RFT.JUI:225
Not logging event ID 2291949724, control  for level 7 is 0.
CM> UTC returned by ToD server 3536754907; UTC offset 19800
Current system time -> Sat Jan 28 21:25:07 2012

System start time -> Sat Jan 28 21:12:24 2012

Starting Tftp of configuration file...
Opening file '~ wajd8382hfasjdYuhj8hhkjsdfk8hJKHJSHKDF7989jhsjhjh+SK'' on rf.er.tgy.kio
0 for reading...
tftp-enforce bypass is using km:ki:ju:oi:~ wajd8382hfasjdYuhj8hhkjsdfk8hJKHJSHKDF7989jhsjhjh+SK'
Initiating fake TFTP Get (tftp-enforce bypass)
Bypass succeeded.File was 60 bytes
TFTPD Started
CM> Forcing Config TFTP IP to 127.0.0.1
Forcing Config File name to ~wjsdf887jhJHSKD+SDHFKJH8wasdhfhhjahskdfjaskdlfj
TFTPD received 1 from AZX.DEF.RFT.JUI:1119
0x000baf40 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain:  (DHCP Server T
hread) Callback request expired:
timerDuration secs = 1
current time secs = 765
elapsed time secs = 1
CM> 0x000bb1b6 [CmDocsisIpThread] Tftp Client::GetReply:  (Tftp Client) Timed ou
t on socket select!
0x000bb1b6 [CmDocsisIpThread] Tftp Client::Send:  (Tftp Client) Attempt #(1) Bac
koff (2) Exp Block #(1) Last Block #(0) Recv'd Block #(0)
CM> 0x000bc156 [CmDocsisIpThread] Tftp Client::GetReply:  (Tftp Client) Timed ou
t on socket select!
0x000bc156 [CmDocsisIpThread] Tftp Client::Send:  (Tftp Client) Attempt #(2) Bac
koff (4) Exp Block #(1) Last Block #(0) Recv'd Block #(0)
CM> 0x000bda4c [DHCP Server Thread] BcmDhcpServerThread::ThreadMain:  (DHCP Serv
er Thread) Callback request expired:
timerDuration secs = 1
current time secs = 776
elapsed time secs = 1
CM> 0x000be096 [CmDocsisIpThread] Tftp Client::GetReply:  (Tftp Client) Timed ou
t on socket select!
0x000be096 [CmDocsisIpThread] Tftp Client::Send:  (Tftp Client) Attempt #(3) Bac
koff (8) Exp Block #(1) Last Block #(0) Recv'd Block #(0)
CM>
Reply
#25
stop forcing a config
__________________________________________________________________________________
******new discord chat linkĀ https://discord.gg/5BQQbsb*******
Reply
#26
(30-01-2012, 05:32 PM)drewmerc Wrote: stop forcing a config

Hello Drewmerc I am not forcing a config ..I am autoserveing the config file ..I don't know what Ip address to give for forcing a config ..if you would ask to think then I would insert 192.168.100.1 since the config file should be taken from the box itself ....anyways I am not forcing and since you are against it i will not force a config in this scenario.

If I don't autoserve the config ..it takes the default speed and its damm slow!!

any other method to this like logging into telnet to change speeds but thats absurd bcoz either way using GUI or telnet it should work

....sorry if I have misunderstood the reply given by you and I have attached the shot just to let you know that the names of certs that I uploaded aren't shown against the labels under BASELINE PRIVACY ..is this normal/ok after uploading the respective certs or am I missing something...thanks


Attached Files Thumbnail(s)
   
Reply
#27
well autoserving or forcing (same damn thing in my head) but you have to stop it as you'll never get online like that as it's very easy for your isp to block and it looks like that is what they have done

what you need are better certs (by better i mean certs that get a faster provisioned config)
__________________________________________________________________________________
******new discord chat linkĀ https://discord.gg/5BQQbsb*******
Reply
#28
(30-01-2012, 06:44 PM)drewmerc Wrote: well autoserving or forcing (same damn thing in my head) but you have to stop it as you'll never get online like that as it's very easy for your isp to block and it looks like that is what they have done

what you need are better certs (by better i mean certs that get a faster provisioned config)

Exactly ..the moment I delete haxorwre.cfg the modem goes online with the default speed ....so this is crux of it.... Any ideas of how to get certs ...any softwares which can grab them off from some other box. ...sniffers?? I don't think so such softwares exist since BPI+ is now forced ...

I am thinking about these provisioned certs ...some certs are specific to each box and some are independent right?? is this what you mean to say ??
so which certs do I need to look for ??because some certs would contain the MAC for a particular box!!!

please let me know thanks again
Reply
#29
sb5100 certs will work with sb5101 and dpc2100r2. Just look at the flash chipset it used. LIke BCM3348 chip will work with BCM3349.
Reply
#30
(30-01-2012, 09:21 PM)carlos305 Wrote: sb5100 certs will work with sb5101 and dpc2100r2. Just look at the flash chipset it used. LIke BCM3348 chip will work with BCM3349.

Both have different mini OS's running.

Taking certificates from a working 5100 and using them on a 5101 will only work if that NODE is white listed for the HFC MAC and certs. 18 months ago, maybe, Yes, it could be done. Not anymore.Most NODES are closed...especially ones in high TOS areas...

And, I can say, clone detection is the number # 1 priority, as most of you talk about it and since the ISP's read here, they see where to move to next. Much of the previous areas that had a high TOS, have clone detection enabled. And , it seems to work quite well. Dont be fooled by anyone that tells you otherwise.

Knowledge=Power
Reply


Forum Jump:


Users browsing this thread: 5 Guest(s)