Yeah you're right about my netmask quote; it is as you suggest
255.****. It's was my gateway that had the 168.*** numbers.
And you're also right to urge caution on the neighbor's (primary)
side--but he is running wpaPersonal security and so far only he and I
know what his password key is.
Downstream from my router is another story; am running repeater bridge
for all the wireless stuff in the studio--which I guess means anyone in
radio range of my router can get the signal. You remind me that I need
to set up a security key for that virtual interface.
Thanx Allen for your thoughtful note,
m
Allen Brown wrote:
And that netmask value has got to go. I'm no router expert, but
I know this is wrong. What you told your router is that when it
accepts connections it will allow the binary bits represented by
the *zeros* in the mask to change. The mask should be something like
255.255.255.0. That says the first three bytes cannot change.
But the last byte can take any value. You can restrict this further
by using some other value in the last byte. But for most cases
the value I am offering will work.
BTW I would be concerned about the security problem that your
neighbour has created for himself. If you can login to his routers
configuration page, that is not good. I recommend that the
router be configured so it can only be configured from the
wired side of the network. But I'm slightly paranoid.
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
