Networking

This site covers Linux networking specific topics. It does not cover general networking questions, these are covered under the more general Wikipedia Computer Networks. See the External Links section for other useful resources.

General

Protocols

Drivers

Device Performance Enhancements

Hardware

Security

Mobility

Administration

Testing

Resources

 

Documentation Links

 

Related Links

 

talk:ipv4

I think the FAQ should be its own page linked to from the main page. Like this FAQ -Jon

Given the amount of info on this wiki I'm not sure that this is a good idea as it could easily get overwhelmed. However we can do it and refactor later if it gets too big. For example DCCP already has an FAQ. --Imcdnzl | DCCP 19:24, 10 May 2006 (PDT)

llc


Linux LLC Stack Origins

The stack present on the Linux kernel was originally contributed by Procom Inc, that released a combined NetBEUI + LLC stack developed for Linux 2.0.36.

linuxnet:policy

In case it isn't obvious

  • Spam will be deleted and rollback as soon as noticed.
  • Any account spamming will be blocked
  • Small furry creatures will be sent to eat your young

current_events

2007

dccp_testing

This page describes how to test the performance of DCCP, choosing suitable test applications, and how to
download the experimental DCCP test tree.

tipc

TIPC


Introduction

TIPC is a LAN protocol, originally designed by Jon Maloy at Ericsson. Its purpose is to provide an efficient, transparent, and scalable communication mechanism for a wide range of possible cluster configurations. It has been in the linux kernel since 2.6.16.
http://tipc.sf.net is the main TIPC site.

talk:tcp_memory_documentation

stack:

call tree:
[] tcp_retransmit_skb+0x176/0x2dd

[] tcp_retransmit_timer

[] tcp_write_timer

[] tcp_write_timer

[] tcp_write

[] run_timer_softirq

[] __do_softirq


=

 smp_apic_timer_interrupt
 apic_timer_interrupt
 mwait_idle
 cpu_idle
 start_kernel

(o) kernel panic - not syncing: Fatal exception in interrupt

kevent

linuxnet:about

This Wiki is for documentation and discussions of development of the Linux Networking.

tipc_faq

networkmanager

NetworkManager is designed to be fully automatic and "Just Work" without intervention, but friendly desktop applications allow users to control the state of the network if they desire. NetworkManager keeps a list of all available network devices, and updates that list when you insert or remove new network cards, dock your laptop, etc. Using this list, NetworkManager determines the best device to use for the computer's network connection.

i/oat

bonding

The Linux bonding driver provides a method for aggregating
multiple network interfaces into a single logical
bonded interface.
The behavior of the bonded interfaces depends upon the mode; generally
speaking, modes provide either hot standby or load balancing services.
Additionally, link integrity monitoring may be performed.

sk_buff

All network-related queues and buffers in the kernel use a common data structure, struct sk_buff. This is a large struct containing all the control information required for the packet (datagram, cell, whatever). The sk_buff elements are organized as a doubly linked list, in such a way that it is very efficient to move an sk_buff element from the beginning/end of a list to the beginning/end of another list.

ifb

The Intermediate Functional Block device is the successor to the IMQ iptables module that was never integrated.
Advantage over current IMQ; cleaner in particular in SMP;
with a _lot_ less code. Old Dummy device functionality is preserved while new one only
kicks in if you use actions.

help:contents

No help specific to Linux Net wiki.

applications

This page summarizes the traffic patterns of applications.

bernd_eckenfels

traceroute

overview

Traceroute is a system administrators utility to trace the route IP packets take from a source system to some destination system.

There are several implementations of this tool. Most distributions include the Lawrence Berkeley National Laboratory Network Research Group version. There is two implementations written especially for LiNUX, one by Olaf Kirch and other one by Dmitry Butskoy.

Syndicate content