Nessus 3.0 Locking Up DSL modem or service
Posted on 2006-04-09
My company put in a QWEST business DSL service at my residence so I could run security scans and penetration testing on off-hours. The QWEST dsl is 1500-down, 525-up with a block of static addresses bridged to my workstations. Nessus scans and vulnerability checks always lock up the DSL service or Modem. The modem must be rebooted to get back on line.
I also have a personal Roadrunner Cable account and I have no technical problems running the scans with cable, with the PC holding a roadrunner dhcp public address. (however, it is neccesary to have a reverse lookup record when you do contract security scanning and I have dynamic residential service . . it is also a violation of the service agreement on a residential account.)
Question: Is this a specific modem problem or a DSL problem ? I am not running NAT on the modem because that is a known issue with scans filling up the return path tables. I am using a Zoom DSL modem that I had sitting around rather than the Actiontec modem that is usually rented from QWEST.
If the cable modem doesn't have a lockup problem, it makes me believe the specific DSL modem has a problem. Any tips on how to determine this without replacing the modem ?