November 29, 2010
Mucking around with TCP/IP always makes my head hurt.
I made space for the Netgear hub on my computer table. Before I can even think of trying to mess around with Wifi, though, I have to make it see my LAN.
It's got four ethernet connectors labeled "LAN" and one labeled "WAN". The WAN connector is supposed to go to my cable modem, and if I was going to use it in router/firewall mode, that's what I would do, I guess. But for the time being I don't want to mess with that.
So my bright idea was to connect its WAN plug to my existing ethernet hub.
In order to set it up, there needs to be a computer connected to one of its LAN connectors, and I was using Alcyone (the ASUS computer) to do that. The Netgear box defaults to 192.168.1.1 and its NAT defaults to a bank of IPs in the 192.168.1.* range. All pretty standard.
Because of some confusion, since resolved, when I got Deneb (the WHS NAS) I reset my entire LAN to use IPs in 169.254.1.*. So Regulus (the Qube) is hardwired to be 169.254.1.1 and Deneb (the WHS) is hardwired to be 169.254.1.2.
I decided the netgear hub (not yet named, but eventually to be "Railgun") should be 169.254.1.3 and 169.254.1.4, and managed to get that set up.
But nothing I've tried has made it so that the netgear box can see my LAN or see the internet. Nada.
I'm tired of screwing with it right now. I'll give it another shot tomorrow.
Posted by: Steven Den Beste in Computers at
07:15 PM
| No Comments
| Add Comment
Post contains 265 words, total size 1 kb.
Enclose all spoilers in spoiler tags:
[spoiler]your spoiler here[/spoiler]
Spoilers which are not properly tagged will be ruthlessly deleted on sight.
Also, I hate unsolicited suggestions and advice. (Even when you think you're being funny.)
At Chizumatic, we take pride in being incomplete, incorrect, inconsistent, and unfair. We do all of them deliberately.
How to put links in your comment
Comments are disabled. Post is locked.18 queries taking 0.0122 seconds, 16 records returned.
Powered by Minx 1.1.6c-pink.