Can't change LAN network to 192.168.0.1 (255.255.255.0) on a fresh install

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install 
tomato-E3000USB-NVRAM60K-1.28.0495MIPSR2-Toastman-VLAN-RT-N-VPN-NOCAT.bin
2. On Basic > Network change br0 to 192.168.0.1 (and corresponding DHCP address 
ranges)

What is the expected output? What do you see instead?

Expect it to succeed but get an error dialog saying that subnet is already in 
use.  It doesn't seem to be in use anywhere.

What version of the product are you using? On what operating system?

tomato-E3000USB-NVRAM60K-1.28.0495MIPSR2-Toastman-VLAN-RT-N-VPN-NOCAT.bin

Please provide any additional information below.

Original issue reported on code.google.com by glen.he...@gmail.com on 7 Feb 2012 at 6:01

[GoogleCodeExporter]

Thanks for your report but unfortunately, I couldn't reproduce it on any recent 
builds of Tomato Teaman-RT (with VLAN GUI enabled). BTW - I also checked what's 
on the public git repo, looking for any differences between the code on branch 
Teaman-RT and Toastman-RT/Toastman-RT-N... but found no significant differences.

This error you're getting: is it when you try to just 'change' something in the 
basic-network page or... when you try to 'save' all your settings on that page?

Original comment by augu...@bott.com.br on 9 Feb 2012 at 4:56

• Changed state: PendingFeedback

[GoogleCodeExporter]

Hi,

If I remember correctly I received a dialog when I tried to make the change 
(before hitting save).  I also ran into a similar issue with the non-VLAN build 
where I changed my LAN to 192.168.0.1/24 and then on the Port Forwarding page I 
would get an iptables-restore error. This was easy to reproduce and may be 
related. 

Thanks.

Original comment by glen.he...@gmail.com on 9 Feb 2012 at 6:43

[GoogleCodeExporter]

Again - thanks for your feedback. However, I'm afraid there might be a few 
things worth clarifying before proceeding any further:

a) unfortunately, I've been unable to reproduce the issue being reported 
(setting LAN address to 192.168.0.x/24). Unless there's some way to 
cause/trigger it to happen, there's not much to look into... to eventually fix 
any problems, don't you agree?

b) with that said, I must ask: can you please provide more information about it 
(i.e. steps will reproduce the problem, as detailed as possible).

c) if you've identified/found/experienced some sort of new/different problem, 
then please do feel free to create a new issue so we can investigate/check it 
out and have it documented properly.

Thanks!

Original comment by augu...@bott.com.br on 11 Feb 2012 at 12:39

[GoogleCodeExporter]

Issue cannot be reproduced, closing due to inactivity.

Original comment by augu...@bott.com.br on 24 Mar 2012 at 11:10

• Changed state: Invalid