Re: Network issues with Linksys BEFSR41 router - SGI

This is a discussion on Re: Network issues with Linksys BEFSR41 router - SGI ; marcus@stade.se (Marcus Stade) wrote in message news: ... > Hi, > > I recently started fiddling with my octane again, after having it > standing on the floor collecting dust for a while. Now I got a little > issue ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: Network issues with Linksys BEFSR41 router

  1. Re: Network issues with Linksys BEFSR41 router

    marcus@stade.se (Marcus Stade) wrote in message news:<2fd0a83c.0403190435.4e4a61d@posting.google.com>...
    > Hi,
    >
    > I recently started fiddling with my octane again, after having it
    > standing on the floor collecting dust for a while. Now I got a little
    > issue with hooking it up to my little LAN here at home. Basically what
    > happens when I hook up my Octane to my Linksys BEFSR41 router is that
    >
    > The little led on the router for that ports keeps blinking regularly.
    > On for about two seconds, and then off for the same amount of time.


    > Before I did an IRIX re-install on it, it also gave me an error
    > saying:
    > "ef0: ef0: remote hub error", or something along the lines of that,
    > iirc.


    Please followup to this thread if you figure out the cause. I'm having
    much the same type of problems connecting my octane and PC to a
    Linksys BEFW11S4 as well as the BEFSR41.

    I've made the change to the kernel to force my Octance's ef0 interface
    to full duplex.
    See http://www.aventec.com/documentation...gotiation.html

    After doing this, the linksys' LEDs report the Octane's port as being
    half duplex! (go figure).
    ifcofnig -av lists ef0 as up and full deplex and I am able ot connect
    through the linksys to other machines on the linksys network. Strange.

    A coworker tells me that linksys switches aren't bad, but that they do
    pass a great deal more ethernet traffic than you would expect (Cisco
    CDP goes right through).

  2. Re: Network issues with Linksys BEFSR41 router

    Brian Leair wrote:
    > After doing this, the linksys' LEDs report the Octane's port as being
    > half duplex! (go figure).


    A sure sign that you don't want to set the kernel to think it's a full-duplex
    link, unless you want *very* bad performance.

    --
    Alexis Cousein Senior Systems Engineer
    alexis@sgi.com SGI/Silicon Graphics Brussels

    Nobody Expects the Belgian Inquisition!


  3. Re: Network issues with Linksys BEFSR41 router

    Alexis Cousein wrote in message news:...
    > Brian Leair wrote:
    > > After doing this, the linksys' LEDs report the Octane's port as being
    > > half duplex! (go figure).

    >
    > A sure sign that you don't want to set the kernel to think it's a full-duplex
    > link, unless you want *very* bad performance.


    When I posted that message I had only powered down the Linksys and had
    restarted the Octane - doing so resulted in the unusual link state.
    Once powered my sgi down and restarted it came up with the link in
    full duplex and the linksys was also happy. Plus, now my networking
    (static ip, default gateway as the linksys) now works.
    Before changing the kernel I could manually enter "route add" to add
    the default gateway address and I could get terrible performance in my
    network but after several minutes gated would log a message "link
    timeout" and it would delete the default gateway entry through ef0.
    Now things just work. Yeah.

    To recap, forcing to full duplex, recompiling the kernel, then
    powering cycling has got me to a point where all works well. What a
    relief.

+ Reply to Thread