FireGryphon wrote:Well, all I want to do right now is get access to the router, but 192.168.x.1 doesn't get me anywhere. What should I do?
I will probably ditch the hub in the near future, but for the time being, I just want to use the router as an accessory to put one of my laptops on wireless using one of my IP addresses, and leave my other computers connected as they are. Is it possible to set it up this way?
Snake wrote:Phone box ---> DSL modem ---> Linksys router ---> Linksys hub ---> VoIP device
FireGryphon wrote:Snake wrote:Phone box ---> DSL modem ---> Linksys router ---> Linksys hub ---> VoIP device
The way VOIP works with my ISP is that I must have the DSL modem first in the chain and the VOIP device second, or the VOIP signal will not be properly split from the data signal.
FireGryphon wrote:There's no model number, but the manufacturer is Motorola. Doesn't help much, but there are no markings other than that on it (and s/n and such).
For the sake of setup, I'm running phone box ---> DSL modem ---> VOIP box ---> 54gl ---> single computer. Obviously, I'm on the 'net, but there's a long ways to go before this thing is setup the way I want. I'm currently trying to figure out how to get the the router to broadcast so my laptop (iBook G4) can pick up a signal from it, and I'm trying to see if I can route more than one static IP through the router.
What's the safest security authentication to setup? With WPA2, is it best to use TKIP+AES, or just AES?
I don't think there is a need to randomized the SSID, it will make new client configuration overly difficult. And on the subject of generating random text, I'll just go to Gibson's password generator.Snake wrote:Then, open up a document editor and type in RANDOM number/letters for the SSID, and RANDOM number/letters for the key (if you want to use hex only instead of plaintext, make sure the letters are A through F only). Then, remove excess letter/numbers until you get the right length of key (64 if hex IIRC).
Flying Fox wrote:I don't think there is a need to randomized the SSID, it will make new client configuration overly difficult.Snake wrote:Then, open up a document editor and type in RANDOM number/letters for the SSID, and RANDOM number/letters for the key (if you want to use hex only instead of plaintext, make sure the letters are A through F only). Then, remove excess letter/numbers until you get the right length of key (64 if hex IIRC).
FireGryphon wrote:Since my main computer (wired) connects using a static IP (and I'd rather not go through the 54GL with it), I end up having to go into the networking control panel in Windows and erase my network info every time I want to access the router's admin controls. Then when I'm done I have to re-enter my IP, gateway, DNS, etc. Is there an easier way with my setup to do this?
Flying Fox wrote:I suppose all your machines that have ISP-supplied IPs have their firewalls enabled? All those nodes are wide open on the internet in a manner of speaking. Why not just consolidate to have one external IP with machines connected behind the router? Don't want to port forward?
That aside, here is one approach you can do what you said you want to do. If you are not using all 4 of your ISP-supplied IPs, assign that to your router, essentially treating the router as a node like any of your "directly connected" device. Turn on remote administration on the router, and then you can access the router's admin interface using that "external" IP from your other wired computers.
This is really not a recommended approach since it means every other machine on the internet can try to access your router, either by knowing or with a port+IP scan. If the router firmware has a security vulnerability it is much easier to get owned since you essentially have port 80/443 open (for the remote admin). Another issue is that your wirelessly connected computers cannot access other machines in your "network" (it's not a LAN anymore since they all have externally assigned IPs behaving like standalone boxes on the edge of the internet) using internal IPs, and vice versa. The other direction is even more scary since you will have to port forward the File Sharing port(s) in order for the wired computers to talk to the wireless ones (since they will be behind the router). Seems like more trouble than it is worth.
Snake wrote:As noted previously, some Mac's have problems with hidden SSID's. Check to make sure yours is broadcasting to test this theory.
Delete the iBook's access point association and rebuild it.
If you were given a password that uses only the hexadecimal range of characters (which are: abcdef0123456789), put a dollar sign ($) before the password. These passwords are 10 characters long for 40-bit encrypted networks or 26 characters long for 128-bit encrypted networks. In a hexadecimal password, the dollar sign is called the Hex Escape. It notifies the software that the characters that follow it should be treated as a hexadecimal number. Other possible hex escapes are "0x" and "0X" (zero-x, and the "x" may be upper or lower case).
Example of 40-bit: $1234abcdef
Example of 128-bit: $12345678901234567890abcdef
Users browsing this forum: Google [Bot] and 1 guest