cancel
Showing results for 
Search instead for 
Did you mean: 

Trinitarian broadband!!!

Townman
Superuser
Superuser
Posts: 22,921
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Trinitarian broadband!!!

Quote from: avodat
Townman - that also changes from having data to no data.

That is either symptomatic of the RouterStats issue or that the laptop is loosing connection to the router.  Looking at the graph rather suggests that negative numbers are being found as opposed to zero, so I suspect that the messages have been scrambled - remember I said it could self-heal in minutes or days!
Kevin

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Trinitarian broadband!!!

If there's no RouterStats.ini file something really has got corrupted  Shocked
Ah, just had a thought, depending on what you are looking with, files with extension names .ini may not be being displayed or the extension isn't.
As I'm not running that version of Windows I can't help on that.  W7 - 64 bit IIRC.
avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

Ok, found the file now - I had discovered that when I did RS config and clicked the 'save', button below the graph, that it doesn't actually save the config data when it is closed down. Yesterday, I took the trouble to search a bit deeper into RS and found the Save Config button at the top of RS window!  
So, yes, there is now a RS config.ini file, as I have just found, but you have to use that button or there is no .ini file.
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Trinitarian broadband!!!

I did, but I can quite understand you missing it in this huge volume of technical stuff you've suddenly had to cope with, which frankly you are doing extremely well. Not to worry.
It's RouterStats.ini     and you should find it in the same place (folder) as you installed RouterStats with the RouterStats.exe file.
avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

See my previous post
I should add that I had yesterday run a search for the file name you were using but it returned nothing, hence my question. At about 11pm last night I clicked the save config button, closed it down and went to bed. After I responded to your yesterday post, this morning, I went back to check and, yes, it was created at 22.57 last night.
However, I have now copied and pasted the file and and called it RouterStatsNew.ini - if I need it I'll change the name again to its original title, having deleted the old version.
BTW stats seem to be running ok this morning, but as I didn't get up until about 8am (shame on me!) it has only been running, today, for a short while.
avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

Here's some of the silly data from last night    Grin
Fri 29 Aug 2014  22:16:24 Rx-Noise=6.4 Tx-Noise=30.8 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:16:44 Rx-Noise=6.4 Tx-Noise=31.0 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:17:04 Rx-Noise=6.4 Tx-Noise=31.0 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:17:24 Rx-Noise=6.4 Tx-Noise=31.0 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:17:44 Rx-Noise=6.4 Tx-Noise=31.0 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:18:04 Rx-Noise=6.4 Tx-Noise=31.0 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:18:25 Rx-Noise=6.4 Tx-Noise=31.0 Rx-Sync=12925 Tx-Sync=440 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:18:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:19:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:19:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:19:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:20:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:20:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:20:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:21:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:21:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:21:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:22:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:22:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:22:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:23:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:23:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:23:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:24:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:24:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:24:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:25:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:25:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:25:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=249896855 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:26:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=249896855 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:26:25 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=249896855 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:26:45 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Fri 29 Aug 2014  22:27:05 Rx-Noise=0.0 Tx-Noise=0.0 Rx-Sync=0 Tx-Sync=0 Rx-=0.0 Tx-=0.0
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Trinitarian broadband!!!

Good morning again  avodat.
Always keep a backup copy of the latest correctly working RouterStats.ini file and always use a copy command to replace a corrupted file so that the backup remains untouched.
Also remember that should you change anything on the RouterStats configuration Login&Logout tab, it immediately starts a new RouterStats.ini file with default settings. Other tabs, you can alter settings without that worry.
As for the silly data  Grin  yep, that's what it does when things go wotsit up as mentioned in Kevin's Confession!
avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

