Crion

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

My guess is they're doing packet shaping.  

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

So I feel I must correct a misconception that I've seen circulating the internet regarding this.  This is a vulnerability in the implementation of WPA2 by various manufacturers, not the WPA2 protocol itself.  Practically, yes everything still needs to be patched but the implications of the two are vastly different.  The first can be fixed by software updates whereas the latter cannot and requires a new protocol.  
 
I've spent most of this morning reading the paper and various vendor product advisories so to summarize the details of this attack:
1) Exploits a Key Reinstallation attack through one of several vectors (4-way handshake, Group Key Exchange, or 802.11r [Fast BSS Transition])
2) Requires a Man-in-the-Middle (MITM) attack
3) Both client and AP/infrastructure are affected and both must be patched to fully mitigate this exploit
4) Affects both WPA2-PSK and WPA2-Enterprise as the vulnerability exists in the implementation of the protocol, not the authentication method
5) Most vendors have already issued patches for this vulnerability as they have known about it for months.  

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

No.  A router can have a security vulnerability which can lead to it getting compromised.  This does not equal malware infection.

No.  A router can have a security vulnerability which can lead to it getting compromised.  This does not equal malware infection.

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

There is no difference between ADSL (Asymetric DSL) and DSL as the latter term is often used to the refer to the former.  There is another type of DSL called VDSL (very high bit-rate DSL) which is faster than your typical ADSL speeds.  An example in the US of VDSL would be AT&T U-Verse.  
 
Cable is often what is known in the industry as an HFC or Hybrid Fiber Coaxial network as there is usually fiber up to a node in your neighborhood which then branches out as Coax from there to your home and modem.  
 
HFC is generally faster and has lower latency than the other two but it all depends on things like your ISP and how far you are from your closest node (this applies to any of the above).  So which is the best is really not a good question to ask.
 
 
Short answer, no.  You cannot replace the Coax cable on your modem with a fiber cable.  They are not interchangeable and on top of that unless the network gear at your home costs several thousand USD, you probably can't even directly connect to something like 50 micron fiber without a fiber converter.  
 
EDIT (Detailed Response):  Fiber is generally only found in cases where you have extremely high bandwidth/low latency requirements or very long distances to cover to transmit the data or enterprise/datacenter networking.  Copper and Coax have a distance limit at which point the signal degrades to the point where it cannot be interpreted by the receiving equipment.  In the case of standard CAT6 ethernet, it's somewhere around 100 meters if I remember correctly.   I don't remember the numbers for coax given I only work with it at home.  
 
As to why you can't connect fiber to your modem, both 50 micron and 62.5 micron fiber usually have one of several types of standard connectors: SC, ST, LC, and others but those are the most common that I've run into.  None of these work with a cable modem for the obvious reason of the cable modem doesn't support any of these connectors.  There may be some residential ISP somewhere in the world that actually comes in directly fiber, but as far as I've ever run into in my 6+ years as a network admin, I've only come across fiber from the ISP at business grade connections such as Metro Ethernet and network gear such as Juniper SRX or M series routers or the trusty old Cisco 7204.  

There is no difference between ADSL (Asymetric DSL) and DSL as the latter term is often used to the refer to the former.  There is another type of DSL called VDSL (very high bit-rate DSL) which is faster than your typical ADSL speeds.  An example in the US of VDSL would be AT&T U-Verse.  
 
Cable is often what is known in the industry as an HFC or Hybrid Fiber Coaxial network as there is usually fiber up to a node in your neighborhood which then branches out as Coax from there to your home and modem.  
 
HFC is generally faster and has lower latency than the other two but it all depends on things like your ISP and how far you are from your closest node (this applies to any of the above).  So which is the best is really not a good question to ask.
 
 
Short answer, no.  You cannot replace the Coax cable on your modem with a fiber cable.  They are not interchangeable and on top of that unless the network gear at your home costs several thousand USD, you probably can't even directly connect to something like 50 micron fiber without a fiber converter.  
 
