GoFlex Net & GoFlex Home

[Mr_Smilodon]

I would like my GoFlex home to have a "fixed" address on my network.  It makes it easier to "find" for maintenance and so forth.  Also, if there is a network problem or firewall issue, and I see that IP on the network, I know what it is.

The option is on the "preferences" menu, so seemingly no problem.  I have set it and it works fine.... UNTIL I power off the unit (or the power company does it for me!).

When the drive boots back up, it switches back to dynamic mode, and gets some random address on the network.  Now I can't find it again from my web browser.

Is there any way to get a fixed IP and "hold" it between power failures?

[robyb]

Hi Mr_smilodon,

I confirmed this bug and have logged it.  We'll make sure to have this fixed for the next update.

Cheers,

Roby!

[Mark5047]

Any update on this yet? I also would prefer to hard code an IP address on my drive.

[matt.jessop]

I don't believe this is fixed yet - I got around it by assigning the IP address on my router using the MAC address of the GFH device.

[cutNdry]

This is truly a frustrating issue, and is a bit of an indictment on Seagate's software testing procedures.

These devices run on some flavor of RedHat Linux, and I have done some investigating into this issue.  After hacking my way in to the device, and taking root control, I did some poking around.

What I found is that the ethernet configuration lives in /etc/sysconfig/network-scripts/ifcfg-eth0

So, I decided to manually edit this file to the required static IP parameters.  I then rebooted the device.  No luck.  There is a startup script somewhere that overwrites this file each time the device boots, so any changes you make to the network configuration at all get overwritten at boot time.

SEAGATE - Okay, so you're busted now.  It is now apparent to all that you did not test this device before shipping it, and there are gaping holes in the startup scripting.  There is no excuse for a product shipping with this kind of bug, period.  If you decide to man up to this problem and tell me where this infuriating little startup script is running from, I'll go away and not bother you anymore.  If you decide to lecture me for hacking this incredibly un-secure device, then I will start posting all the security flaws I have found.

I look forward to your reply.  Of course, if I beat you to the punch and find the script myself, then I will let all the cats out of the bag at once.

Cheers!

[cutNdry]

Too late.

I have found the source file that overwrites the /etc/sysconfig/network-scripts/ifcfg-eth0 at each boot.

The source file is /etc/sysconfig/network-scripts/dhcp.ifcfg-eth0

Since I have yet to find the script that invokes this overwrite, I simply made my changes to the source file and now my device has a properly functioning static IP address.

SEAGATE - I will be available on the job market starting in January.  Please let me know if you would like some help.  I will keep my mouth shut about the security holes for now.

For all of you wanting a fix to this issue, if you are ballsy enough to "void" your warranty, I highly recommend getting ssh access to your device, getting root access, and configuring this correctly yourself.

DON'T BRICK YOUR DEVICE!!  You can easily do this if you give it a non-working ifcfg.  I hacked a hardware serial port onto my device to get console access in case I did accidentally brick it, for which you will need a 3.3v TTL to RS-232 converter, but it is well worth the effort.

In any event, my device now works as it should.  Seagate should be awfully embarassed that an end-user FIXED THEIR BUG for them, and did so by EXPLOITING THE SECURITY HOLES in the device, which are well documented eslewhere on the net.

Yes, I am a heck CUSTOMER.  You should hire me, then I'd HAVE to shut up.

[robyb]

Thanks for your help, we have located the source of the problem and resolved it.  It will be available in the next update.

Cheers,

Roby!

[Keithsmythe]

Hi CutNdry,

You seem to be able to provide answers better than Seagate can.

Do you know if there are any likely issues in regard to viruses if the Goflex Home drive is shared between Macs and PC's?

Thanks

Keith

[Gregc100]

Hi!

When we can expect new software. Can you please hurry with update beacuse it's a big problem for me?

Best regards,

Gregor

[robm1q]

Dear Seagate,

I am the network administrator for a fairly large advertising agency, and put my reputation and my technological backround on the line in recommending your GoFlex Product.  We purchased your product, set it up in our offices, and mailed it to our datacenter to be plugged into a colocated server in another state.   [Keep It Nice] in not testing the devices retention of a fixed ip address we had to ship the piece of [Edit: Please do not evade the word filter] back here, spend countless hours trying to determine what was wrong until we ran across this thread.   Our network doesn't use DHCP.... Fixed IP's only.   So your device basically fails on all counts.  

I assure you I will NEVER recommend ANY Seagate product or harddrive ever again.  

Thank you for making me look like a fool in front of coworkers and other IT professionals in recommending your [Edit: Please do not evade the word filter] device.   I suggest releasing a software update before you alienate other long term and highly loyal customers such as myself.  

Yours truly,

Robert M