12 Jan, 2010

1 commit

  • 3c509 was changed to support ethtool in 2002, making the 'xcvr' module
    parameter obsolete in most cases. More recently 3c509 was converted
    to the modern driver model and this parameter was removed. Fix the
    documentation to refer to ethtool rather than the module parameter.

    Signed-off-by: Ben Hutchings
    Signed-off-by: David S. Miller

    Ben Hutchings
     

04 Dec, 2009

1 commit

  • commit 8ec1e0ebe26087bfc5c0394ada5feb5758014fc8
    Author: Patrick McHardy
    Date: Thu Dec 3 12:16:35 2009 +0100

    ipv4: add sysctl to accept packets with local source addresses

    Change fib_validate_source() to accept packets with a local source address when
    the "accept_local" sysctl is set for the incoming inet device. Combined with the
    previous patches, this allows to communicate between multiple local interfaces
    over the wire.

    Signed-off-by: Patrick McHardy

    Signed-off-by: David S. Miller

    Patrick McHardy
     

03 Dec, 2009

3 commits

  • Define sysctl (tcp_cookie_size) to turn on and off the cookie option
    default globally, instead of a compiled configuration option.

    Define per socket option (TCP_COOKIE_TRANSACTIONS) for setting constant
    data values, retrieving variable cookie values, and other facilities.

    Move inline tcp_clear_options() unchanged from net/tcp.h to linux/tcp.h,
    near its corresponding struct tcp_options_received (prior to changes).

    This is a straightforward re-implementation of an earlier (year-old)
    patch that no longer applies cleanly, with permission of the original
    author (Adam Langley):

    http://thread.gmane.org/gmane.linux.network/102586

    These functions will also be used in subsequent patches that implement
    additional features.

    Requires:
    net: TCP_MSS_DEFAULT, TCP_MSS_DESIRED

    Signed-off-by: William.Allen.Simpson@gmail.com
    Signed-off-by: David S. Miller

    William Allen Simpson
     
  • David S. Miller
     
  • The commit 27fed4175acf81ddd91d9a4ee2fd298981f60295 (ip: fix logic of
    reverse path filter sysctl) has changed the logic of rp_filter. The
    document about rp_filter is out of date. Now, setting
    conf/all/rp_filte with 0 can also enable source validation.

    Update the document according to the commit.

    Signed-off-by: Shan Wei
    Signed-off-by: David S. Miller

    Shan Wei
     

07 Oct, 2009

2 commits

  • On Friday 02 October 2009 20:53:51 you wrote:

    > This is good although I would have shortened the name.

    Ah, I knew I forgot something :) Here is v4.

    tavi

    >From 24d96d825b9fa832b22878cc6c990d5711968734 Mon Sep 17 00:00:00 2001
    From: Octavian Purdila
    Date: Fri, 2 Oct 2009 00:51:15 +0300
    Subject: [PATCH] ipv6: new sysctl for sending TLLAO with unicast NAs

    Neighbor advertisements responding to unicast neighbor solicitations
    did not include the target link-layer address option. This patch adds
    a new sysctl option (disabled by default) which controls whether this
    option should be sent even with unicast NAs.

    The need for this arose because certain routers expect the TLLAO in
    some situations even as a response to unicast NS packets.

    Moreover, RFC 2461 recommends sending this to avoid a race condition
    (section 4.4, Target link-layer address)

    Signed-off-by: Cosmin Ratiu
    Signed-off-by: Octavian Purdila
    Signed-off-by: David S. Miller

    Octavian Purdila
     
  • In some cases there is not desirable to switch back to primary interface when
    it's link recovers and rather stay with currently active one. We need to avoid
    packetloss as much as we can in some cases. This is solved by introducing
    primary_reselect option. Note that enslaved primary slave is set as current
    active no matter what.

    Patch modified by Jay Vosburgh as follows: fixed bug in action
    after change of option setting via sysfs, revised the documentation
    update, and bumped the bonding version number.

    Signed-off-by: Jiri Pirko
    Signed-off-by: Jay Vosburgh
    Signed-off-by: David S. Miller

    Jiri Pirko
     

05 Oct, 2009

1 commit

  • It is not currently possible to instruct pktgen to use one selected tx queue.

    When Robert added multiqueue support in commit 45b270f8, he added
    an interval (queue_map_min, queue_map_max), and his code doesnt take
    into account the case of min = max, to select one tx queue exactly.

    I suspect a high performance setup on a eight txqueue device wants
    to use exactly eight cpus, and assign one tx queue to each sender.

    This patchs makes pktgen select the right tx queue, not the first one.

    Also updates Documentation to reflect Robert changes.

    Signed-off-by: Eric Dumazet
    Signed-off-by: Robert Olsson
    Signed-off-by: David S. Miller

    Eric Dumazet
     

