Mark Binner - Wed, 2011/08/03 - 16:58

Can anyone help me with this one? I downloaded the new version 11-2 File server appliance and installed it on a Dell Optiplex 755. After rebooting I went through the network configuration. When I chose to set the IP address via DHCP it just returned to the same menu. If I then rebooted, a message appeared saying 'network is not yet configured'. The process repeated as above.

If I chose a static IP address, the details for connecting via Webmin, file sharing etc was displayed (sorry, I don't know what the menu is called) and the settings were preserved after booting. In effect, I could not set networking to use DHCP AND store the result. I had the same problem on the same machine with 11-1 release too.

Is this a fault or I am missing something crucial?

Thanks.

Forum: 
Support
Tags: 
file server
ip address
Jeremy Davis's picture

Jeremy Davis - Wed, 2011/08/03 - 18:21

Or strictly speaking an issue whereby the TKL confconsole doesn't respect the settings made in Webmin (assuming I'm on the right track and you're using Webmin for your networking settings).

To avoid this issue use the TKL confconsole for setting up your networking rather than Webm. Confconsole can be accessed via a local terminal (if on vm or hardware with screen connected) or via SSH (remote and/or headless server). Should all be fairly self explanatory.

Mark Binner - Wed, 2011/08/03 - 18:48

Jeremy,

Thanks for the very speedy response. I didn't make the setting changes in Webmin (or at least not at first), I got the error just using the menu that comes up during the first boot after installation. I tried Webmin later thinking I could 'cheat'. No such luck.


Jeremy Davis's picture

Jeremy Davis - Thu, 2011/08/04 - 04:11

Going back over your initial post again I see what's happened. Sorry I didn't understand initially. The screen you are talking about is the confconcole (or Configuration Console). It should default to DHCP and if you are happy with that then there should be no need for further networking configuration.

So let me get it straight. You install and after finishing installation you get to the confconsole and it says "network is not yet configured" and if you go into netrworking you select DHCP and it drops you back to the same screen with the same message re networking? But it will let you set a static IP with conficonsole? And then everything works as expected?

From what you've said my first guess would be something not quite right with your DHCP and/or your appliance connecting to it. Can you ping your DHCP server from your TKL appliance? Why do you want DHCP anyway? IMO it's much better for a server to have a static IP anyway.

Mark Binner - Thu, 2011/08/04 - 13:18

I don't think I worded my query as well as I might have. Here is the sequence of events:

  1. Install TKL
  2. Reboot after removing CD
  3. Enter root password x 2
  4. Enter extplorer password x 2
  5. Initialise Hub Services > Skip (won't work because of corporate network setup)
  6. Security Updates > Skip (same reason)
  7. Message 'Networking not yet configured' appears
  8. Menu appears with options for DHCP or Static IP
  9. Choose DHCP
  10. It DOES pick up and display an IP address but displays the same menu as step 8 (with options to 'Select' or Back') rather than proceeding to the Fileserver Appliance Services menu that shows the URLs for File Manager, Web Shell, Webmin, SMB/CIFS and SSH/STFP. You do get this menu if you choose Static IP in step 8. If you go back and 'Quit' or 'Reboot' you get the message in step 7 when it boots, so the DHCP-obtained IP address has not been saved. Static is fine.

I hope that is a lot clearer than my first attempt. It does seem like a bug to me.

I really appreciate all your help, Jeremy.


Jeremy Davis's picture

Jeremy Davis - Thu, 2011/08/04 - 15:24

I don't recall having a similar problem but couldn't recall the exact steps so I just did a clean install (of v11.1)

After step 6 my machine automatically gets an IP via DHCP and displays the main conconsole screen (like you describe when you set a static IP in step 10). If I go Advanced Menu>>Networking>>DHCP it gives me a new IP via DHCP and drops me back to the networking page as you describe. If I go Back>>Back it takes me back to the main confconsole screen again (with my new DHCP IP). If from the networking page I set a static IP it also drops me back to the networking page (requires Back>>Back to get back to the main confconsole screen again).

So it still sounds to me like some sort of networking or DHCP problem in your environment. In your comments you mention a prohibitive corporate network setup, perhaps that is interfereing? Or perhaps for some reason the driver for your NIC is a little flakey in Linux and is not initialising properly? The only time I have ever seen the 'Networking not yet configured' message was with unsupported hardware - but it was quite different because it wouldn't allow setting of iP at all (static or DHCP) because it couldn't even see the NIC.

Still TBH I think that servers should have a static IP. IMO it makes for a more robust and reliable network. DHCP is fine for end user systems (desktops, laptops, smart phones, etc) and ad-hoc setups, but IMO servers should be set static. It allows for a nice clean, consistent DNS setup with less to go wrong.

Mark Binner - Thu, 2011/08/04 - 17:15

I tried again using a different PC but the same media and network environment. The result was the same as before. Then I tried an older, lower spec PC and that gave the result I expected i.e. like you described in your last post. To me, that means your theory about flaky NIC support would seem to be the most likely. I agree that it is odd that it works with static IPs if it's a driver issue.

I get what you mean about servers and IP addresses. Can we agree to differ on that one? My logic is to use TKL Fileserver as an easy-to-set-up NAS box in a variety of locations that all have DHCP servers. If I use static IP addresses I have to know what IP addresses are in use in each place to ensure I don't have address conflicts. What a lot of faff that would be. I'll let DHCP earn its keep :-)

I think it's rather a shame that more people don't look at the Turnkey File server as an option for a quick and dirty NAS box because it fulfils that role brilliantly. Most forums talk about FreeNAS, which I kinda like, but TKL is so easy and speedy to set up. Then all you do is map a drive to \\fileserver\storage on your Windows box and you have a place to store/dump whatever you want. Good eh?

Anyway, my sincere thanks for your help/suggestions/wisdom. I'm sure we will talk again sometime in the future.

Best regards,

Mark


Jeremy Davis's picture

Jeremy Davis - Fri, 2011/08/05 - 04:59

Although it's a pity that it doesn't work as it should with your hardware of choice. For interest sake it may be worth tring to install the driver direct from the NIC manufacturer and see if that helps. In a recent thread another user (with a completely different problem involving a Realtek NIC) installed an upstream driver and that resolved his issue (despite the fact that it seemed to be the same driver version). It's a stab in the dark but may be worth the effort?

And it sounds as if in your usage scenario (a portable NAS) that DHCP is indeed the preferred option, so sorry to push my personal barrow on that one without having all the info.

Glad to hear that TKL fileserver is working out for you now and glad I could be of some assistance to you. Good luck with it and no doubt talk again another time :)

Add new comment