Marc Chamberlin wrote:
Togan, James, you both pointed out the same thing, which I was kinda afraid of, that the 169.254.x.x network is a non-routable IP address range. I have encountered issues with this before and so far have not come up with a good answer. My trouble is that the devices on this network consist of some Motorola Canopy wireless access points and subscriber modules. These sit on towers and are not easily accessible, and the trouble is that if there is a power cycle, then these devices reboot and come up with a default IP address on the 169.254.x.x network. This is how I get my internet access to my SOHO network at home/business, I live way out in the woods! (I have tried to look into upgrading the firmware of these devices but so far no joy in figuring out how to do so, in order to get around this problem.)
Is there no non-volatile memory for storing configuration? If not, I'd consider those devices to be defective out of the box. There is absolutely no excuse for that sort of nonsense.
I set up the router B for the 192.168.20.x network to handle smart cell phones and some associated devices and get them off of the gateway computer and internal network (192.168.10.x) used for my home/business computers and servers. This is an attempt to improve phone call drops and intermittent issues we were having when the cell phones were on the same network as all the rest of our computers.
Greg - Yes I think you see/understand what I am trying to do with having a separate network set up outside of my gateway computer. It sounds to me that from what you are saying, even if I could switch the 169.254.xx network address over to something like a 10.x.x.x network I would still have routing problems. Hmmmm, anyone got any ideas on how to go about solving this? Suggestions on wireless routers I can use? Right now I am using Rosewill wireless routers and I don't see any settings that allow me to override routing rules and still provide NAT capabilities.
As I menitoned, RFC1918 addresses, which include 10.x.y.z, are routable. They just can't be routed over the public Internet. So, you'd just need NAT to resolve that issue. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org