Winsconsin firmware: DNS change doesn't stick
fcassia
I finally migrated my OSD to Arizona firmware... all went well, except
for one thing...
I have 192.168.100.249 for gateway AND DNS (the router runs a DNS proxy)
When I go to the Manual tcp/ip setup, I enter the IP address and
192.168.100.249 for Gateway
and
192.168.100.249 for DNS
I click save and....
DNS returns to 192.168.100.250 !
Any ideas??? I did notice when I ran the initial "assistant" that I
misread and pressed OK and it used DHCP, so DNS and router were set to
250 as default value.
When I entered Manual, I tried to change both to 249 but only gateway
was changed. The change to DNS ip address does not "stick" it is
replaced again with 250.
GRRRRRRRRRRRRRRRRR
Before someone asks, I'm running the latest greatest Arizona build, I
manually donwlaoded the latest upk file, saved to a SD, tried to "run"
it from the SD card and I was told I already had that version.
FC
Jason Shah
I had this problem once, and it couldn't write the updated entry because the internal storage was essentially overflowing...
fcassia
> Is your OSD's internal storage too full?
> I had this problem once, and it couldn't write the updated entry because the
> internal storage was essentially overflowing...
>
Thanks for the reply Jason.
I really don't know what to think. How does one overflow the internal
storage?. I didn't know you could save stuff there.
FC
Jason Shah
Well, in my case, I had been loading all those fun hacks into the OSD's memory, not onto the CF card. Turned out that was a bad idea.
Ugo Riboni
> misread and pressed OK and it used DHCP, so DNS and router were set to
> 250 as default value.
> When I entered Manual, I tried to change both to 249 but only gateway
> was changed. The change to DNS ip address does not "stick" it is
> replaced again with 250.
Not sure, but you may want to try and delete (from telnet)
/media/ext/data/sysconfig.ini
and then reboot the unit, it will give you the first boot "assistant"
again and you can choose fixed IP instead of DHCP.
If that fails too, remove that file again, remove also
/mnt/OSD/sysconfig/network/interfaces, reboot and repeat.
That said, changing the setting from the normal network settings at
any time (like you did) should've worked as well, so you may have
found a bug.
--
nero
fcassia
It feels as if it uses the DNS from DHCP no matter what, EVEN if yu
select Fixed IP. Because I had a router (used as switch, with the
router functionality disabled) on the LAN powered on and with DHCP
enabled and it had the .250 as DNS.
Now I disabled the DHCP functionality in that device, did a power
cycling on it, rebooted the OSD, tried to set DNS to .249 and it goes
back to .250. It's driving me mad.
I will telnet and delete the mentioned files. Also, I should mention
that while in shell mode on the OSD, I expect to press "back" and go
back to the main menu. that doesn't happen. I had to press another key
(I don't remember which one now) but it's not "back"... I thought for
a moment that I had entered a shell with no exit option. Oh, and EXIT
does nothing. Nor does QUIT.
FC
Ugo Riboni
The button to exit shell i think is HOME. //nero
Fernando Cassia
>
> That shell is very limited. If you want a real shell, telnet into the box :)
> The button to exit shell i think is HOME. //nero
I'm on telnet.
Where the !@#$$# is the DNS info? I'll just edit it manually...
/mnt/OSD/sysconfig/network $ cat interfaces
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
#default is to not bring the interface up.
# just in case users are on nfs booting.
auto eth0
iface eth0 inet static
address 10.26.6.50
netmask 255.255.255.0
gateway 10.26.6.249
/mnt/OSD/sysconfig/network $
-----------------------------------------------------------------\
FC
Fernando Cassia
Confirmed: there's an odd bug in there. No matter what I edit the DNS
goes back to 10.26.6.250.
Evidently there's some active DHCP server on my network (the network
laser printer? one of my NAS hard drives? I don't care which one).
Erasing config files on the OSD doesn't make a difference. It lets you
change the IP address, default gateway, netmask, etc. But when it
comes to the DNS... it seems to get whatever is given by any active
DHCP server on the LAN...
Sheesh!!
FC