dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
6653
share rss forum feed


dillyhammer
START me up
Premium,MVM
join:2010-01-09
Scarborough, ON
kudos:10
Reviews:
·WIND Mobile
·Start Communicat..
reply to urbang33k

Re: Bell Usage Meter counting LAN data?

Yeah, I don't know if it's even possible. What I'm saying is I can't imagine how Bell would see internal lan traffic otherwise. The device has nothing to do with measuring or calculating usage. That's done on a separate piece of equipment far from the user's premises.

This just doesn't make any sense on a lot of levels.

But I will say this. If an ISP was able to cook up some scheme to measure lan traffic and bill the user for it... I would surely expect Bell to be the first, and the leader, in such an endeavour.



Mike
--
Cogeco - The New UBB Devil -»[Burloak] Usage Based Billing Nightmare
Cogeco UBB, No Modem Required - »[Niagara] 40gb of "usage" while the modem is unplugged


MaynardKrebs
Heave Steve, for the good of the country
Premium
join:2009-06-17
kudos:4

Bell - The Stuxnet of Billing ???



pat2k8

join:2000-12-24
Burlington, ON
kudos:1

Click for full size
Well I am home, quickly hooked up my DD-WRT and got the house back online. Usage is "normal" and the last 5+ GB day was the 14th when I transfered a file from my NAS to my Desktop.

I remember questioning why my desktop was directly connected to my PPPOe and the 2-wire also was? I am curious if this appears as 2 connections through Bell and they tag my bandwidth?

anyways, I am maxed out for the month and will wait until the 27th to reconnect my 2-wire and prove out my theory.

Open to any other ideas.
--
Pat2k8@yahoo.caBurlington, Ontario.

a_mckie

join:2012-08-31
East York, ON

said by pat2k8 :
I am curious if this appears as 2 connections through Bell and they tag my bandwidth?
Are you suggesting the data goes from your home, to Bell, then back to your home again? Wouldn't the data be counted in your Upload data usage in that case?

-A


reallynow

@lightning.net
reply to pat2k8

Having LAN traffic go out to the Internet and back violates basic routing.

First, LAN uses rfc1918 addresses that would not route on the Internet.

Second, the net mask for the devices on the LAN would not send traffic to the default route since the devices all belong to the same local subnet.

Third, if your traffic went UP to the Internet and back DOWN to you machine then you would see 5gb upload and 5gb download, not 5gb download and less than 1gb upload.

Take your tinfoil hat off, get some sunlight and breath in the fresh air!



pat2k8

join:2000-12-24
Burlington, ON
kudos:1
reply to pulp46

I have warmed up to the idea that I am off my rocker. i am now looking to switch providers.

i did do a netstat with the 2-wire hooked -up and also tested my theory, but on the 2-wire i only can watch the Bell usage meter. Not very reliable. Netstat with the 2-wire shows a buch of WAN connections, as if it is taking priority over the LAN connection? They both travel down 1 cable to the 2-wire.

Anyhoo, if the is any interest in my netstat I dont want to post if nobody wants to see it.

I will watch the usage meter to see if my 650mb file transfer shows as a download. i am the only person on the network in my house right now......thx all.....
--

Burlington, Ontario.



pulp46
Premium
join:2003-01-28

Please post the netstat results, pat!



pat2k8

join:2000-12-24
Burlington, ON
kudos:1
reply to pulp46

okee dokee:

The first netstat is with my dd-wrt router and DSL-300G modem