These look a lot healthier!!
<102> Aug 30 00:54:14 SNTP Synchronised again to server: 212.159.6.9
<102> Aug 30 01:54:15 SNTP Synchronised again to server: 212.159.6.9
<81> Aug 30 02:47:51 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 66.85.173.179 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<102> Aug 30 02:54:15 SNTP Synchronised again to server: 212.159.6.9
<102> Aug 30 03:54:15 SNTP Synchronised again to server: 212.159.6.9
<102> Aug 30 04:54:15 SNTP Synchronised again to server: 212.159.6.9
<81> Aug 30 05:15:56 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 66.85.173.179 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<81> Aug 30 05:25:16 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 66.85.173.179 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<81> Aug 30 05:49:50 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 66.85.173.179 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<102> Aug 30 05:54:15 SNTP Synchronised again to server: 212.159.6.9
<81> Aug 30 06:02:52 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 182.133.230.230 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 06:05:15 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 183.67.111.218 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 06:11:15 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 222.83.61.186 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 06:12:36 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 96.251.26.170 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 06:26:10 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 119.164.116.119 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 06:28:38 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 203.198.244.31 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<81> Aug 30 06:45:43 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 58.69.142.179 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 06:54:15 SNTP Synchronised again to server: 212.159.6.9
<81> Aug 30 07:02:05 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 173.55.15.219 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 07:54:15 SNTP Synchronised to server: 212.159.13.49
<37> Aug 30 08:09:22 LOGIN User logged in on TELNET (192.168.1.)
<81> Aug 30 08:23:46 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 185.9.194.1 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Host Unreacheable
<37> Aug 30 08:33:41 LOGIN User logged in on [HTTP] (from 192.168.1.)
<102> Aug 30 08:54:16 SNTP Synchronised again to server: 212.159.13.49 )
<81> Aug 30 09:18:45 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 71.105.17.59 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<37> Aug 30 09:26:57 LOGIN User logged in on [HTTP] (from 192.168.1.)
<37> Aug 30 09:53:55 LOGIN User  logged in on [HTTP] (from 192.168.1.)
<102> Aug 30 09:54:16 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 10:18:39 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 66.85.173.179 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<81> Aug 30 10:44:59 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 181.236.176.47 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 10:54:16 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 11:10:14 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 220.109.219.118 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 11:28:56 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 184.66.130.66 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Aug 30 11:28:59 FIREWALL replay check (1 of 1): Protocol: ICMP  Src ip: 184.66.130.66 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<37> Aug 30 11:40:48 LOGIN User  logged in on [HTTP] (from 192.168.1.)
<81> Aug 30 11:52:34 FIREWALL replay check (1 of 2): Protocol: ICMP  Src ip: 82.10.56.194 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Host Unreacheable
<102> Aug 30 11:54:16 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 12:10:22 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 111.194.171.66 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 12:40:29 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 191.243.209.2 Dst ip: 91.125.2.98 Type: Time Exceeded Code: Time to Live exceeded in Transit
<102> Aug 30 12:54:16 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 13:52:56 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 179.200.144.201 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 13:54:16 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 14:02:25 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 110.51.2.96 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 14:22:55 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 36.45.180.9 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 14:29:23 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 110.154.120.42 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 14:54:17 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 15:14:30 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 180.143.140.252 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<84> Aug 30 15:39:07 IDS proto parser : tcp null port (1 of 1) : 123.151.42.61   91.125.2.98     40    46  TCP 12208->0 [S.....] seq 395949732 ack 0 win 8192
<81> Aug 30 15:43:27 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 31.18.236.38 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Aug 30 15:43:30 FIREWALL replay check (1 of 1): Protocol: ICMP  Src ip: 31.18.236.38 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<102> Aug 30 15:54:17 SNTP Synchronised again to server: 212.159.13.49
<84> Aug 30 15:58:40 IDS scan parser : tcp port scan: 74.125.230.159 scanned at least 10 ports at 91.125.2.98. (1 of 1) : 74.125.230.159  91.125.2.98     40    56  TCP 80->54615 [...R..] seq 2991951266 ack 0 win 0
<81> Aug 30 16:05:15 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 211.204.219.21 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 16:47:40 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 59.86.196.85 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Aug 30 16:51:51 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 173.51.160.146 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 16:54:17 SNTP Synchronised again to server: 212.159.13.49
<84> Aug 30 17:26:31 IDS proto parser : tcp null port (1 of 1) : 113.108.21.16   91.125.2.98     40    48  TCP 12209->0 [S.....] seq 1027199114 ack 0 win 8192
<102> Aug 30 17:54:17 SNTP Synchronised again to server: 212.159.13.49
<81> Aug 30 18:24:16 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 89.217.76.63 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Aug 30 18:24:19 FIREWALL replay check (1 of 2): Protocol: ICMP  Src ip: 89.217.76.63 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Aug 30 18:31:25 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 186.208.124.117 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Aug 30 18:54:17 SNTP Synchronised again to server: 212.159.13.49
{admin}

          Uptime: 1 day, 7:35:28    DSL Type: ITU-T G.992.5    Bandwidth (Up/Down) [kbps/kbps]: 440 / 12.925    Data Transferred (Sent/Received) [MB/GB]: 92,75 / 1,15    Output Power (Up/Down) [dBm]: 12,6 / 0,0    Line Attenuation (Up/Down) [dB]: 10,8 / 22,5    SN Margin (Up/Down) [dB]: 31,2 / 6,4    System Vendor ID (Local/Remote): TMMB / ----    Chipset Vendor ID (Local/Remote): BDCM / IFTN    Loss of Framing (Local/Remote): 0 / 0    Loss of Signal (Local/Remote): 0 / 0    Loss of Power (Local/Remote): 0 / 0    Loss of Link (Remote): -    Error Seconds (Local/Remote): 87 / 0    FEC Errors (Up/Down): 0 / 31.156    CRC Errors (Up/Down): 0 / 154    HEC Errors (Up/Down): 0 / 2.235 generateTasks() 
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Trinitarian broadband!!!

