RayLopez99 said:
In the range 103.XX.XXX.XXX
Before there was not as many live IP addresses.
Changes to my network: I switched from a static IP address to a dynamic IP address with my ISP provider. I also let a third party who is not affiliated with the ISP company supervise the installation.
I am using the freeware "Advanced IP Scanner" by Famatech to check the live IP addresses, which have different .XXX extensions at the end but all the same MAC address--could this just be the DSL modem? (I have a DSL modem (with firewall) and a router 'downstream' of the DSL modem, then my PCs connect to this router). But if so, why so many, over 45 such IP addresses, at the moment?
Is there is a chance other people are sharing my DSL line and can read my data traffic? Or use my bandwidth? The guy who I let supervise my installation is generally honest but he does run a cybercafe as a business--and that is why I'm suspicious about the bandwidth stealing issue. Or, it could just be a coincidence to there now being a "Dynamic" connection.
RL
There's better than that. You can use Wireshark for tracing stuff.
http://en.wikipedia.org/wiki/Wireshark
*******
Let's take some scenarios.
DSL_Modem ---- Ray's Computer
If you do that, terminating PPPOE or PPPOA in software in Windows,
you'll see the full force of the Internet scanning efforts. That
is not a recommended config, even with Windows Firewall engaged.
Now, if we run this way...
DSL_Modem ---- router ---- Ray's Computer
That configuration has the advantage, that IPV4 NAT prevents a lot
of stuff from happening. If you're running IPV6, then you'll have
lost any advantage of IPV4 NAT.
To make my router secure here (that second hardware config),
I attempted to make it stealthy.
1) Do no Port Forwarding. That means, don't run any servers on
your desktop computer, and open ports in the router so that
the Internet can "see" your server. Similarly, don't use the
DMZ feature (port forwarding on steroids).
2) I add this rule to the router. When an IDENTD packet comes in,
it is forwarded to a non-existent node on my LAN. This is to
prevent an IDENTD packet from gaining a response from the router.
Allow identd WAN,* LAN,192.168.253.253 TCP,113
3) Some routers support dyndns. When you have a dynamic IP, it's possible
to "advertise" your new IP address, via Dynamic DNS. The router sends
the mapping of "ray.someisp.com" to a commercial operation like dyndns.org,
and the DNS tables are updated with your particulars. A person would
do this sort of thing, if running servers. So if you were running a
web server, your installer could enable dyndns in the router, so that
your IP mapping would be working. People who don't run servers, don't
particularly need dyndns (unless it's a vanity thing).
OK, with those out of the way, why are you seeing activity ?
You *can* see activity on the WAN (left hand side of router).
That would be normal. Any turkey can scan your external IP
address if they want.
You should not see random addresses on the LAN side. That's
a sign you're not running IPV4 NAT, you're Port Forwarding
or the like.
*******
One reason your public IP address gets scanned, is a function
of what the previous ISP customer was using the DNS address for.
Now that you're "dynamic", you get to see the after-effects of
what the previous customer was doing.
Say the address 123.123.123.123 was used by a previous customer,
and they were running BitTorrent. That's a peer to peer protocol,
with many participants.
What's bad about BitTorrent ? It's a persistent protocol, which
is not typically how you're supposed to design networking clients.
Say I'm running BitTorrent, and I turn off the power on my ADSL
modem. My ADSL session drops. The dynamic DNS address used, is put
back in the pool of addresses at the ISP. BitTorrent clients
continue to "hump" that IP address, even though they're not
getting a response.
Then, Ray dials up via his ADSL modem, and is assigned 123.123.123.123.
Well, what happens ? All the BitTorrent clients, dumb as they are,
continue to pound 123.123.123.123 at some well-known port numbers,
looking for the previous BitTorrent session.
When that happens here, I see "scanning" or "pounding" on the WAN side,
I just drop the lease and renew, and get a new IP address. I
repeat until I get a "clean one". If everyone using your ISP
is using BitTorrent, this could take a while. Note that the ISP
may have the ADSL set to disconnect for 15 minutes, if you release
and renew the lease, too many times in a short interval. (That's
"lease pounding protection", for the ISP itself.)
If you're running a router with IPV4 NAT, then the "pounding" should
show on the WAN light of the router. But no packets should be
forwarded to the LAN side.
*******
Your own client software can encourage communications. For example,
if you start Firefox running, and don't use it, Firefox will
talk to some Google node, to get a list of addresses for
filtering. So clients can do their own communications, for
various purposes. And then, you'd see some weird things
on the LAN side. Basically, Firefox downloads stuff on its own,
with no prompting from you.
And if you expect help, give a complete IP address, like the mythical
123.123.123.123 I made up above. I can't promise anything (as it looks
like zoneinfo is busted now), but knowing even one IP address
and doing a reverse translation, might give some idea what
kind of scan is happening.
HTH,
Paul