The second is the 2-wire as the modem and router, my PC is connected to the router AND a PPPoe connection.(still unsure how this became connected before)

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tower>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:5354 Tower-PC:49155 ESTABLISHED
TCP 127.0.0.1:49155 Tower-PC:5354 ESTABLISHED
TCP 192.168.2.24:54872 208.89.14.135:https ESTABLISHED
TCP 192.168.2.24:54873 208.89.14.135:https ESTABLISHED
TCP 192.168.2.24:55947 www-slb-11-12-prn1:http TIME_WAIT
TCP 192.168.2.24:55949 67.69.174.115:http TIME_WAIT
TCP 192.168.2.24:55950 67.69.174.34:http TIME_WAIT
TCP 192.168.2.24:55974 67.69.174.18:http TIME_WAIT
TCP 192.168.2.24:55984 star-slb-ecmp-01-prn1:http TIME_WAIT
TCP 192.168.2.24:56004 yyz06s06-in-f23:https ESTABLISHED
TCP 192.168.2.24:56005 yyz06s07-in-f11:https ESTABLISHED
TCP 192.168.2.24:56006 yyz06s07-in-f11:https ESTABLISHED
TCP 192.168.2.24:56007 yyz06s06-in-f23:https ESTABLISHED
TCP 192.168.2.24:56008 yyz06s06-in-f23:https ESTABLISHED
TCP 192.168.2.24:56010 yyz06s06-in-f23:https ESTABLISHED
TCP 192.168.2.24:56012 yyz06s07-in-f24:https TIME_WAIT
TCP 192.168.2.24:56015 yyz06s06-in-f6:https ESTABLISHED
TCP 192.168.2.24:56016 yyz06s06-in-f6:https ESTABLISHED
TCP 192.168.2.24:56017 yyz06s06-in-f23:http ESTABLISHED
TCP 192.168.2.24:56068 yyz06s07-in-f15:https ESTABLISHED
TCP 192.168.2.24:56069 yyz06s07-in-f15:https ESTABLISHED
TCP 192.168.2.24:56070 yyz06s07-in-f15:https ESTABLISHED
TCP 192.168.2.24:56071 yyz06s06-in-f31:https ESTABLISHED
TCP 192.168.2.24:56072 yyz06s06-in-f31:https ESTABLISHED
TCP 192.168.2.24:56073 yyz06s06-in-f2:https ESTABLISHED
TCP 192.168.2.24:56074 yyz06s06-in-f2:https ESTABLISHED
TCP 192.168.2.24:56075 yyz06s06-in-f2:https ESTABLISHED
TCP 192.168.2.24:56076 yyz06s06-in-f9:https ESTABLISHED
TCP 192.168.2.24:56077 yyz06s06-in-f9:https ESTABLISHED
TCP 192.168.2.24:56078 yyz06s06-in-f9:https ESTABLISHED
TCP 192.168.2.24:56079 yyz06s06-in-f9:https ESTABLISHED
TCP 192.168.2.24:56080 yyz06s06-in-f9:https ESTABLISHED
TCP 192.168.2.24:56081 yyz06s06-in-f9:https ESTABLISHED
TCP 192.168.2.24:56082 yyz06s06-in-f3:https ESTABLISHED
TCP 192.168.2.24:56083 yyz06s06-in-f3:https ESTABLISHED
TCP 192.168.2.24:56084 yyz06s06-in-f3:https ESTABLISHED
TCP 192.168.2.24:56085 yyz06s06-in-f3:https ESTABLISHED
TCP 192.168.2.24:56086 yyz06s07-in-f8:https ESTABLISHED
TCP 192.168.2.24:56087 yyz06s07-in-f8:https ESTABLISHED
TCP 192.168.2.24:56088 yyz06s07-in-f8:https ESTABLISHED
TCP 192.168.2.24:56089 yyz06s07-in-f8:https ESTABLISHED
TCP 192.168.2.24:56090 yyz06s07-in-f8:https ESTABLISHED
TCP 192.168.2.24:56091 yyz06s07-in-f8:https ESTABLISHED
TCP 192.168.2.24:56092 yyz06s06-in-f3:https ESTABLISHED
TCP 192.168.2.24:56093 yyz06s06-in-f2:https ESTABLISHED
TCP 192.168.2.24:56094 yyz06s06-in-f3:https ESTABLISHED
TCP 192.168.2.24:56095 yyz06s06-in-f2:https ESTABLISHED
TCP 192.168.2.24:56096 yyz06s06-in-f2:https ESTABLISHED
TCP 192.168.2.24:56104 DCOSLA:https TIME_WAIT
TCP 192.168.2.24:56115 bell:https ESTABLISHED
TCP 192.168.2.24:56137 DNS-321:microsoft-ds ESTABLISHED

