Memory policy: ECC disabled, Data cache writealloc Linux version 2.6.34.10_sd5115v100_wr4.3 (gcc version 4.4.6 (GCC) ) #1 SMP Tue Apr 22 18:04:ĬPU: ARMv7 Processor revision 1 (ARMv7), cr=10c53c7fĬPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Image Type: ARM Linux Kernel Image (uncompressed) # Booting kernel from Legacy Image at 85c00054. MAGIC1: 0x0, MAGIC2: 0x0, the magic is error!!! Slave_paramA in flash, CRC:0xa3c1ca20, Magic1:0x0, Magic2:0x0, count:0, CommitedArea:0x0, Active:0x0, RunFlag:0x0 Nand(Hardware): Block:128KB Page:2KB Chip:128MB*1 OOB:64B ECC:4Bytes One of the advantages of fiber is that it it allows much higher upstream bandwidth than the typically way more asymmetric XDSL or DOCSIS links.Use the main slave_param area from flash, the RAM data is not OK!!! (But note for many internet flows the bottleneck will be completely outside of your control, so in reality you will have trouble statically accounting for anything more remote than your direct access link, as those links are typically shared between users and over-subscribed and hence do not guarantee fixed bandwidths per user).īTW, 20/1? That seems quite "cruel" from your ISP to not go at least 20/10. But for the overhead accounting you really only need to model/specify the overhead applicable at the bottleneck link independent on all the links before and after. Yes, as far as I can tell you are running a dualNAT setup there. My question is… Im using a DIR-835 behind a Huawei HG8245H which i cannot put to bridge mode (because of my ISP settings, but is using PPPoE) though i have the huawei modem in DMZ, i believe im dual natting or at least adding a hop to the network… should i increase the packet overhead or keep these settings?
0 kommentar(er)