03 Oct, 2009

1 commit


21 Sep, 2009

1 commit


05 Sep, 2009

1 commit

  • This patch introduces a new sysctl option to make IPv4 Address Scoping
    configurable .

    In networking environments where DNAT rules in iptables prerouting
    chains convert destination IP's to link-local/private IP addresses,
    SCTP connections fail to establish as the INIT chunk is dropped by the
    kernel due to address scope match failure.
    For example to support overlapping IP addresses (same IP address with
    different vlan id) a Layer-5 application listens on link local IP's,
    and there is a DNAT rule that maps the destination IP to a link local
    IP. Such applications never get the SCTP INIT if the address-scoping
    draft is strictly followed.

    This sysctl configuration allows SCTP to function in such
    unconventional networking environments.

    Sysctl options:
    0 - Disable IPv4 address scoping draft altogether
    1 - Enable IPv4 address scoping (default, current behavior)
    2 - Enable address scoping but allow IPv4 private addresses in init/init-ack
    3 - Enable address scoping but allow IPv4 link local address in init/init-ack

    Signed-off-by: Bhaskar Dutta
    Signed-off-by: Vlad Yasevich

    Bhaskar Dutta
     

02 Sep, 2009

1 commit


20 Aug, 2009

1 commit


13 Aug, 2009

1 commit


28 Jul, 2009

1 commit


27 Jul, 2009

1 commit


18 Jul, 2009

1 commit


15 Jun, 2009

1 commit


13 Jun, 2009

1 commit


12 Jun, 2009

1 commit

  • Commit b00055aacdb172c05067612278ba27265fcd05ce " [NET] core: add
    RFC2863 operstate" defined new interface flag values. Its
    documentation specified that these flags could be accessed from user
    space via SIOCGIFFLAGS. However, this does not work because the new
    flags do not fit in that ioctl's argument width.

    Change the documentation to match the code's behavior. Also change
    the source to explicitly show the truncation. This _should_ have no
    effect on executable code, and did not with gcc 4.2.4 generating x86
    code.

    A new ioctl could be defined to return all interface flags to user
    space. However, since this has been broken for three years with no
    one complaining, there doesn't seem much need. They are still
    accessible via netlink.

    Reported-by: "Fredrik Arnerup"
    Signed-off-by: John Dykstra
    Signed-off-by: David S. Miller

    John Dykstra
     

09 Jun, 2009

1 commit


01 Jun, 2009

1 commit

  • Add 'autoconf' and 'disable_ipv6' parameters to the IPv6 module.

    The first controls if IPv6 addresses are autoconfigured from
    prefixes received in Router Advertisements. The IPv6 loopback
    (::1) and link-local addresses are still configured.

    The second controls if IPv6 addresses are desired at all. No
    IPv6 addresses will be added to any interfaces.

    Signed-off-by: Brian Haley
    Signed-off-by: David S. Miller

    Brian Haley
     

19 May, 2009

3 commits


18 May, 2009

1 commit


05 May, 2009