C:\Users\Tower>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 65.92.49.24:56286 yyz06s06-in-f0:https ESTABLISHED
TCP 65.92.49.24:56287 yyz06s06-in-f0:https ESTABLISHED
TCP 65.92.49.24:56294 www-ecmp-06-prn1:http ESTABLISHED
TCP 65.92.49.24:56295 67.69.174.115:http ESTABLISHED
TCP 65.92.49.24:56296 67.69.174.115:http TIME_WAIT
TCP 65.92.49.24:56297 67.69.174.115:http ESTABLISHED
TCP 65.92.49.24:56298 67.69.174.115:http TIME_WAIT
TCP 65.92.49.24:56299 67.69.174.115:http TIME_WAIT
TCP 65.92.49.24:56300 67.69.174.115:http ESTABLISHED
TCP 65.92.49.24:56301 67.69.174.25:http ESTABLISHED
TCP 65.92.49.24:56302 www-ecmp-06-prn1:http ESTABLISHED
TCP 65.92.49.24:56303 157.238.74.43:http TIME_WAIT
TCP 65.92.49.24:56304 157.238.74.43:http ESTABLISHED
TCP 65.92.49.24:56305 204.183.124.123:http ESTABLISHED
TCP 65.92.49.24:56306 67.69.174.25:http ESTABLISHED
TCP 65.92.49.24:56307 157.238.74.34:http ESTABLISHED
TCP 65.92.49.24:56308 157.238.74.34:http TIME_WAIT
TCP 65.92.49.24:56309 67.69.174.25:http ESTABLISHED
TCP 65.92.49.24:56310 67.69.174.25:http ESTABLISHED
TCP 65.92.49.24:56311 67.69.174.25:http ESTABLISHED
TCP 65.92.49.24:56312 67.69.174.25:http ESTABLISHED
TCP 65.92.49.24:56313 67.69.174.17:http TIME_WAIT
TCP 65.92.49.24:56314 67.69.174.9:http TIME_WAIT
TCP 65.92.49.24:56315 67.69.174.9:http TIME_WAIT
TCP 65.92.49.24:56316 67.69.174.114:http TIME_WAIT
TCP 65.92.49.24:56317 67.69.174.35:http ESTABLISHED
TCP 65.92.49.24:56318 67.69.174.35:http ESTABLISHED
TCP 65.92.49.24:56319 67.69.174.35:http TIME_WAIT
TCP 65.92.49.24:56320 67.69.174.35:http TIME_WAIT
TCP 65.92.49.24:56321 67.69.174.35:http TIME_WAIT
TCP 65.92.49.24:56322 67.69.174.35:http TIME_WAIT
TCP 65.92.49.24:56323 67.69.174.128:http TIME_WAIT
TCP 65.92.49.24:56324 67.69.174.130:http ESTABLISHED
TCP 65.92.49.24:56325 157.238.74.59:http TIME_WAIT
TCP 65.92.49.24:56326 67.69.174.130:http ESTABLISHED
TCP 65.92.49.24:56327 67.69.174.130:http ESTABLISHED
TCP 65.92.49.24:56328 67.69.174.130:http ESTABLISHED
TCP 65.92.49.24:56329 67.69.174.130:http ESTABLISHED
TCP 65.92.49.24:56330 67.69.174.130:http ESTABLISHED
TCP 65.92.49.24:56331 157.238.74.59:http ESTABLISHED
TCP 65.92.49.24:56332 204.183.124.98:http ESTABLISHED
TCP 65.92.49.24:56333 204.183.124.98:http ESTABLISHED
TCP 65.92.49.24:56334 204.183.124.98:http TIME_WAIT
TCP 65.92.49.24:56335 204.183.124.98:http TIME_WAIT
TCP 65.92.49.24:56336 star-slb-10-08-prn1:http ESTABLISHED
TCP 65.92.49.24:56337 star-slb-10-08-prn1:http TIME_WAIT
TCP 65.92.49.24:56338 www-ecmp-06-prn1:http ESTABLISHED
TCP 65.92.49.24:56339 channel-ecmp-13-prn1:http ESTABLISHED
TCP 127.0.0.1:2869 Tower-PC:56267 ESTABLISHED
TCP 127.0.0.1:5354 Tower-PC:49155 ESTABLISHED
TCP 127.0.0.1:5357 Tower-PC:56212 TIME_WAIT
TCP 127.0.0.1:5357 Tower-PC:56220 TIME_WAIT
TCP 127.0.0.1:5357 Tower-PC:56225 TIME_WAIT
TCP 127.0.0.1:5357 Tower-PC:56230 TIME_WAIT
TCP 127.0.0.1:5357 Tower-PC:56266 TIME_WAIT
TCP 127.0.0.1:5357 Tower-PC:56274 TIME_WAIT
TCP 127.0.0.1:49155 Tower-PC:5354 ESTABLISHED
TCP 127.0.0.1:56237 Tower-PC:56238 ESTABLISHED
TCP 127.0.0.1:56238 Tower-PC:56237 ESTABLISHED
TCP 127.0.0.1:56267 Tower-PC:icslap ESTABLISHED
TCP 192.168.2.103:56215 N Router 687F741C61AC:1780 TIME_WAIT
TCP 192.168.2.103:56239 yyz06s06-in-f20:http ESTABLISHED
TCP 192.168.2.103:56240 yyz06s06-in-f23:http ESTABLISHED
TCP 192.168.2.103:56243 yyz06s06-in-f15:https FIN_WAIT_1
TCP 192.168.2.103:56245 OCSP:http ESTABLISHED
TCP 192.168.2.103:56273 mymodem:http ESTABLISHED
TCP 192.168.2.103:56278 mymodem:http ESTABLISHED
TCP 192.168.2.103:56279 mymodem:http ESTABLISHED
TCP 192.168.2.103:56280 mymodem:http ESTABLISHED
TCP 192.168.2.103:56281 mymodem:http ESTABLISHED
TCP 192.168.2.103:56282 mymodem:http ESTABLISHED
TCP 192.168.2.103:56283 mymodem:http ESTABLISHED
TCP 192.168.2.103:56293 DNS-321:microsoft-ds ESTABLISHED

