8 comments

• 

  Anonymous

  5 years ago

  That's good... But let's loop it up a little. We had huge problems with solaris's autonegotiation algorithm, so I wrote the following scripts:
  
  getduplex.sh and fixduplex.sh
  
  Getduplex will loop through each interface defined in ifconfig, and show what the current status is: full or half duplex, 10 or 100 megabit, and will flag any that arn't 100/full.
  
  Fixduplex will 'fix' them to be 100/full on the fly. It makes networking pause for about 3 seconds (3 scary seconds) but it comes back. :-)
  
  http://cyberbuzz.gatech.edu/jprice/sun-duplex
  
  The scripts understands hme, qfe, dfme, and eri interfaces (and only up to 100 mbit. I don't have gig-copper gear to play with).
  reply
• 

  qmchenry

  5 years ago

  I had opportunity to use your script today and it is slick! Thanks for sharing it with us!
  
  Quinn
  reply
• 

  Spamly

  4 years ago

  THanks for the scripts! Love 'em!
  reply
• 

  Duck Dood

  4 years ago

  Thanks for those, zapman! fixduplex.sh got a little exercise today, and worked like a champ.
  
  :D
  reply
• 

  Caesar

  4 years ago

  This information perfect.
  
  thaks very much
  
  caesar
  :wink:
  reply
• 

  Anonymous

  3 years ago

  forcing full-duplex is in general a bad idea, because if the switch on the other end of the link is set to auto-negotiate, it will autonegotiate half-duplex. While this may not happen every time, it's the expected behavior:
  
  http://www.cisco.com/warp/public/473/46.html
  
  their advice is,
  * use autonegotiation whenever it works
  * if you manually set speed or duplex on either end, then manually set duplex on both ends.
  reply
• 

  Anonymous

  1 year ago

  Does anyone still have this script? I'm desperately looking for such a script to check the status.
  The link from above is down.
  
  Thanks,
  
  Ed.
  reply
• 

  Anonymous

  1 year ago

  http://web.archive.org/web/20050419155043/cyber...
  reply