1 commit

  • This should be very safe compared with full enabled, so I see
    no reason why it shouldn't be done right away. As ECN can only
    be negotiated if the SYN sending party is also supporting it,
    somebody in the loop probably knows what he/she is doing. If
    SYN does not ask for ECN, the server side SYN-ACK is identical
    to what it is without ECN. Thus it's quite safe.

    The chosen value is safe w.r.t to existing configs which
    choose to currently set manually either 0 or 1 but
    silently upgrades those who have not explicitly requested
    ECN off.

    Whether to just enable both sides comes up time to time but
    unless that gets done now we can at least make the servers
    aware of ECN already. As there are some known problems to occur
    if ECN is enabled, it's currently questionable whether there's
    any real gain from enabling clients as servers mostly won't
    support it anyway (so we'd hit just the negative sides). After
    enabling the servers and getting that deployed, the client end
    enable really has some potential gain too.

    Signed-off-by: Ilpo Järvinen
    Signed-off-by: David S. Miller

    Ilpo Järvinen
     

23 Apr, 2009

1 commit


13 Apr, 2009

1 commit

  • Fix a zero address hole bug in the bonding arp_ip_target list
    that was causing the bond to ignore ARP replies (bugz 13006).
    Instead of just setting the array entry to zero, we now
    copy any additional entries down one slot, putting the
    zero entry at the end. With this change we can now have
    all the loops that walk the array stop when they hit a zero
    since there will be no addresses after it.

    Changes are based in part on code fragment provided in kernel:
    bugzilla 13006:

    http://bugzilla.kernel.org/show_bug.cgi?id=13006

    by Steve Howard

    Signed-off-by: Brian Haley
    Signed-off-by: Jay Vosburgh
    Signed-off-by: David S. Miller

    Brian Haley
     

02 Apr, 2009

1 commit

  • - vxge driver help text file.

    - No change from previous submission.

    - Changes in previous submissions -
    Removed the performance tuning section with instructions to disable
    time stamps and change sysctl settings - Reported by Dave Miller
    General clean up.
    - Removed tx/rx_pause, exec_mode, tx_steering_type, rx_steering_type, gro,
    intr_type, rx & tx max_indicate_pkts and exec_mode loadable parameters. The
    driver default settings work well in most if not all cases. Another patch
    to configure these parameters with ethtool will be released in the future -
    Reported by Stephen Hemminger.
    - Incorporated following fixes based on comments from Ben Hutchings
    Removed references to earlier kernel versions.
    Removed sections that are similar for all drivers -
    Load/Unload
    Identifying the adapter/interface
    Boot time configuration
    Removed loadable parameter -
    NAPI - Napi is always enabled.
    rx_steering_type & ring_blocks - The driver default settings
    work well in most if not all cases. Another patch to configure
    these parameters with ethtool will be released in the future.
    Removed ethtool support section - No need to duplicate ethtool
    docs here.
    Removed Known Issue on SUSE 9 - Doesn't apply when using a
    current kernel.
    Removed Common Problems section - These don't apply to in-tree modules.
    Removed Available Downloads section - Not sure this belongs in-tree.
    Removed Copyright information - This notice doesn't belong in
    the kernel.

    Signed-off-by: Sivakumar Subramani
    Signed-off-by: Rastapur Santosh
    Signed-off-by: Ramkrishna Vepa
    Signed-off-by: David S. Miller

    Ramkrishna Vepa
     

19 Mar, 2009

1 commit

  • Fix the behavior of allowing both sysctl and addrconf_dad_failure()
    to set the disable_ipv6 parameter without any bad side-effects.
    If DAD fails and accept_dad > 1, we will still set disable_ipv6=1,
    but then instead of allowing an RA to add an address then
    immediately fail DAD, we simply don't allow the address to be
    added in the first place. This also lets the user set this flag
    and disable all IPv6 addresses on the interface, or on the entire
    system.

    Signed-off-by: Brian Haley
    Signed-off-by: David S. Miller

    Brian Haley
     

15 Mar, 2009

1 commit


05 Mar, 2009

1 commit


04 Mar, 2009

1 commit

  • Add "disable" module parameter support to ipv6.ko by specifying
    "disable=1" on module load. We just do the minimum of initializing
    inetsw6[] so calls from other modules to inet6_register_protosw()
    won't OOPs, then bail out. No IPv6 addresses or sockets can be
    created as a result, and a reboot is required to enable IPv6.

    Signed-off-by: Brian Haley
    Signed-off-by: David S. Miller

    Brian Haley
     

27 Feb, 2009

1 commit

  • This file documents the specifics of the RDS sockets API,
    as well as covering some of the details of its internal
    implementation.

    Signed-off-by: Andy Grover
    Signed-off-by: David S. Miller

    Andy Grover
     

24 Feb, 2009

2 commits


23 Feb, 2009

1 commit

  • Extend existing reverse path filter option to allow strict or loose
    filtering. (See http://en.wikipedia.org/wiki/Reverse_path_filtering).

    For compatibility with existing usage, the value 1 is chosen for strict mode
    and 2 for loose mode.

    Signed-off-by: Stephen Hemminger
    Signed-off-by: David S. Miller

    Stephen Hemminger
     

16 Feb, 2009

2 commits

  • Instructions for time stamping outgoing packets are take from the
    socket layer and later copied into the new skb.

    Signed-off-by: Patrick Ohly
    Signed-off-by: David S. Miller

    Patrick Ohly
     
  • User space can request hardware and/or software time stamping.
    Reporting of the result(s) via a new control message is enabled
    separately for each field in the message because some of the
    fields may require additional computation and thus cause overhead.
    User space can tell the different kinds of time stamps apart
    and choose what suits its needs.

    When a TX timestamp operation is requested, the TX skb will be cloned
    and the clone will be time stamped (in hardware or software) and added
    to the socket error queue of the skb, if the skb has a socket
    associated with it.

    The actual TX timestamp will reach userspace as a RX timestamp on the
    cloned packet. If timestamping is requested and no timestamping is
    done in the device driver (potentially this may use hardware
    timestamping), it will be done in software after the device's
    start_hard_xmit routine.

    Signed-off-by: Patrick Ohly
    Signed-off-by: David S. Miller

    Patrick Ohly