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

1.3.3.4 don't work with Linux Fedora Core 5 kernel up to 2.6.17-x

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by aver5, Aug 23, 2006.

  1. aver5

    aver5 LI Guru Member

    1.3.3.4 don't work with Linux Fedora Core 5 kernel up to 2.6.17-x

    Hello
    I' now working with 1.3.3.4 ...
    I'm glad to see new fonction like Bandwith management ...
    all was worked fine but when I use a computer with linux fedora Core 5 and a Kernel up to 2.6.17-xx
    network work very bad : small connecion like ssh work but when I launch bigger command ( directory listing on ssh or web access with big picture) transfert stay pending even connection seem to be let in established mode

    NOTE that on linux FC5 2.6.16-xx all working fine .....

    Is someone have the same problem on teh same platform or not ???
    IMPORTANT : no errlog on liunx adn or RV082
     
  2. Toxic

    Toxic Administrator Staff Member

    so do you still have problems when using an older firmware like v1.3.2?

    I ask as this topic is 1.3.3.4 related issues only.
     
  3. aver5

    aver5 LI Guru Member

    I don't know about 1.3.3.2 I've directly updated form 1.1.6.13 to 1.3.3.4
    Of course this problem was not in 1.1.6.13

    This is stange because wan access are blocked and also administration interface
    I't seem to be a problem from LAN side to WAN or to local GUI
    problem occur when computer is directly connected on RV082 LAN port or behind a switch
     
  4. aver5

    aver5 LI Guru Member

    new informations
    bandwith very slow with Fedora Core 5 kernel 2.6.17 occur also from wan access ...
    strange strange I think about a big problem on tcp config like sack fack dsack mtu ....
     
  5. Toxic

    Toxic Administrator Staff Member

    Anyone else experiencing this problem of NO access using a RV082 v1.3.3.4 firmware and Fedora?

    what MTU does linux use and what MTU are you using on the RV082?

    anything on the RV082 logs showing errors?
     
  6. pablito

    pablito Network Guru Member

    I'm using CentOS with kernel 2.6x without problem, it isn't Fedora but close. I initially had trouble with 1.3.2 that is now much better with the beta 1.3.4. Until the beta came out I had success with the old 1.1x version.

    To test you might try seeing if the problem is upstream & downstream or just upstream. My trouble was with upstream over DSL. The beta version is now much better.
     
  7. aver5

    aver5 LI Guru Member

    Anyone else experiencing this problem of NO access using a RV082 v1.3.3.4 firmware and Fedora?

    what MTU does linux use and what MTU are you using on the RV082?
    Linux MTU is 1500 and RV082 manualy on 1500 to
    I've tested a lot of tcp params on Linux statcks
    see all possibilities
    net.ipv4.tcp_max_syn_backlog = 1024
    net.ipv4.tcp_rfc1337 = 0
    net.ipv4.tcp_stdurg = 0
    net.ipv4.tcp_abort_on_overflow = 0
    net.ipv4.tcp_tw_recycle = 0
    net.ipv4.tcp_syncookies = 1
    net.ipv4.tcp_fin_timeout = 60
    net.ipv4.tcp_retries2 = 15
    net.ipv4.tcp_retries1 = 3
    net.ipv4.tcp_keepalive_intvl = 75
    net.ipv4.tcp_keepalive_probes = 9
    net.ipv4.tcp_keepalive_time = 7200
    net.ipv4.ipfrag_time = 30
    net.ipv4.ip_dynaddr = 0
    net.ipv4.ipfrag_low_thresh = 196608
    net.ipv4.ipfrag_high_thresh = 262144
    net.ipv4.tcp_max_tw_buckets = 180000
    net.ipv4.tcp_max_orphans = 131072
    net.ipv4.tcp_synack_retries = 5
    net.ipv4.tcp_syn_retries = 5
    net.ipv4.ip_nonlocal_bind = 0
    net.ipv4.ip_no_pmtu_disc = 0
    net.ipv4.ip_autoconfig = 0
    net.ipv4.ip_default_ttl = 64
    net.ipv4.ip_forward = 0
    net.ipv4.tcp_retrans_collapse = 1
    net.ipv4.tcp_sack = 1
    net.ipv4.tcp_window_scaling = 1
    net.ipv4.tcp_timestamps = 1
    net.ipv4.conf.eth0.promote_secondaries = 0
    net.ipv4.conf.eth0.force_igmp_version = 0
    net.ipv4.conf.eth0.disable_policy = 0
    net.ipv4.conf.eth0.disable_xfrm = 0
    net.ipv4.conf.eth0.arp_ignore = 0
    net.ipv4.conf.eth0.arp_announce = 0
    net.ipv4.conf.eth0.arp_filter = 0
    net.ipv4.conf.eth0.tag = 0
    net.ipv4.conf.eth0.log_martians = 0
    net.ipv4.conf.eth0.bootp_relay = 0
    net.ipv4.conf.eth0.medium_id = 0
    net.ipv4.conf.eth0.proxy_arp = 0
    net.ipv4.conf.eth0.accept_source_route = 0
    net.ipv4.conf.eth0.send_redirects = 1
    net.ipv4.conf.eth0.rp_filter = 1
    net.ipv4.conf.eth0.shared_media = 1
    net.ipv4.conf.eth0.secure_redirects = 1
    net.ipv4.conf.eth0.accept_redirects = 1
    net.ipv4.conf.eth0.mc_forwarding = 0
    net.ipv4.conf.eth0.forwarding = 0


    anything on the RV082 logs showing errors?
    __________________
    Regards Simon
     

Share This Page