Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 2 3 [4]

Author Topic: Serving (slightly) better stats directly from Zyxel modems  (Read 11131 times)

johnson

  • Reg Member
  • ***
  • Posts: 838
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #45 on: March 17, 2020, 03:45:35 AM »

So I had a play and cant get a zyxel accessible from a remote IP at all myself.

I'm thinking its probably due to a modem mode zyxel not having a default gateway etc, no access to outside of the lan.

Will fiddle more tomorrow.
Logged

hacktrix2006

  • Reg Member
  • ***
  • Posts: 305
    • xDSL Stats:
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #46 on: March 17, 2020, 03:46:23 AM »

Thanks bud, setting up wireguard for now though.

Sent from my SNE-LX1 using Tapatalk

Logged

johnson

  • Reg Member
  • ***
  • Posts: 838
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #47 on: March 17, 2020, 03:49:38 AM »

Thanks bud, setting up wireguard for now though.

Will find a more optimal solution to occasional remote access to the modem, but having a wireguard setup to remote into your network from any location is never a bad thing!  :D
Logged

hacktrix2006

  • Reg Member
  • ***
  • Posts: 305
    • xDSL Stats:
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #48 on: March 17, 2020, 03:54:49 AM »

Will find a more optimal solution to occasional remote access to the modem, but having a wireguard setup to remote into your network from any location is never a bad thing!  :D
That is very true, however thank you for your time and assistance. Will let you get back to what you was doing.

Update: I tried Wireguard and although I could pull up the router WebGUI I couldn't pull up the modem WebGUI so really stumped.

Sent from my SNE-LX1 using Tapatalk
« Last Edit: March 17, 2020, 01:41:57 PM by hacktrix2006 »
Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #49 on: March 17, 2020, 05:46:16 PM »

Sincerest apology if you know all this already: Being in the same IP address range doesn’t mean you’re automatically in the same subnet - definition = “broadcast domain”. In my case the main LAN broadcast domain has an 81.187.x.y public/global/routable address in a /26 and each modem’s admin i/f lives in its own broadcast domain at 192.168.n.1 where n=1,2,3,4 is the nth modem (I have four modems). So that’s 1+4=5 broadcast domains=5 subsets, and in my case they are all distinct non-overlapping address ranges, but that’s just coincidental, it’s down to how I configured the modems.
Logged

hacktrix2006

  • Reg Member
  • ***
  • Posts: 305
    • xDSL Stats:
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #50 on: March 17, 2020, 05:51:57 PM »

Sincerest apology if you know all this already: Being in the same IP address range doesn’t mean you’re automatically in the same subnet - definition = “broadcast domain”. In my case the main LAN broadcast domain has an 81.187.x.y public/global/routable address in a /26 and each modem’s admin i/f lives in its own broadcast domain at 192.168.n.1 where n=1,2,3,4 is the nth modem (I have four modems). So that’s 1+4=5 broadcast domains=5 subsets, and in my case they are all distinct non-overlapping address ranges, but that’s just coincidental, it’s down to how I configured the modems.
It's always a great thing to relearn so no need to apologise beside it might help others.

However both modem and router are in same ip range of 192.168.1.0/32 I have even tried 192.168.1.0/24 however It did just remind me my Guest network has been setup on another range with firewall rules set to block WebGUI access and that's on the same vlan going to wan.

Sent from my SNE-LX1 using Tapatalk

Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #51 on: March 17, 2020, 06:07:46 PM »

I don’t understand your comment about "/32". That’s not large enough to have two IP addresses in it. Surely the modem and the router have to have two distinct IP addresses in their subnet? How does the modem manage if an incoming packet has src_address==dest_address, as when it replies to incoming packets it will be replying to itself? So I don’t see how the modem can be in a subnet that is /32. Your main LAN will typically be in a /24 or /16 if it’s in the usual home user setup with RFC1918 NAT-ed IP addresses?

Each of my modems lives in its own /24, as it happens, and in each subnet the modem is 192.168.n.1 and the router is 192.168.n.254.
Logged

hacktrix2006

  • Reg Member
  • ***
  • Posts: 305
    • xDSL Stats:
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #52 on: March 17, 2020, 06:18:04 PM »

I have Modem on 192.168.1.1 /255.255.255.0 and router on 192.168.1.3 /255.255.255.0 with guest network on 10.0.1.1 / 255.255.0.0 .

Guest network and normal network are on same vlan however guest network is isolated from the main network via firewall rules so they can't access webgui's or main network systems.

Hopefully this helps clear things up.

Sent from my SNE-LX1 using Tapatalk

Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #53 on: March 17, 2020, 06:42:25 PM »

Right. Some confusion earlier then, as you have a /24 there given it is 255.255.255.0, not a /32.
Logged

hacktrix2006

  • Reg Member
  • ***
  • Posts: 305
    • xDSL Stats:
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #54 on: March 17, 2020, 06:43:56 PM »

Sorry about that networking can be confusing at times lol. Hold up I had wireguard setup up to /32 and not /24 so that might be why it didn't work with wireguard lol. Will mess again later thanks for your time.

Sent from my SNE-LX1 using Tapatalk

Logged

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #55 on: May 12, 2020, 05:23:57 PM »

Question: on the CRC and FEC const vs time graphs, what are the units on the verticaly axis? I have modem #4 running very very slowly, with a lot of noise and the downstream CRC count is high compared to the other modems. The CRC rate figure shown on the y axis is the count CRC of corrected errors[?] per unit what time[?]