They certainly do, let's hope it continues OK.
avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

Dragging along at 6.3 (6.4 at best), but no freaking-out by the router, as yet.  Signal strength, as measured by Net Gear app, averages 100% at -47dBm at the router location (still in the hall with trailing lead)..
Townman
Superuser
Superuser
Posts: 22,921
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Trinitarian broadband!!!

Hi Avodat,
The SNRM is not a concern.  6dB is what the line has been set to.  The synch speed is what it is.  The most important thing right now is that you no longer get drops.
Kevin

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Acassim
Plusnet Alumni (retired)
Plusnet Alumni (retired)
Posts: 1,075
Registered: ‎11-06-2007

Re: Trinitarian broadband!!!

Hi all,
Finally back on community for the majority of the week so should have a little more time to keep an eye on this thread now.
@Avodat - How has the connection been for you today? I see from your RADIUS logs that you've had an ongoing connection for just over 2 days now which looks promising. In addition to this I see the speed is set to 11.4mbps on our side after a drop down to 7.1mbps on the 28/08/14 so this looks like a promising sign also.
I'm hoping that we see the speeds start to move back up however we can still travel down the route of looking at the replacement of the copper.
avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

Hi Adam,
It seems to be trundling along ok, with no drops for a few days  Smiley
The difficlty with replacing the copper wire is that I live in a tied house - the phone belongs to my landlord. If he pays for it to be updated, I have to pay tax on the cost as it is a benefit, not an essential part of the landlord's responsibility. The only other possibility is that I pay for it, which I cannot afford (I already live in fuel poverty!).
Townman
Superuser
Superuser
Posts: 22,921
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Trinitarian broadband!!!

Quote from: Townman
@Adam,
Just thinking, does anything need doing with the open fault ticket to stop it "dying" ?

Hi Adam,
It is good to see you back here, hope you were not called out too often during the weekend.
We really need to see if Avodat can get through a week without a disconnect before he looks at moving his kit back to its usual location.  It would be very interesting news all round if we find that the connectivity issues appears resolved by the firmware upgrade.  Positive for Avodat and informative to the PN diagnostic process.
Fixing the disconnects I suspect is Avodat's primary concern, though it would be good to also get the line running nearer its full potential synch speed.
Thanks for your continued attention to this one.
Cheers,
Kevin

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

avodat
Grafter
Posts: 128
Registered: ‎25-07-2014

Re: Trinitarian broadband!!!

