Tim wrote:
> The manual says the device has IP address 192.168.10.1,
> but as far as I can see you have to have a machine
> running 192.168.10.something to see the device's web-page?
> I know 192.168.10.* is an allowed address,
> but is it so popular that one can assume it is in use?
Within a totally isolated LAN, you can use almost any IP that you
want
to. But once you join other networks (LAN, WAN, or internet), you have
to use the ones reserved for private use (such as 192.168.x.y, but there
are a few others, as well - 10.x.y.z, 172.16.x.y to 172.31.x.y).
Taking the common 192.168.x.y one, the first three quads have to be the
same (for the usual 255.255.255.0 netmask) to be able to talk between
themselves (the netmask sets the boundary between what's considered
inside or outside; and to reach what's outside, you have to go through
the gateway).
So, if you want to talk to something at 192.168.10.1, you'll either need
to be in the same 192.168.10.x subnet, or you'd need to change the
netmasks on both devices to 255.255.0.0.
Thanks very much, that clarifies the situation completely.
Actually, the repeater is now working, surprisingly well.
The secret was that I had to run the wizard on the repeater's web-page,
which asked me for the router password.
But as you say, I had to set the ethernet IP address on my laptop
to 192.168.10.5 or similar.
You could create a network connection on your laptop that doesn't
use
DHCP, so you can preset your laptop to be 192.168.10.something, to play
with that device, while you configure things.
Yes, I probably should have edited /etc/sysconfig/network-scripts/ifcfg-*
to turn off DHCP.
(NetworkManager has the annoying habit of inventing new entries here -
I see there is one for ifcfg-New_802-3-ethernet_connection.)
Anyway, all's well that ends well.
--
Timothy Murphy
gayleard /at/
eircom.net
School of Mathematics, Trinity College, Dublin