No IP address assigned after installing Alt-F

[Chris Cobb]

Hi - I've installed Alt-F-0.1RC4 on my DNS-323-rev-A1. Previously it was using v1.10 of the vendor's firmware. The install appeared to complete okay and it took several hours to check the disks as expected.

The problem is that I can't now connect to it. I've checked that Alt-F is running (by keeping pressed the power button and seeing the orange light left/right). I finally tried resetting the device (20+ secs pressing the back button.

After each step I've checked devices connected to my router and the DNS-323 doesn't appear.

I've read the FAQ, wiki and search the forum but have hit a brick wall. Can anyone help out?

[Cohech]

Additional: one time while trying to access my router (via IP address) the Alt-F Status Page appeared! I therefore assume they're both trying to use the same IP address (192.168.1.254).

What I don't understand is why the DNS-323 isn't picking up an IP address from the router, which is running DHCP. All other devices are getting IP addresses from the router without a problem.

[João Cardoso]

On Friday, September 12, 2014 9:40:38 PM UTC+1, Cohech wrote:

Additional: one time while trying to access my router (via IP address) the Alt-F Status Page appeared! I therefore assume they're both trying to use the same IP address (192.168.1.254).

Try using another network cable.

Yes, I know, but when you have excluded all the reasonable reasons, what is left must be the culprit, as impossible as it seems (loose Sherlock Holmes saying)

[Cohech]

Tried three different cables, plugged into switch (as original configuration prior to Alt-F) and also plugged directly into router - no difference, still not working.

Also tried excluding the router (which appears to have the IP conflict) by simply plugging in laptop and DNS-323 into switch and turning off the router. No joy with this though either.

After each step not working I've tried rebooting the DNS-323 and then resetting it. Nothing seems to work.

I'm sure it must be a networking issue though, as Alt-F reports it's running fine (long push on power button).

Any suggestions welcome, as currently the DNS-323 is completely useless - I can't even revert back to the manufacturers firmware.

Thanks!

[João Cardoso]

On Saturday, September 13, 2014 3:32:14 PM UTC+1, Cohech wrote:

Tried three different cables, plugged into switch (as original configuration prior to Alt-F) and also plugged directly into router - no difference, still not working.

Also tried excluding the router (which appears to have the IP conflict) by simply plugging in laptop and DNS-323 into switch and turning off the router. No joy with this though either.

If you have long (>20sec, say 25 seconds) pressed the back reset button, clearing all flashed-saved settings, on power-up it will try to get a DHCP lease; if it can't get one in 3 seconds, it will try to ping 192.168.1.254 and if receives a reply it will try 192.168.1.253, ... until 192.168.1.230.

So if you use a direct-cable connection to a PC with a static ip of, say 192.168.1.100 and no DHCP server running, you can find it at 192.168.1.254

[added: this also means that if you powerup the box with the network cable unplugged it will set itself to 192.168.1.254]

[Cohech]

(Apologies for delay - been away)

Tried a direct cable connect via Mac laptop but couldn't get it working. Then tried via Windows PC and connected via 192.168.1.254 - at last, party time!

I then updated the IP address (so it doesn't conflict with the router) to 192.168.1.205 and saved the changes. I now can't access the Alt-F page using the 205 or 254 addresses. Have tried rebooting the DNS-323 and clearing my browser cache and restarting it.

I've recovered the situation by 20+ sec rear button reboot and am back to 192.168.254.

Any reason why I can't successfully change the IP address? 

[João Cardoso]

I can't really help more. The code sequence for Alt-F to get an IP is:

# get an ip using the following priority:

# 1st, use kernel cmd line ip= (kexec or fonz reloaded) -- not applicable

# 2nd, use defaults stored in flash, either DHCP or a static IP -- there are none when clearing settings (or after a +20 sec reset)

# 3d, try to read vendor sib.conf -- there are none after clearing settings the first time (or after a +20 sec reset)

# 4th, try to use a dhcp server

# 5th, find and use a non-used ip address from 192.168.1.254 to 230 range

so:

-after saving settings, only 2 applies and no fallback exists

-after clearing settings 4 applies and if it fails 5 is used as a fallback.

-when using 5, If no network cable is attached (at boot time) it will use 192.168.1.254.

If you find that after clearing settings (and with the network cable attached at *boot* time) the DHCP server is not used (4 fails) and the box gets 192.168.1.254 when it is already assigned to another host, it has to be a network issue.

Perhaps the DHCP server is slow to answer and 4 is readily abandoned? Or in 5, when testing an existing IP the host with that IP don't reply fast enough and Alt-F takes its IP (192.168.1.254)? Don't know.

As you have now tested most things, there are only two situations for you to test: try using another router or try assigning the router another IP (so the box will use 192.168.1.254)

Sorry

[Chris Cobb]

I'm now thinking the DNS-323 might have a problem with its ethernet port - that could explain the issue. I'll check into in further and report back.

--
You received this message because you are subscribed to a topic in the Google Groups "Alt-F" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alt-f/cvBwy2u3aTk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alt-f+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/alt-f.
For more options, visit https://groups.google.com/d/optout.