wa8yxm wrote:
Only difference I'd make is the last octet. Insted of 002 I usually go with something like 202. Darn few home networks assign a 202 but many assigna a 002.
But if it's workign.. Don't fix it. So file for future note
I have a restaurant I visit where they are often "Sold out" on their LInksys home/small office router (That is all assignable IP addresses are assigned)
This computer connects to that one as 201 (Assigned are 100-199 in case you wonder. Normally a linksys just does 100-49 but .. Someone edited it so there were 100 addy's. changed the lease time last visit too.
It's surprising how many wifi routers have IP pools that are smaller than their subnet. A common trick is to use an address outside the pool (guess) but within the subnet.
After all, default traffic outside the subnet goes directly to gateway on most configurations ;)
Even when DHCP RSVP is used by MAC Address, more often than not, not actual restriction is in place other than DHCP. So manually hardcode an IP address to a non-windows machine that overlaps a device on the network already (ie servers anyone?) and wait for that other device to give up and disable the IP interface and keep banging until you steal that IP address. If you picked the correct device to impersonate, you now have massive network privs.
Add to it that many (most?) SOHO routers allow MAC Address cloning. Grab any device already on the net, clone the MAC and IP address, and you're now on the net!
Anyone still think networks (especially public access) are secure?
...and this is 6th grader kind of level stuff. Start pushing TMP stuff and life gets really interesting, LOL.
Multi-homed PCs can be very vulnerable for the network it is attached to, be careful, OP ;)
