Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

WTF: tftp downloads

  • 05-09-2001 7:29pm
    #1
    djr
    Registered Users, Registered Users 2 Posts: 231 ✭✭


    balls! got a secondhand 3c8432 (3com isdn bridge/router) recently will lorra security (of course no passwords supplied) tried all the usual backdoors to no avail; had to resort to wiping the flash memory via dip switches inside the router. question is this: no matter what version of the boot image (boot.68k) i try to transfer by (at this stage numerous different daemons) tftp, i always get this error from the router:
    > fl BOOT.68K
    FORMAT Flash and download Y/N ? y

    Formatting ..............................done.
    7527936 bytes available.


    Invalid MAC address in EEPROM - using 08-00-02-00-58-84
    Trying LAN L2 ... 100BaseTX full duplex connection detected.

    tftp load of file <BOOT.68K> from server 192.168.1.53

    Beginning transfer 3526
    Invalid image header. Trying next boot source
    Load failed!

    following the failure i get fired back to monitor mode.

    any help would be appreciated.



Comments

  • #2
    Gavin
    Registered Users, Registered Users 2 Posts: 4,676 ✭✭✭Gavin


    Well obviously enough it looks like there is something wrong with the file... Is it the right file ? I dunno, haven't used intelligent 3com stuff at all.

    Gav


  • #3
    djr
    Registered Users, Registered Users 2 Posts: 231 ✭✭djr


    i figured that is *was* corrupted initially, but i have since used 2 or 3 diff versions of the firmware obtained from variuos sources (cd's, ftp, bbs), and i get the same problem on every boot image.

    oh well, cheers anyway.


Advertisement