WRT54GS Default Network

Archived from groups: (More info?)

Hi all,
I have a WRT54GS which of course defaults to a 192.168.1.0 class C
network.

What I would like to have is a default network in a 172.24.0.0 range
(specifically a 172.24.4.x range) which is really a class B network.

Is there anyway to convince the WRT54GS to supply such an addres?
And can get the builtin DHCP to server addresses in the same range?

I have tried setting the routers IP through the config page, but after
doing so I could not ping the router at the expected address (and yes
my computer was also set for the same network)

Regards
Peter

Archived from groups: (More info?)

peterem2000@hotmail.com wrote:

> Hi all,
> I have a WRT54GS which of course defaults to a 192.168.1.0 class C
> network.
>
> What I would like to have is a default network in a 172.24.0.0 range
> (specifically a 172.24.4.x range) which is really a class B network.

OK, I'll bite. Why? I did have trouble last week with the defaults - every
time I took my laptop into work a rogue DHCP server on 192.168.1.1 gave me
the IP my router gave me the night before. I ended up changing my router
to 192.168.22.1, because I might wait weeks before network admin tracks
down this server. Anyway, having my router dish up anything unusual will
likely solve that problem.
>
> Is there anyway to convince the WRT54GS to supply such an addres?
> And can get the builtin DHCP to server addresses in the same range?

If you're using sveasoft firmware, Talisman lets you change it to _any_
class C address in the 192.168.0.0 range. I think you'd have to dig into
the underlying Linux configuration to change it to anything else (which you
_can_ do).

--
derek

Archived from groups: (More info?)

well I tried setting the device to a 172.24.4.1 address. As you
mentioned the device only really allows for a /24 network, as the best
mask you can get is 255.255.255.0

I set those parameters via the admin page, and then set my laptop to
172.24.4.2 255.255.255.0 but I could not ping the WRT54GS .. I tried
this a few times to see that I done it correctly, but in the end
reverted back to my 192 adddress

Archived from groups: (More info?)

Yves Konigshofer wrote:
> What was your computer's Gateway address set to?
>

Thanks .. that was it. While I had my laptops port set to a static
address that matched the network the router was on, I didn't realise
that I needed a gateway address. I assumed that I would not need one
as I was pinging an address on the same segment. Obviously not. All
my issues are solved now, and my *&^%& work software likes my laptop
once again.