cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Re: Persistent Dropped Connections.

JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: Persistent Dropped Connections.

‎30-05-2015 5:48 PM

Ah, OK (I was working back from your post at 1252 which said you'd already done it.)
Message 46 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎30-05-2015 6:08 PM

i added an edit at 13.03 Smiley
Message 47 of 115
(1,080 Views)
0 Thanks
Townman
Superuser
Superuser
Posts: 23,056
Thanks: 9,642
Fixes: 160
Registered: ‎22-08-2007

Re: Persistent Dropped Connections.

‎30-05-2015 10:31 PM

Line test drops typically last a little over 3 minutes.

In another browser tab, login into the Plusnet user portal BEFORE clicking the fault & ticket links

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.

If this post helped, please click the Thumbs Up and if it fixed your issue, please click the This fixed my problem green button below.

Message 48 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎31-05-2015 5:25 AM

another drop at 21.50 pm last night  and my ip profile has dropped from 4mb to 3mb Cry   and again at 7.56am  Cry and snr has gone to  9 again Angry  just don a quiet line test and there seams to be some static noise on the line
edited to add second drop
Message 49 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎01-06-2015 6:19 AM

i have had more drops and my speed has dropped again and snr up around 10.4, here are my router logs and it show when it drops its terminating on a signal 15 ,  May 31 08:17:35  daemon  pppd[27096]: PPPoE: Terminating on signal 15. why is this PPPoE, i thought it shoud be PPPoA 0/38 which my router is set to, and also this is showing daemon pppd[27096]: Terminating connection due to link down.
all ideas and comments welcome
May 31 07:57:10  daemon  UPNPD[7390]: received signal 15, good-bye
 May 31 07:57:12  daemon  UPNPD[27422]: HTTP listening on port 2800
 May 31 07:57:14  user  syslog: end: interface: ppp_0_0_38_1 go to up
 May 31 08:04:32  daemon  DHCP SERVER: DHCP request from 00:26:ab:e1:f1:17
 May 31 08:04:32  daemon  DHCP SERVER: DHCP ack to 00:26:ab:e1:f1:17
 May 31 08:08:36  user  syslog: ethctl eth0 vport query 2>/var/vcfgerr
 May 31 08:08:36  user  syslog: rm /var/vcfgerr
 May 31 08:08:36  user  syslog: ethctl eth1 vport query 2>/var/vcfgerr
 May 31 08:08:36  user  syslog: rm /var/vcfgerr
 May 31 08:16:35  user  syslog: ethctl eth0 vport query 2>/var/vcfgerr
 May 31 08:16:35  user  syslog: rm /var/vcfgerr
 May 31 08:16:35  user  syslog: ethctl eth1 vport query 2>/var/vcfgerr
 May 31 08:16:35  user  syslog: rm /var/vcfgerr
 May 31 08:16:52  user  kernel: Line 0: ADSL link down
 May 31 08:16:53  user  syslog: tc qdisc del dev ppp_0_0_38_1 root 2>/dev/null
 May 31 08:16:54  daemon  pppd[27096]: Terminating connection due to link down.
 May 31 08:16:59  user  kernel: Line 0: xDSL G.994 training
 May 31 08:17:04  user  kernel: Line 0: ADSL link down
 May 31 08:17:05  user  kernel: Line 0: xDSL G.994 training
 May 31 08:17:10  user  kernel: Line 0: ADSL link down
 May 31 08:17:11  user  kernel: Line 0: xDSL G.994 training
 May 31 08:17:16  user  kernel: Line 0: ADSL link down
 May 31 08:17:17  user  kernel: Line 0: xDSL G.994 training
 May 31 08:17:19  user  kernel: Line 0: ADSL link down
 May 31 08:17:21  user  kernel: Line 0: xDSL G.994 training
 May 31 08:17:26  user  kernel: Line 0: ADSL G.992 started
 May 31 08:17:28  user  kernel: Line 0: ADSL G.992 channel analysis
 May 31 08:17:33  user  kernel: Line 0: ADSL link up, interleaved, us=448, ds=3840
 May 31 08:17:35  daemon  pppd[27096]: PPPoE: Terminating on signal 15.
 May 31 08:17:35  daemon  pppd[27096]: Clear IP addresses.  Connection DOWN.
 May 31 08:17:35  daemon  pppd[27096]: Clear IP addresses.
 May 31 08:17:35  daemon  pppd[27096]: Connection terminated.
 May 31 08:17:35  daemon  pppd[27096]: Connect time 20.5 minutes.
 May 31 08:17:35  daemon  pppd[27096]: Sent 793351 bytes, received 2732694 bytes.
 May 31 08:17:35  user  kernel: dev_shutdown, dec ppp device refcnt, dev->refcnt=4
 May 31 08:17:35  user  kernel: unregister_netdevice: waiting for ppp_0_0_38_1 to become free. Usage count = -1
 May 31 08:17:35  user  kernel: dev->name = ppp_0_0_38_1, dev->refcnt=-1
 May 31 08:17:35  user  kernel: after reset to 0, dev->refcnt=0
 May 31 08:17:35  daemon  pppd[27096]: Exit.
 May 31 08:17:35  daemon  pppd[31015]: PPPoATM setdevname_pppoatm
 May 31 08:17:35  daemon  pppd[31015]: PPPoATM setdevname_pppoatm - SUCCESS
 May 31 08:17:35  daemon  pppd[31015]: pppd 2.4.1 started by admin, uid 0
 May 31 08:17:35  daemon  pppd[31015]: PPP: Start to connect ...
 May 31 08:17:35  daemon  pppd[31015]: Using interface ppp0_0_38_1
 May 31 08:17:35  daemon  pppd[31015]: Connect: ppp_0_0_38_1 <-->
 May 31 08:17:42  daemon  pppd[31015]: PPP LCP UP.
 May 31 08:17:42  daemon  pppd[31015]: PPP LCP UP.
 May 31 08:17:43  daemon  pppd[31015]: local  IP address 87.112.189.235
 May 31 08:17:43  daemon  pppd[31015]: remote IP address 195.166.128.186
 May 31 08:17:43  daemon  pppd[31015]: primary   DNS address 212.159.6.9
 May 31 08:17:43  daemon  pppd[31015]: secondary DNS address 212.159.6.10
 May 31 08:17:43  daemon  pppd[31015]: Received valid IP address from server.  Connection UP.
 May 31 08:17:43  user  syslog: begin: interface: ppp_0_0_38_1 go to up
 May 31 08:17:44  daemon  dnsmasq[92]: using nameserver 8.8.4.4#53
 May 31 08:17:44  daemon  dnsmasq[92]: using nameserver 8.8.8.8#53
 May 31 08:17:44  daemon  UPNPD[27422]: received signal 15, good-bye
 May 31 08:17:46  daemon  UPNPD[31224]: HTTP listening on port 2800
 May 31 08:17:48  user  syslog: end: interface: ppp_0_0_38_1 go to up
 May 31 08:18:09  syslog  -- MARK --
 May 31 08:20:17  daemon  DHCP SERVER: DHCPDISCOVER from c4:95:a2:0e:67:dd via br0
 May 31 08:20:18  daemon  DHCP SERVER: DHCP offer to c4:95:a2:0e:67:dd
 May 31 08:20:18  daemon  DHCP SERVER: DHCP request from c4:95:a2:0e:67:dd
 May 31 08:20:18  daemon  DHCP SERVER: DHCP ack to c4:95:a2:0e:67:dd
 May 31 08:28:43  daemon  DHCP SERVER: DHCP request from 30:85:a9:55:e7:4b
 May 31 08:28:43  daemon  DHCP SERVER: DHCP ack to 30:85:a9:55:e7:4b
 May 31 08:54:23  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 08:54:23  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 09:09:52  daemon  DHCP SERVER: DHCPDISCOVER from c4:95:a2:0e:67:dd via br0
 May 31 09:09:53  daemon  DHCP SERVER: DHCP offer to c4:95:a2:0e:67:dd
 May 31 09:09:53  daemon  DHCP SERVER: DHCP request from c4:95:a2:0e:67:dd
 May 31 09:09:53  daemon  DHCP SERVER: DHCP ack to c4:95:a2:0e:67:dd
 May 31 09:18:09  syslog  -- MARK --
 May 31 09:28:11  daemon  DHCP SERVER: DHCPDISCOVER from c4:95:a2:0e:67:dd via br0
 May 31 09:28:12  daemon  DHCP SERVER: DHCP offer to c4:95:a2:0e:67:dd
 May 31 09:28:12  daemon  DHCP SERVER: DHCP request from c4:95:a2:0e:67:dd
 May 31 09:28:12  daemon  DHCP SERVER: DHCP ack to c4:95:a2:0e:67:dd
 May 31 09:36:31  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 09:36:31  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 09:39:01  daemon  DHCP SERVER: DHCP request from 18:3b:d2:96:fb:c4
 May 31 09:39:01  daemon  DHCP SERVER: DHCP ack to 18:3b:d2:96:fb:c4
 May 31 10:18:09  syslog  -- MARK --
 May 31 10:18:52  daemon  DHCP SERVER: DHCPDISCOVER from 00:1d:ec:08:e4:4b via br0
 May 31 10:18:52  daemon  DHCP SERVER: DHCP offer to 00:1d:ec:08:e4:4b
 May 31 10:18:52  daemon  DHCP SERVER: DHCP request from 00:1d:ec:08:e4:4b
 May 31 10:18:52  daemon  DHCP SERVER: DHCP ack to 00:1d:ec:08:e4:4b
 May 31 11:16:51  daemon  DHCP SERVER: DHCP request from 94:de:80:8a:aa:f1
 May 31 11:16:51  daemon  DHCP SERVER: DHCP ack to 94:de:80:8a:aa:f1
 May 31 11:18:09  syslog  -- MARK --
 May 31 11:19:23  daemon  DHCP SERVER: DHCP request from 18:3b:d2:96:fb:c4
 May 31 11:19:23  daemon  DHCP SERVER: DHCP ack to 18:3b:d2:96:fb:c4
 May 31 12:18:09  syslog  -- MARK --
 May 31 13:12:01  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 13:12:01  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 13:16:02  daemon  DHCP SERVER: DHCP request from 00:1c:26:4f:00:0b
 May 31 13:16:02  daemon  DHCP SERVER: DHCP ack to 00:1c:26:4f:00:0b
 May 31 13:16:34  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:16:37  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:18:09  syslog  -- MARK --
 May 31 13:19:27  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:19:30  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:20:40  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:20:43  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:21:58  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:22:02  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:23:28  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:23:31  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 13:54:55  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 13:54:55  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 14:18:09  syslog  -- MARK --
 May 31 15:18:08  syslog  -- MARK --
 May 31 16:18:08  syslog  -- MARK --
 May 31 16:40:00  daemon  DHCP SERVER: DHCP request from a0:02:dc:ed:17:9d
 May 31 16:40:00  daemon  DHCP SERVER: DHCP ack to a0:02:dc:ed:17:9d
 May 31 16:42:00  daemon  DHCP SERVER: DHCP request from 00:bb:3a:94:e0:8b
 May 31 16:42:00  daemon  DHCP SERVER: DHCP ack to 00:bb:3a:94:e0:8b
 May 31 17:18:08  syslog  -- MARK --
 May 31 17:39:16  user  kernel: KLOB extended to 5 pools
 May 31 17:50:25  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 17:50:25  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 18:18:08  syslog  -- MARK --
 May 31 18:35:51  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 18:35:51  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 18:43:27  daemon  DHCP SERVER: DHCP request from 00:1c:26:4f:00:0b
 May 31 18:43:27  daemon  DHCP SERVER: DHCP ack to 00:1c:26:4f:00:0b
 May 31 18:43:30  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 18:43:33  daemon  DHCP SERVER: DHCPINFORM from 192.168.1.106
 May 31 19:18:08  syslog  -- MARK --
 May 31 19:34:39  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 19:34:39  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 19:59:55  daemon  DHCP SERVER: DHCP request from 30:85:a9:55:e7:4b
 May 31 19:59:55  daemon  DHCP SERVER: DHCP ack to 30:85:a9:55:e7:4b
 May 31 20:14:22  daemon  DHCP SERVER: DHCP request from 00:26:ab:e1:f1:17
 May 31 20:14:22  daemon  DHCP SERVER: DHCP ack to 00:26:ab:e1:f1:17
 May 31 20:18:08  syslog  -- MARK --
 May 31 20:46:18  daemon  DHCP SERVER: DHCP request from 18:3b:d2:96:fb:c4
 May 31 20:46:18  daemon  DHCP SERVER: DHCP ack to 18:3b:d2:96:fb:c4
 May 31 21:11:22  daemon  DHCP SERVER: DHCP request from 18:3b:d2:96:fb:c4
 May 31 21:11:22  daemon  DHCP SERVER: DHCP ack to 18:3b:d2:96:fb:c4
 May 31 21:18:08  syslog  -- MARK --
 May 31 21:56:30  daemon  DHCP SERVER: DHCP request from cc:3a:61:b0:75:7a
 May 31 21:56:30  daemon  DHCP SERVER: DHCP ack to cc:3a:61:b0:75:7a
 May 31 22:18:08  syslog  -- MARK --
 May 31 22:18:52  daemon  DHCP SERVER: DHCP request from 00:1d:ec:08:e4:4b
 May 31 22:18:52  daemon  DHCP SERVER: DHCP ack to 00:1d:ec:08:e4:4b
 May 31 22:56:41  user  kernel: Line 0: ADSL link down
 May 31 22:56:42  user  syslog: tc qdisc del dev ppp_0_0_38_1 root 2>/dev/null
 May 31 22:56:42  user  kernel: Line 0: xDSL G.994 training
 May 31 22:56:44  daemon  pppd[31015]: Terminating connection due to link down.
 May 31 22:56:47  user  kernel: Line 0: ADSL G.992 started
 May 31 22:56:49  user  kernel: Line 0: ADSL G.992 channel analysis
 May 31 22:56:54  user  kernel: Line 0: ADSL link up, interleaved, us=448, ds=3552
 May 31 22:56:56  daemon  pppd[31015]: PPPoE: Terminating on signal 15.
 May 31 22:56:56  daemon  pppd[31015]: Clear IP addresses.  Connection DOWN.
 May 31 22:56:56  daemon  pppd[31015]: Clear IP addresses.
 May 31 22:56:56  daemon  pppd[31015]: Connection terminated.
 May 31 22:56:56  daemon  pppd[31015]: Connect time 879.4 minutes.
 May 31 22:56:56  daemon  pppd[31015]: Sent 123859057 bytes, received 631326182 bytes.
 May 31 22:56:56  user  kernel: dev_shutdown, dec ppp device refcnt, dev->refcnt=4
 May 31 22:56:57  user  kernel: unregister_netdevice: waiting for ppp_0_0_38_1 to become free. Usage count = -1
 May 31 22:56:57  user  kernel: dev->name = ppp_0_0_38_1, dev->refcnt=-1
 May 31 22:56:57  user  kernel: after reset to 0, dev->refcnt=0
 May 31 22:56:57  daemon  pppd[31015]: Exit.
 May 31 22:56:57  daemon  pppd[25253]: PPPoATM setdevname_pppoatm
 May 31 22:56:57  daemon  pppd[25253]: PPPoATM setdevname_pppoatm - SUCCESS
 May 31 22:56:57  daemon  pppd[25253]: pppd 2.4.1 started by admin, uid 0
 May 31 22:56:57  daemon  pppd[25253]: PPP: Start to connect ...
 May 31 22:56:57  daemon  pppd[25253]: Using interface ppp0_0_38_1
 May 31 22:56:57  daemon  pppd[25253]: Connect: ppp_0_0_38_1 <-->
 May 31 22:57:03  daemon  pppd[25253]: PPP LCP UP.
 May 31 22:57:04  daemon  pppd[25253]: PPP LCP UP.
 May 31 22:57:04  daemon  pppd[25253]: local  IP address 87.112.92.247
 May 31 22:57:04  daemon  pppd[25253]: remote IP address 195.166.128.192
 May 31 22:57:04  daemon  pppd[25253]: primary   DNS address 212.159.6.9
 May 31 22:57:04  daemon  pppd[25253]: secondary DNS address 212.159.6.10
 May 31 22:57:04  daemon  pppd[25253]: Received valid IP address from server.  Connection UP.
 May 31 22:57:05  user  syslog: begin: interface: ppp_0_0_38_1 go to up
 May 31 22:57:05  daemon  dnsmasq[92]: using nameserver 8.8.4.4#53
 May 31 22:57:05  daemon  dnsmasq[92]: using nameserver 8.8.8.8#53
 May 31 22:57:05  daemon  UPNPD[31224]: received signal 15, good-bye
 May 31 22:57:07  daemon  UPNPD[25482]: HTTP listening on port 2800
 May 31 22:57:09  user  syslog: end: interface: ppp_0_0_38_1 go to up
 May 31 23:16:50  daemon  DHCP SERVER: DHCP request from 94:de:80:8a:aa:f1
 May 31 23:16:50  daemon  DHCP SERVER: DHCP ack to 94:de:80:8a:aa:f1
 May 31 23:18:08  syslog  -- MARK --
 Jun 01 00:18:08  syslog  -- MARK --
 Jun 01 01:18:08  syslog  -- MARK --
 Jun 01 02:18:08  syslog  -- MARK --
 Jun 01 03:18:08  syslog  -- MARK --
 Jun 01 04:11:10  daemon  DHCP SERVER: DHCP request from a0:02:dc:ed:17:9d
 Jun 01 04:11:10  daemon  DHCP SERVER: DHCP ack to a0:02:dc:ed:17:9d
 Jun 01 04:13:14  daemon  DHCP SERVER: DHCP request from 00:bb:3a:94:e0:8b
 Jun 01 04:13:14  daemon  DHCP SERVER: DHCP ack to 00:bb:3a:94:e0:8b
 Jun 01 04:18:08  syslog  -- MARK --
 Jun 01 05:18:08  syslog  -- MARK --
 Jun 01 06:02:04  user  syslog: ethctl eth0 vport query 2>/var/vcfgerr
 Jun 01 06:02:04  user  syslog: rm /var/vcfgerr
 Jun 01 06:02:04  user  syslog: ethctl eth1 vport query 2>/var/vcfgerr
 Jun 01 06:02:04  user  syslog: rm /var/vcfgerr
Message 50 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎01-06-2015 12:52 PM

any update on question id 104974144 please
Message 51 of 115
(1,080 Views)
0 Thanks
plusnettony
Plusnet Staff
Plusnet Staff
Posts: 2,188
Thanks: 48
Fixes: 18
Registered: ‎24-07-2014

Re: Persistent Dropped Connections.

‎01-06-2015 6:32 PM

It's in the faults queue at the moment and will be picked up shortly.
If this post resolved your issue please click the 'This fixed my problem' button
 Tony T
 Plusnet Help Team
Message 52 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎01-06-2015 8:39 PM

Thanks for an update
Message 53 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎02-06-2015 12:26 PM

had a reply from plusnet saying no fault found and the connection has just dropped again straight to 0 and back up.
where do i go from here ,
connection went down 12.14,11 seconds  back up 12.14.46 seconds down for just 35 seconds
Message 54 of 115
(1,080 Views)
0 Thanks
MatthewWheeler
Plusnet Help Team
Plusnet Help Team
Posts: 8,908
Thanks: 1,525
Fixes: 479
Registered: ‎01-01-2012

Re: Persistent Dropped Connections.

‎02-06-2015 2:16 PM

That will have been our Faults team testing the line.
The testing is intrusive so it will have caused a drop.
Aside from that drop it doesn't look too bad and you should be getting around 3mbps at the moment?
For the length of your line that's quite good.
If this post resolved your issue please click the 'This fixed my problem' button
 Matthew Wheeler
 Plusnet Help Team
Message 55 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎02-06-2015 2:55 PM

here is a speed test of my line and a router stats, and my router stats are showing that my upsnr is 7.00db and down snr is 9.2 , my up has always been around 16db
is it normal to have drops on the line and can my snr be put back to 6db
cheers
Message 56 of 115
(1,080 Views)
0 Thanks
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: Persistent Dropped Connections.

‎02-06-2015 4:18 PM

Do those SNR's match what your router is reporting?
I doubt whether even with a perfect line you'd get a completely smooth US SNR plot like that.
Message 57 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎02-06-2015 4:24 PM

yes, here you go
Message 58 of 115
(1,080 Views)
0 Thanks
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: Persistent Dropped Connections.

‎02-06-2015 4:50 PM

Gosh - that has to be some sort of blip - perhaps someone with a Billion 7800n has seen something similar (if it's telling the truth, I want one!  ;))
Message 59 of 115
(1,080 Views)
0 Thanks
lenny
Grafter
Posts: 207
Registered: ‎04-05-2015

Re: Persistent Dropped Connections.

‎03-06-2015 9:11 AM

any comments please
Message 60 of 115
(1,080 Views)
0 Thanks