C:\Users\Tower>
--

Burlington, Ontario.



pulp46
Premium
join:2003-01-28

A LOT more TIME_WAIT going on with the 2wire. Hopefully someone with great experience will chyme in, thanks pat!



anon

@torservers.net
reply to pat2k8

Would you please try netstat -n so we can see the IP addresses rather than the host names? It will be easier to determine on-net/off-net traffic.

From the looks of it though, those yyzs06-*in-f* entries are typically Google CDN (Content Distribution Network) for Google/YouTube video streaming. These are local sites that help serve up content quicker.

If your PC was idle when you ran netstat, then there's some software running in the background doing something you are not aware of.



netstat

@bellmobilite.ca

netstat -bno will display the IP addresses, ports, owner of the process and the executable, that should give plenty of info including what program is connecting to what IP.



anon

@ccc.de
reply to pat2k8

Would you please try netstat -n so we can see the IP addresses rather than the host names? It will be easier to determine on-net/off-net traffic.

From the looks of it though, those yyzs06-*in-f* entries are typically Google CDN (Content Distribution Network) for Google/YouTube video streaming. These are local sites that help serve up content quicker.

If your PC was idle when you ran netstat, then there's some software running in the background doing something you are not aware of.



bestsavvy

@bell.ca

The troll is strong in this thread. 5+ pages wow. LAN usage is NOT counted geeze.



dillyhammer
START me up
Premium,MVM
join:2010-01-09
Scarborough, ON
kudos:10
Reviews:
·WIND Mobile
·Start Communicat..

said by bestsavvy :

The troll is strong in this thread. 5+ pages wow. LAN usage is NOT counted geeze.

We're talking about Bell here. Try and keep up, oh anonymous one.

»[Internet] Bell charging for wireless "intranet" usage

Mike
--
Cogeco - The New UBB Devil -»[Burloak] Usage Based Billing Nightmare
Cogeco UBB, No Modem Required - »[Niagara] 40gb of "usage" while the modem is unplugged
Expand your moderator at work