It is a still a new performance nightmare at the moment. The downstream SNRM was 2.5 dB and I forced a resync which brought the d/s SNRM up to 3.1dB. The downstream rate is even slower now, with a downstream sync rate below 2.5Mbps, whereas it was  ~2.9 Mbps before, and in total I have lost about 0.8-1.0Mbps total effective download rate from speed tests with speedtester2.aa.net.uk compared to what it was like a couple of months ago.

Live sync rates:
  #1: down 2807 kbps, up 519 kbps
  #2: down 2700 kbps, up 544 kbps
  #3: down 2964 kbps, up 389 kbps
  #4: down 2457 kbps, up 515 kbps

Modem #4 CRC count vs time graph:



Modem #4 stats:

xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason:   8000
Last initialization procedure status:   0
Max:   Upstream rate = 436 Kbps, Downstream rate = 2708 Kbps
Bearer:   0, Upstream rate = 515 Kbps, Downstream rate = 2457 Kbps

Link Power State:   L0
Mode:         ADSL2 Annex A
TPS-TC:         ATM Mode(0x0)
Trellis:      U:ON /D:ON
Line Status:      No Defect
Training Status:   Showtime
      Down      Up
SNR (dB):    3.1       6.0
Attn(dB):    65.0       41.0
Pwr(dBm):    18.4       12.4

         ADSL2 framing
         Bearer 0
MSGc:      52      11
B:      28      62
M:      8      1
T:      3      1
R:      16      12
S:      2.9745      3.8462
L:      667      156
D:      1      8

         Counters
         Bearer 0
SF:      2803623      754342
SFErr:      2593      10
RS:      60978814      473909
RSCorr:      201383      13964
RSUnCorr:   2733      0

ReXmt:      464652      0
ReXmtCorr:   464413      0
ReXmtUnCorr:   2884      0

         Bearer 0
HEC:      3616      17
OCD:      0      0
LCD:      0      0
Total Cells:   263857767      55806956
Data Cells:   5188622      1176787
Drop Cells:   0
Bit Errors:   167670      1432

ES:      219901      278
SES:      121      8
UAS:      4933      4825
AS:      45884

         Bearer 0
INP:      26.00      2.00
INPRein:   0.00      0.00
delay:      8      8
PER:      16.17      16.34
OR:      28.68      8.32
AgR:      2475.44   522.12

Bitswap:   5896/5896      105/105

Total time = 33 days 4 hours 1 min 23 sec
FEC:      21598882      717266
CRC:      347108      447
ES:      219901      278
SES:      121      8
UAS:      4933      4825
LOS:      12      2
LOF:      79      2
LOM:      8      0
Latest 15 minutes time = 1 min 23 sec
FEC:      348      11
CRC:      8      0
ES:      7      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      3625      274
CRC:      34      0
ES:      32      0
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 4 hours 1 min 23 sec
FEC:      57112      5415
CRC:      661      8
ES:      631      8
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      688715      22265
CRC:      9424      4
ES:      8006      4
SES:      0      0
UAS:      54      54
LOS:      0      0
LOF:      0      0
LOM:      0      0
Since Link time = 12 hours 44 min 43 sec
FEC:      201383      13964
CRC:      2593      10
ES:      2252      10
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
« Last Edit: May 12, 2020, 05:40:35 PM by Weaver »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #56 on: May 12, 2020, 07:05:59 PM »

Question: on the CRC and FEC const vs time graphs, what are the units on the vertical yaxis?

Number of events per minute. I.e. number of CRCs per minute and number of FECs per minute.

Quote
The CRC rate figure shown on the y axis is the count CRC of corrected errors[?] per unit what time[?]

No, not corrected errors but actual CRC errors recorded in the immediate, preceding minute.
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Weaver

  • Senior Kitizen
  • ******
  • Posts: 11459
  • Retd s/w dev; A&A; 4x7km ADSL2 lines; Firebrick
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #57 on: May 12, 2020, 07:17:21 PM »

Thank you I take it that FEC count is the count of error events corrected by RS ?

So it’s per minute. Where does L2 RETX come in in this count? Is PHY irrelevant here, if retransmission is required then it goes ahead and either succeeds or not but isn’t shown in these particular figures in this graph?

In the raw stats figures, are those first numbers under bearer 0 etc : ReXMT etc - are those just cumulative totals? Those in the first set just up and up? As opposed to being counts per some unit time interval? Which one sees further down in the various time interval sections.
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: Serving (slightly) better stats directly from Zyxel modems
« Reply #58 on: May 12, 2020, 07:53:49 PM »

Thank you I take it that FEC count is the count of error events corrected by RS ?

Yes, RS and any other "goodness" that was capable of making the correction

Quote
Where does L2 RETX come in in this count? Is PHY irrelevant here, if retransmission is required then it goes ahead and either succeeds or not but isn’t shown in these particular figures in this graph?

Sorry, that is something I do not know.

Quote
In the raw stats figures, are those first numbers under bearer 0 etc : ReXMT etc - are those just cumulative totals? Those in the first set just up and up? As opposed to being counts per some unit time interval? Which one sees further down in the various time interval sections.

They are cumulative totals. The delta is created by subtracting the previous cumulative total (at time n - 1 minutes) from the current cumulative total (at time n minutes).
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.
Pages: 1 2 3 [4]