1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Alchemy bug?

Discussion in 'Sveasoft Firmware' started by hokie21, Feb 2, 2007.

  1. hokie21

    hokie21 LI Guru Member

    I am using Alchemy V1.0 v3.37.6.8sv. For a long time I have had a single computer where the network connection would stop working for a little time each night. When the computer stops working, all services from the computer stop working and then a little while later they all come back. The funny thing about this problem was that it was only a problem from a single computer and only when the computer tried to talk to IP addresses outside the local subnet. A reboot of the computer would also always solve the problem. After about 2 years of this problem, I think have finally figured out what was going on.

    This seems to be a reproducable bug in Alchemy V1.0 v3.37.6.8sv.

    Configuration:
    Set up a range of ports to forward to the test computer IP address for "both" in the "port range forward" config menu. Make sure "enable" is NOT selected.

    To see the problem:
    As the computer is used, the outbound source port on the host computer increments upward with each new outbound connection. As the outbound host source port number is within the range defined above, the outbound packets will be discarded by the linksys! I found this with the help of Wallwatcher which showed these connections as "blocked" even though I had no "blocking" configured in the router!

    Workaround:
    Configure "disabled" forwarding configurations to an unused IP address.
     

Share This Page