If you don't like AT&T, go to another service provider. That's the wonderful thing about competition, consumer choice. The only regulation that would be acceptable is mandated transparency, where if the business operates a certain way, it has to let the customer know in the fine print. The only time the government should be enforcing "net neutrality" is if the government has already created a legal monopoly, and the consumer does not have a choice. These types of telecommunication monopolies already exist is some areas.
I never said it gave you information on protocols used, I said "then you can use other apps to test port response times" you do not need admin access to remotely get response times to a remote port, you just need to be able to access the port, if you can't, then slow downs are not the issue as you can't access it to begin with if port 80 is fast, but port 8383 to same server is slow, and 8383 is someone streaming port, then the question is WHY is one slow and the other not, if you get the same results from multiple ISPs, the issue is on the streaming servers side or their ISP, if it's not, then it's on the client or ISP of the client side these tools help pinpoint the issue and yes, tracert, ping and testing port responsiveness, ect.... from multiple points and systems is some of basic tools\methods professionals use to trouble shoot\test networks and point them where to do more detailed research, you have to start somewhere and work your way down till you find the root of the issue, common sense .
What apps can you use to monitor ports that get you what you claim can be found? And ports do not initiate the responses. Learn the material before you speak.
near as I can tell net neutrality is solution in search of a problem, just another layer of useless bureaucracy at best and big government intrusion at the worst
yes, but the fcc has access to the results of whatever tests they perform from all of their volunteers ISPs, not what a free speedtest site would offer you for instance when you get statistics from a large number of users from a large number of ISPs, you can start to compile the data, if netflix also gives the gov such access then they can also see Netflix's ISP stats again just one more tool in the arsenal ... .
where did I say that, you need to slow down and actually read a post the FCC is using crowd-sourcing to preform some testing of ISP networks http://www.fcc.gov/measuring-broadband-america "Measuring Fixed Broadband Reports offer results of rigorous broadband performance testing for 13 of the largest wireline broadband providers that serve well over 80 percent of the U.S. residential market. Tests conducted used automated, direct measurements of service delivered to the homes of thousands of volunteers across the United States. Learn More. " the FCC has access to the hardware the volunteers install on their network, the fcc supplies this hardware, it's their server, the server reports the data to one of the FCC's servers, so what more access do they need to access their own data? .
You need to know what you are talking about. So what test inspects router configs? Your link is like the other links I've responded about. They do not monitor network's configs which can be altered to affect speed. You have yet to address anything I have asked about. Go and get educated about how networks work pal.
where did I say anything about router configs? you start by testing speeds and looking for slow downs, if you find a issue then you move to the next step and work on getting access to the routers you have identified as having an issue your problem is you think you know exactly where the issue is before you research it, that is not the way it works, you troubleshoot the issue first to pinpoint where the issue is just because Netflix is slow on a persons PC\TIVO\ect.... doesn't mean it's the ISPs fault, that is why you do this type of research from multiple clients, multiple ISPs, ect..... think bigger, your thinking too small, the FCC is not out to find "one client" issues and resolve them, that is not their job, they are looking for trends that effect all\many of a ISPs clients if one person complains, the FCC is not even going to look into it, if 1000's do repeatedly over time, they will look into it .
You can alter router configs to slow down traffic. Testing speeds from A to B mean nothing. You have to go deeper. Your problem is you know nothing about me. I have a CCENT, CCNA, a CCNAS, CompTIA+ CCNA Voice certs. I do admin work fora managed services company here in the Chicago area. For some silly reason you think a few tests are sufficient to monitor ISP's to verify compliance with respect to the new rules. And you are wrong. You have yet to say what test gets you the results you are looking for. The tests you name do not prove what you claim no matter how much you keep repeating it. YOU think bigger pal! I already am! You will need to monitor thousands of routers, know their configs and analyze all the data to see if the ISP is complying with speed consistency in every case. LOL! And what does 'look into it' mean? You have yet to offer any answers that will fit that criteria. You think you know what you're talking about but you really don't.
the FCC is not tech support, they are looking for trends, they are not gonna research single client issues, they are gonna to gather results from many ISP's, many Clients and look for trends, coupled with complaints from multiple customers of ISPs not sure what your point is anyways, are you saying we should let the ISPs be bad guys cause you with so much network knowledge can't even understand how they will tell there were network issues over long periods of time that only effect certain web services of certain companies after an issue was reported to them by 1000's of customers over a a given period of time? .
Routers do no have to have issues to slow down traffic. Make sense novice. You're not capable of keeping up with me pretender. What tests are those kid?
where did I say that caused ALL slow downs? the ISSUE will be able to be tracked down to potential endpoints, common points between multiple clients with that same issue, you keep narrowing the points to search until you find the root cause, isn't that how you troubleshoot the network in your company? or do you use a magic eight ball? fact is, the very first step will to be to contact the ISP in question and ask them to look into it, most likely when the ISP realizes they have been caught, they will correct it, if not the FCC will have to do more .
What the hell does all of that mean? How will you do that? So you'll trust the ISP to just step up and say 'we're wrong' because some ignorant FFC dweeb called them?? And what 'more' will the FCC 'do' and how? Still waiting.
you obviously have no network knowledge as I explained one way it could be done and you still don't get it the FCC only needs to show a trend of it happening to multiple clients over a period of time and that the slow point is on the ISPs network, it will be up to the ISP to explain why it's happening and fix it it's like telemarketing rules, we fine corps that call after a certain time or ignore do not call lists... how do they test that? they check call reports from the client side, if they show a call from the offending corp, the offending corp needs to show why or face a large fine, they do not have to prove it was intentional, only that it happened, and they only really check into it based on many complaints, but many companies have paid the price for violating it, and now most large corps do not violate those rules "Telemarketer agrees to $3.4 million FTC penalty over unwanted calls" http://www.today.com/news/telemarketer-agrees-3-4-million-ftc-penalty-over-unwanted-calls-2D79710375 .
Hey buddy, tell me what this router is doing and give me a topology based on this CLI.............. Current configuration : 1574 bytes ! version 15.1 no service timestamps log datetime msec no service timestamps debug datetime msec no service password-encryption ! hostname ISP ! ! ! ! ! ! no ip cef no ipv6 cef ! ! ! ! license udi pid CISCO2911/K9 sn FTX1524R44K ! ! ! ! ! ! ! ! ! ! ! spanning-tree mode pvst ! ! ! ! ! ! interface GigabitEthernet0/0 ip address 30.30.30.30 255.255.255.0 duplex auto speed auto ! interface GigabitEthernet0/1 no ip address duplex auto speed auto shutdown ! interface GigabitEthernet0/2 no ip address duplex auto speed auto shutdown ! interface Serial0/1/0 no ip address clock rate 2000000 shutdown ! interface Serial0/1/1 no ip address clock rate 2000000 shutdown ! interface Serial0/2/0 ip address 27.27.27.28 255.255.255.0 ip ospf authentication message-digest ip ospf message-digest-key 1 md5 cisco clock rate 2000000 ! interface Serial0/2/1 no ip address clock rate 2000000 shutdown ! interface Serial0/3/0 ip address 26.26.26.27 255.255.255.0 ip ospf authentication message-digest ip ospf message-digest-key 1 md5 cisco clock rate 2000000 ! interface Serial0/3/1 --More-- %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/2/0, changed state to up ip address 28.28.28.29 255.255.255.0 ip ospf authentication message-digest ip ospf message-digest-key 1 md5 cisco clock rate 2000000 ! interface Vlan1 no ip address shutdown ! router ospf 1 log-adjacency-changes network 26.26.26.0 0.0.0.255 area 0 network 30.30.30.0 0.0.0.255 area 0 network 28.28.28.0 0.0.0.255 area 0 network 27.27.27.0 0.0.0.255 area 0 ! ip classless ! ip flow-export version 9 ! ! ! ! ! ! ! line con 0 ! line aux 0 ! line vty 0 4 login ! ! ! end
Explain what's going on here......................... hostname S3Router ! ! ! enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0 ! ! ip dhcp excluded-address 192.168.70.1 192.168.70.9 ip dhcp excluded-address 192.168.100.1 192.168.100.9 ip dhcp excluded-address 172.16.0.1 172.16.0.20 ! ip dhcp pool VLAN70 network 192.168.70.0 255.255.255.0 default-router 192.168.70.1 dns-server 192.168.50.2 ip dhcp pool VOICE network 192.168.100.0 255.255.255.0 default-router 192.168.100.1 option 150 ip 10.0.0.1 dns-server 192.168.50.2 ip dhcp pool WIRELESS network 172.16.0.0 255.255.255.0 default-router 172.16.0.1 dns-server 8.8.8.8 ! ! aaa new-model ! aaa authentication login default group tacacs+ local ! ! aaa authorization exec default group tacacs+ local ! ! ! no ip cef no ipv6 cef ! ! ! username admin privilege 15 secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0 ! ! license udi pid CISCO2911/K9 sn FTX1524L4OY license boot module c2900 technology-package securityk9 ! ! ! crypto isakmp policy 1 encr aes 256 authentication pre-share group 2 ! crypto isakmp key cisco address 26.26.26.26 ! ! crypto ipsec security-association lifetime seconds 86400 ! crypto ipsec transform-set SECUREWAN esp-aes 256 esp-sha-hmac ! crypto map IPSECWAN 100 ipsec-isakmp set peer 26.26.26.26 set pfs group2 set security-association lifetime seconds 86400 set transform-set SECUREWAN match address SECURED-TRAFFIC ! ! ! ! ip ssh version 2 ip domain-name mycorp.com ! ! spanning-tree mode pvst ! ! ! ! ! ! interface GigabitEthernet0/0 no ip address duplex auto speed auto ! interface GigabitEthernet0/0.70 encapsulation dot1Q 70 ip address 192.168.70.1 255.255.255.0 ip nat inside ! interface GigabitEthernet0/0.100 encapsulation dot1Q 100 ip address 192.168.100.1 255.255.255.0 ! interface GigabitEthernet0/1 ip address 172.16.0.1 255.255.255.0 ip access-group 100 in ip nat inside duplex auto speed auto ! interface GigabitEthernet0/2 no ip address duplex auto speed auto shutdown ! interface Serial0/3/0 no ip address clock rate 2000000 shutdown ! interface Serial0/3/1 ip address 27.27.27.27 255.255.255.0 ip ospf authentication message-digest ip ospf message-digest-key 1 md5 cisco ip nat outside clock rate 2000000 crypto map IPSECWAN ! interface Vlan1 no ip address shutdown ! router ospf 1 log-adjacency-changes network 192.168.70.0 0.0.0.255 area 3 network 192.168.100.0 0.0.0.255 area 3 network 27.27.27.0 0.0.0.255 area 0 ! ip nat inside source list NATOVERLOAD interface Serial0/3/1 overload ip classless ip route 0.0.0.0 0.0.0.0 Serial0/3/1 ! ip flow-export version 9 ! ! ip access-list extended SECURED-TRAFFIC permit ip 192.168.70.0 0.0.0.255 192.168.10.0 0.0.0.255 access-list 1 permit 192.168.60.0 0.0.0.255 access-list 100 deny ip 172.16.0.0 0.0.0.255 192.168.0.0 0.0.255.255 access-list 100 deny ip 172.16.0.0 0.0.255.255 10.0.0.0 0.0.0.255 access-list 100 permit ip any any access-list 2 permit 192.168.70.0 0.0.0.255 access-list 3 permit 172.16.0.0 0.0.0.255 ip access-list extended NATOVERLOAD deny ip 192.168.70.0 0.0.0.255 192.168.10.0 0.0.0.255 deny ip 192.168.70.0 0.0.0.255 192.168.20.0 0.0.0.255 deny ip 192.168.70.0 0.0.0.255 192.168.30.0 0.0.0.255 deny ip 192.168.70.0 0.0.0.255 192.168.40.0 0.0.0.255 deny ip 192.168.70.0 0.0.0.255 192.168.50.0 0.0.0.255 deny ip 192.168.70.0 0.0.0.255 192.168.60.0 0.0.0.255 permit ip 192.168.70.0 0.0.0.255 any permit ip 172.16.0.0 0.0.0.255 any ! no cdp run ! ! tacacs-server host 192.168.50.2 key cisco ! ! ! logging 192.168.50.2 line con 0 ! line aux 0 ! line vty 0 4 access-class 1 in exec-timeout 2 0 login authentication default transport input ssh line vty 5 15 access-class 1 in exec-timeout 2 0 login authentication default transport input ssh ! ! ntp authentication-key 1234 md5 0822455D0A16 7 ntp authenticate ntp server 192.168.50.2 key 0 ! end
Help me with this.................... S2S2>en Password: S2S2#show run Building configuration... Current configuration : 2372 bytes ! version 12.2 no service timestamps log datetime msec no service timestamps debug datetime msec no service password-encryption ! hostname S2S2 ! enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0 ! ! ! mls qos ! ip ssh version 2 ip domain-name mycorp.com ! username admin secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0 ! ! spanning-tree mode pvst ! interface FastEthernet0/1 switchport access vlan 70 switchport mode access switchport voice vlan 100 switchport port-security maximum 2 switchport port-security mac-address sticky spanning-tree portfast mls qos trust dscp ! interface FastEthernet0/2 switchport access vlan 70 switchport mode access switchport voice vlan 100 switchport port-security maximum 2 switchport port-security mac-address sticky spanning-tree portfast mls qos trust dscp ! interface FastEthernet0/3 switchport access vlan 70 switchport mode access switchport voice vlan 100 switchport port-security maximum 2 switchport port-security mac-address sticky spanning-tree portfast mls qos trust dscp ! interface FastEthernet0/4 switchport access vlan 70 switchport mode access switchport port-security maximum 2 switchport port-security mac-address sticky spanning-tree portfast spanning-tree bpduguard enable ! interface FastEthernet0/5 ! interface FastEthernet0/6 ! interface FastEthernet0/7 ! interface FastEthernet0/8 ! interface FastEthernet0/9 ! interface FastEthernet0/10 ! interface FastEthernet0/11 ! interface FastEthernet0/12 ! interface FastEthernet0/13 ! interface FastEthernet0/14 ! interface FastEthernet0/15 ! interface FastEthernet0/16 ! interface FastEthernet0/17 ! interface FastEthernet0/18 ! interface FastEthernet0/19 ! interface FastEthernet0/20 ! interface FastEthernet0/21 ! interface FastEthernet0/22 ! interface FastEthernet0/23 ! interface FastEthernet0/24 ! interface GigabitEthernet0/1 switchport mode trunk spanning-tree portfast trunk mls qos trust dscp ! interface GigabitEthernet0/2 ! interface Vlan1 no ip address shutdown ! interface Vlan70 ip address 192.168.70.249 255.255.255.0 ip helper-address 192.168.50.2 ! ip default-gateway 192.168.70.1 ! ! ! ! access-list 1 permit 192.168.60.0 0.0.0.255 line con 0 ! line vty 0 4 access-class 1 in exec-timeout 2 0 login local transport input ssh line vty 5 15 access-class 1 in exec-timeout 2 0 login local transport input ssh ! ! end
so you have proved you know what a router config file looks like, what does that have to do with researching where a network issue is occurring... nothing in this scenario anyways not sure why you want me to tell you about the vlans, ip's and gateway address, ethernet ports, ect in your config files, nothing to do with this issue and not my expertise the FCC doesn't have access to router config files during initial issue research, so they do not come into play during that research, they may at a later point, but not in determining where the issue is happening, which is what the FCC is concerned with your trying to make this too hard on yourself, you do not need to know how an engine is built or what a cop is thinking to know a small town is setting up unfair speed traps, you only need to know where the unfair speed traps are happening... once you discover that, more research can be done for someone that claims to have your knowledge, you should know the stuff I am explaining to you, as it plain ol common sense .
You claim to know networking so explain the configs. If you can't explain them then you know nothing. The hell they don't. if you do not know the configs then you do not know how traffic is being treated. You're trying to oversimplify it. That's because you have no clue on the matter. I can go into any of those configs and make two or three changes that slow down the traffic and no one would know. - - - Updated - - - That's because I wrote them.
All your links, and what you think net neutrality is, is irrelevant. As I have repeatedly mentioned, the only thing that matters is those 320+ secret pages the FCC passed yesterday. You can pontificate all day and all night, it means nothing. You are supporting an undefined phrase and you hope it is what you dream it is.
publican, I tire of trying to explain why it can be done why don't you now explain to us why you think the FCC will not be able to tell if an ISP is sabotaging it's competitors, and why you believe it's an impossibility to determine this, with access to both the 'client sides' and 'server sides' of the issue, what ISP the issue is occurring on? .
The Administration has a little sound bite and the useful idiots take it hook, line, and sinker without realizing the unintended consequences of government intrusion into the most dynamic and free systems in existence.