Seem to have spoken too soon:
<81> Sep  1 00:04:23 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 79.100.172.17 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 00:21:47 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 58.51.112.115 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 00:54:01 SNTP Synchronised again to server: 212.159.13.50
<81> Sep  1 01:04:53 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 198.27.77.37 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Protocol Unreacheable
<81> Sep  1 01:21:25 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 46.10.20.82 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 01:54:01 SNTP Synchronised again to server: 212.159.13.50
<81> Sep  1 02:25:03 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 77.85.145.57 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 02:45:48 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 179.21.188.230 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 02:50:32 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 175.181.116.19 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 02:54:00 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 208.175.134.203 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 02:54:01 SNTP Synchronised to server: 212.159.6.10
<81> Sep  1 03:01:09 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 190.88.163.60 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 03:25:10 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 27.188.27.108 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 03:54:01 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 04:41:44 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 110.47.25.173 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 04:54:01 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 05:29:57 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 177.216.50.243 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 05:54:01 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 06:08:16 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 183.87.246.48 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 06:54:01 SNTP Synchronised again to server: 212.159.6.10
<37> Sep  1 07:29:12 LOGIN User logged in on TELNET (192.168.1.)
<102> Sep  1 07:54:02 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 08:18:49 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 212.25.56.22 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 08:54:02 SNTP Synchronised again to server: 212.159.6.10
<37> Sep  1 08:55:27 LOGOUT User logged out on TELNET (192.168.1.)
<81> Sep  1 09:13:33 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 177.86.180.193 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 09:18:20 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 191.24.173.115 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 09:29:17 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 210.109.120.68 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 09:39:48 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 217.14.192.25 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<102> Sep  1 09:54:02 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 10:00:30 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 46.255.64.208 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 10:44:44 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 183.201.87.65 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 10:54:02 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 11:05:47 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 202.216.4.123 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Host Unreacheable
<84> Sep  1 11:08:31 IDS proto parser : tcp null port (1 of 1) : 113.108.21.16   91.125.2.98     40    48  TCP 12203->0 [S.....] seq 1061025786 ack 0 win 8192
<81> Sep  1 11:41:33 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 179.228.231.42 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 11:54:02 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 12:13:59 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 114.83.34.126 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 12:53:03 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 151.230.135.117 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Host Unreacheable
<102> Sep  1 12:54:02 SNTP Synchronised again to server: 212.159.6.10
<37> Sep  1 12:58:15 LOGIN User logged in on TELNET (192.168.1.)
<37> Sep  1 13:10:51 LOGOUT User logged out on TELNET (192.168.1.)
<81> Sep  1 13:19:01 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 89.245.238.106 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<81> Sep  1 13:19:04 FIREWALL replay check (1 of 1): Protocol: ICMP  Src ip: 89.245.238.106 Dst ip: 91.125.2.98 Type: Destination Unreachable Code: Communication Administratively Prohibited
<102> Sep  1 13:54:03 SNTP Synchronised again to server: 212.159.6.10
<173> Sep  1 14:30:41 xDSL linestate down
<132> Sep  1 14:31:29 PPP link down (Internet) [91.125.2.]

<173> Sep  1 14:31:36 xDSL linestate down
<173> Sep  1 14:32:34 xDSL linestate down
<173> Sep  1 14:33:04 xDSL linestate down
<173> Sep  1 14:33:30 xDSL linestate up (ITU-T G.992.5; downstream: 12880 kbit/s, upstream: 440 kbit/s; output Power Down: 20.9 dBm, Up: 12.9 dBm; line Attenuation Down: 23.0 dB, Up: 10.8 dB; snr Margin Down: 6.1 dB, Up: 31.1 dB)
<38> Sep  1 14:33:33 PPP CHAP Receive challenge from rhost bras-red6.wv (Internet)
<38> Sep  1 14:33:34 PPP CHAP Receive challenge from rhost PCL-AG02 (Internet)
<38> Sep  1 14:33:35 PPP CHAP Receive success (Internet)
<132> Sep  1 14:33:36 PPP link up (Internet) [87.112.59.]


<14> Sep  1 14:34:16 CONFIGURATION saved by TR69
<81> Sep  1 14:34:54 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 88.134.219.145 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Host Unreacheable
<81> Sep  1 14:53:03 FIREWALL icmp check (1 of 7): Protocol: ICMP  Src ip: 175.136.231.125 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 14:54:03 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 15:27:24 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 101.85.157.59 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<102> Sep  1 15:54:03 SNTP Synchronised again to server: 212.159.6.10
<81> Sep  1 15:58:19 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 118.161.36.249 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<81> Sep  1 16:09:40 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 115.25.87.211 Dst ip: 87.112.59.198 Type: Destination Unreachable Code: Port Unreacheable
<37> Sep  1 16:12:49 LOGIN User logged in on TELNET (192.168.1.)
{admin}