EDIT (Detailed Response):  Fiber is generally only found in cases where you have extremely high bandwidth/low latency requirements or very long distances to cover to transmit the data or enterprise/datacenter networking.  Copper and Coax have a distance limit at which point the signal degrades to the point where it cannot be interpreted by the receiving equipment.  In the case of standard CAT6 ethernet, it's somewhere around 100 meters if I remember correctly.   I don't remember the numbers for coax given I only work with it at home.  
 
As to why you can't connect fiber to your modem, both 50 micron and 62.5 micron fiber usually have one of several types of standard connectors: SC, ST, LC, and others but those are the most common that I've run into.  None of these work with a cable modem for the obvious reason of the cable modem doesn't support any of these connectors.  There may be some residential ISP somewhere in the world that actually comes in directly fiber, but as far as I've ever run into in my 6+ years as a network admin, I've only come across fiber from the ISP at business grade connections such as Metro Ethernet and network gear such as Juniper SRX or M series routers or the trusty old Cisco 7204.  

The listed "maximums" for WiFi standards are theoretical and in no way reflect real world performance. With headers, trailers, padding, interference, CSMA/CA, and STDM layered on top of the rated "theoretical maximum", real world speeds are just far lower.

There is no difference between ADSL (Asymetric DSL) and DSL as the latter term is often used to the refer to the former.  There is another type of DSL called VDSL (very high bit-rate DSL) which is faster than your typical ADSL speeds.  An example in the US of VDSL would be AT&T U-Verse.  
 
Cable is often what is known in the industry as an HFC or Hybrid Fiber Coaxial network as there is usually fiber up to a node in your neighborhood which then branches out as Coax from there to your home and modem.  
 
HFC is generally faster and has lower latency than the other two but it all depends on things like your ISP and how far you are from your closest node (this applies to any of the above).  So which is the best is really not a good question to ask.
 
 
Short answer, no.  You cannot replace the Coax cable on your modem with a fiber cable.  They are not interchangeable and on top of that unless the network gear at your home costs several thousand USD, you probably can't even directly connect to something like 50 micron fiber without a fiber converter.  
 
EDIT (Detailed Response):  Fiber is generally only found in cases where you have extremely high bandwidth/low latency requirements or very long distances to cover to transmit the data or enterprise/datacenter networking.  Copper and Coax have a distance limit at which point the signal degrades to the point where it cannot be interpreted by the receiving equipment.  In the case of standard CAT6 ethernet, it's somewhere around 100 meters if I remember correctly.   I don't remember the numbers for coax given I only work with it at home.  
 
As to why you can't connect fiber to your modem, both 50 micron and 62.5 micron fiber usually have one of several types of standard connectors: SC, ST, LC, and others but those are the most common that I've run into.  None of these work with a cable modem for the obvious reason of the cable modem doesn't support any of these connectors.  There may be some residential ISP somewhere in the world that actually comes in directly fiber, but as far as I've ever run into in my 6+ years as a network admin, I've only come across fiber from the ISP at business grade connections such as Metro Ethernet and network gear such as Juniper SRX or M series routers or the trusty old Cisco 7204.  

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".

Oh I could go on and on about this since I was a tech for a while and now am a sysadmin.
1. We saw an increase in phishing spam sent to our users wanting them to "confirm their accounts" to "keep them open". We send out an official announcement saying that we've noticed an increase in spam asking for users passwords and to not give out passwords in an email if asked. We end up getting about 20 users reply to the announcement with their username and password... fail...
2. Probably the funniest moment I've ever had in tech support was when someone walked into the place I was working holding an ethernet cable by both ends. He claimed that his machine had gotten infected with a virus and that he reinstalled Windows and it came back so he was convinced that the virus was "stuck in his ethernet cable" and was holding the ends up because he didn't want it to "fall out".