Sign up
Vonage Forum Menu
The Vonage Forums
Vonage VoIP Forum
Vonage Forum Archive
Vonage Canada
Vonage UK
Vonage Stock
Fax, Tivo & Alarms
Hard Wiring
Number Transfer
V-Phone & SoftPhone
VoIP Feature Request
Vonage TV Ads
International Rates
Forum Suggestions
Report a Bug
The Cafeteria
Forums Archive
All Vonage News
Vonage In The News
Press Releases
Forum Digest
News Archives
Vonage Sign Up Info
Vonage Features
Vonage Area Codes
Vonage FAQ
Vonage Reviews
VoIP Speed Test
Vonage Toolbar
Network Setup
Wiring & Installation
Vonage 911
Business Account
VoIP Acronyms
VoIP Advertising
Wi-Fi Phone
Contact Support
Member Registration
Member Login
Member List
Your Account
Private Message
Forum Faqs
Recommend Us
Website Feedback
Forum Syndication
Forum Newsletter
Search Using Google
Search Forums
Search News
Forum Speed Dial
Vonage Forum
Forum Community
The Vonage Forums
Vonage VoIP Forum
Forum Archive
Vonage Canada
Vonage UK
Vonage Stock
Fax, Tivo & Alarms
Hard Wiring
Number Transfer
V-Phone & SoftPhone
Feature Request
Vonage On TV
International Rates
Forum Suggestions
Report A Bug
The Cafeteria
All Archives
Vonage News
All Vonage News
In The News
Press Releases
Forum Digest
News Archive
Vonage Information
Sign Up Info
Vonage Features
Area Codes
Vonage FAQ
Vonage Reviews
VoIP Speed Test
Vonage Toolbar
Network Setup
Wiring & Installation
Vonage 911
Business Account
VoIP Acronyms
VoIP Advertising
Wi-Fi Phone
Contact Support
Member Services
Registration
Member Login
Member List
Your Account
Private Messages
Forum Faq's
Recommend Us
Website Feedback
RSS Syndication
Forum Newsletter
Search
Search Using Google
Search Forums
Search News
Vonage Forums
Why is 216.115.24.192 port scanning
Goto page
1
,
2
Next
Vonage® VoIP Forum - Vonage News, Reviews And Discussion
»
Vonage Forum Archive
Author
Message
Tallance
New Forum Member
Joined: Dec 02, 2005
Posts: 4
Posted:
Fri Dec 02, 2005 3:33 pm
Post subject: Why is 216.115.24.192 port scanning
When a consultant checks his phone list on the vonage.comat my location. A port scan from 216.115.24.192 is logged at our firewall. There is no
Vonage
phone being used on the network (that is known anyway). It happens when he logs into check his account.
Why is this happening?
Thanks,
Tal
NateHoy
Vonage Forum
MVM
Joined: Nov 01, 2005
Posts: 2257
Location: New England
Posted:
Fri Dec 02, 2005 3:50 pm
Post subject: Re: Why is 216.115.24.192 port scanning
Tallance wrote:
When a consultant checks his phone list on the vonage.comat my location. A port scan from 216.115.24.192 is logged at our firewall. There is no
Vonage
phone being used on the network (that is known anyway). It happens when he logs into check his account.
Why is this happening?
Thanks,
Tal
That IP address (according to Arin) is owned by
Vonage
.
What do you mean by "checks his phone list"? Do you mean his voicemail? Hmm. That "should" just be a regular web page, albeit an SSL one.
What port is being scanned?
_________________
Comcast Cable (3m down / 256k up) -> Linksys BEFCMU10 v2 (DOCSIS 1.0) -> WRT54G v4 ("Tomato" firmware) -> the rest of my network including a WRTP54G (Firmware: 5.01.04)
My
Vonage
Self-Help Guides:
http://vonage.nmhoy.net
Tallance
New Forum Member
Joined: Dec 02, 2005
Posts: 4
Posted:
Fri Dec 02, 2005 4:18 pm
Post subject:
The person logs onto the
Vonage
site and looks at the phone number list of sent and received calls for his
Vonage
phones.
I know that the ip is
Vonage
that is why I post the question here, hoping that some else had noticed it, or knew why.
There appears to be 1 to 2 port scans per times he access the
Vonage
web site.
The port scans
[22/Nov/2005 11:01:23] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 65281, 65282, 65283, 65284, 65285, 65286, 65287, 65288, 65289, 65279, ..."
[22/Nov/2005 11:01:43] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 65281, 65282, 65283, 65284, 65285, 65286, 65288, 65289, 65303, 65279, ..."
[22/Nov/2005 11:02:19] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 65303, 65313, 65314, 65316, 65318, 65319, 65320, 65321, 65322, 65323, ..."
[22/Nov/2005 11:02:59] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 65313, 65314, 65316, 65318, 65319, 65320, 65321, 65323, 65334, 65335, ..."
[29/Nov/2005 10:02:55] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61003, 61007, 61008, 61009, 61010, 61011, 61012, 61013, 61014, 61015, ..."
[29/Nov/2005 10:03:15] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61003, 61007, 61008, 61009, 61010, 61011, 61012, 61013, 61014, 61015, ..."
[29/Nov/2005 10:03:55] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61003, 61007, 61008, 61009, 61010, 61011, 61012, 61013, 61014, 61016, ..."
[29/Nov/2005 13:18:38] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 51567, 51569, 51571, 51573, 51574, 51578, 51580, 51581, 51582, 51583, ..."
[29/Nov/2005 13:19:38] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 51578, 51580, 51581, 51582, 51583, 51584, 51585, 51587, 51590, 51591, ..."
[01/Dec/2005 15:33:37] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61466, 61470, 61473, 61474, 61475, 61477, 61478, 61479, 61481, 61482, ..."
[01/Dec/2005 15:33:57] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61466, 61470, 61473, 61474, 61475, 61477, 61478, 61479, 61481, 61482, ..."
[01/Dec/2005 15:34:37] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61466, 61470, 61473, 61474, 61475, 61477, 61478, 61479, 61481, 61482, ..."
[01/Dec/2005 15:38:57] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61640, 61642, 61643, 61644, 61645, 61647, 61648, 61650, 61652, 61653, ..."
[01/Dec/2005 15:39:47] PORTSCAN hostip="216.115.24.192" log="protocol:TCP, source: 216.115.24.192, destination: xx.xxx.xx.xx, ports: 61640, 61642, 61643, 61644, 61645, 61647, 61648, 61649, 61650, 61652, ..."
NateHoy
Vonage Forum
MVM
Joined: Nov 01, 2005
Posts: 2257
Location: New England
Posted:
Fri Dec 02, 2005 4:57 pm
Post subject:
WOW! Is that a partial extract? As in, does it port scan the ENTIRE port range?
Even if it's just the ports you posted... Holy cow! There's no reason for
Vonage
do be doing that to serve up a web page. Good catch.
Vonage
, even if it was contacting the phone adapter for some bizarre reason, or trying to, should already have a different IP address for the adapter, and shouldn't be anywhere NEAR those ranges, and would have absolutely no reason to be pumping port scans to ports their adapters don't even use.
I'd have your consultant call Customer Service directly on this one, and insist on going up the support chain a couple of steps. Straaaaange.
_________________
Comcast Cable (3m down / 256k up) -> Linksys BEFCMU10 v2 (DOCSIS 1.0) -> WRT54G v4 ("Tomato" firmware) -> the rest of my network including a WRTP54G (Firmware: 5.01.04)
My
Vonage
Self-Help Guides:
http://vonage.nmhoy.net
KDWycha
Vonage Forum Evangelist
Joined: Jan 19, 2005
Posts: 605
Location: Tampa, Florida USA (813)
Posted:
Fri Dec 02, 2005 6:06 pm
Post subject:
I should contact one of my many consultants and see if i am being probed too.
_________________
Kevin Wycha
Vonage
Subscriber Since: Jan 17, 2005
Linksys RT31P2 Router/ATA
Motorola SB5100 Cablemodem
Roadrunner TampaBay (10mb down/1mb up)
---
w00t!
Tallance
New Forum Member
Joined: Dec 02, 2005
Posts: 4
Posted:
Mon Dec 05, 2005 1:40 pm
Post subject:
Yes that is a partial , it does appear to scan more, but that is all the firewall is logging to the accessible log. I will contact my consultant and see what happens. Thanks for the confirmation that something is wrong.
ColdGin
Vonage Forum Evangelist
Joined: Oct 03, 2005
Posts: 423
Posted:
Mon Dec 05, 2005 2:20 pm
Post subject:
yes the phone device actually sends us its IP address and the open port from behind the NAT router. I can look at a devices debug log and see 192.168.x.x.:459382 or something similar. I have no idea why the site would be scanning those IPs.
Of course anyone I ask here about that looks at me like I just suggested a coleslaw wrestling tournament right here in the call center and then they yell at me and chase me back to my phone. So no luck on my initial inquiries...
j-card
Vonage Forum Senior
Joined: Nov 23, 2005
Posts: 119
Location: Victoria, British Columbia, Canada
Posted:
Mon Dec 05, 2005 2:30 pm
Post subject: Port Scan
How does one check for a port scan?
I have a router, but I don't know how to check for port scans...
Would be interesting to see if this is happening here as well...
_________________
J-Card
-------------------------------------------------
"If you can't dazzle with brilliance, baffle with bull$&!#"
Please vote on how you would rate your service! Lets see what people really think!
Canada
UK
US
NateHoy
Vonage Forum
MVM
Joined: Nov 01, 2005
Posts: 2257
Location: New England
Posted:
Mon Dec 05, 2005 2:50 pm
Post subject: Re: Port Scan
j-card wrote:
How does one check for a port scan?
I have a router, but I don't know how to check for port scans...
Would be interesting to see if this is happening here as well...
Generally, you have to be running a router sophisticated enough to log all connection attempts. In the logs, just look for a whole list of connection attempts from the same IP address to all different ports.
_________________
Comcast Cable (3m down / 256k up) -> Linksys BEFCMU10 v2 (DOCSIS 1.0) -> WRT54G v4 ("Tomato" firmware) -> the rest of my network including a WRTP54G (Firmware: 5.01.04)
My
Vonage
Self-Help Guides:
http://vonage.nmhoy.net
navydavy2001
Vonage Forum
MVM
Joined: May 26, 2005
Posts: 1123
Posted:
Mon Dec 05, 2005 2:58 pm
Post subject:
The WRT-54G v4.20.7 Linksys Firmware seems to have a log under Admin. Kinda stripped down, but it shows incoming and outgoing. I see lots of www, and even a couple of tftp entries from when I backed up my Cisco router IOS's.
Display posts from previous:
All Posts
1 Day
7 Days
2 Weeks
1 Month
3 Months
6 Months
1 Year
Oldest First
Newest First
Vonage® VoIP Forum - Vonage News, Reviews And Discussion
»
Vonage Forum Archive
Goto page
1
,
2
Next
Jump to:
Select a forum
Vonage® VoIP Forums
----------------
Vonage
Vonage Forum Archive
Vonage Canada
Vonage UK
Vonage Stock
Fax - Tivo - Alarms
Hard Wiring - Installation
LNP – Local Number Portability
Vonage V-Phone & SoftPhone
VoIP Feature Wish List
Vonage TV Commercials
International Rates
Forum Suggestions - Open Topics
----------------
The Cafeteria - Any Non Vonage Topic
Forum Suggestions - Comments
Report A Forum Bug
You
cannot
post new topics in this forum
You
cannot
reply to topics in this forum
You
cannot
edit your posts in this forum
You
cannot
delete your posts in this forum
You
cannot
vote in polls in this forum
All times are GMT - 5 Hours