Linux上的基础网络设备总结

谁借莪１个温暖的怀抱￠ 2022-07-12 18:47 383阅读 0赞

# 1 Linux 上的基础网络设备详解和工作原理 #

[http://www.ibm.com/developerworks/cn/linux/1310\_xiawc\_networkdevice/][http_www.ibm.com_developerworks_cn_linux_1310_xiawc_networkdevice]

# 2 ip操作 #

VLANs management

ip link add link eth0 name eth0.2 type vlan id 2
    ip link add link eth0 name myvlan type vlan id 2 loose_binding on
    ip link delete myvlan type vlan
    ip link add foo type vlan help

This replaces the obsolete vconfig(8) program and adds new features.

The loose\_binding flag stops the VLAN interface from tracking the line protocol status of the underlying device.

Creation of TUN/TAP interfaces

ip tuntap add dev mytap mode tap user md

This replaces the obsolete tunctl(8) program.

Creation of dummy interfaces

ip link add mydummy type dummy

The only way to create more dummy interfaces after the dummy module has been loaded used to be loading it again with a different name, and they were all named dummyN. Since module-init-tools does not support anymore loading the same module multiple times, iproute fully replaced this method.

Ethernet in GRE tunnels

ip link add mygretun type gretap remote 192.0.2.1
    ip link add foo type gretap help

A practical way to remotely bridge two Ethernet networks. The IP MTU is reduced of the expected 20 (IP) + 4 (GRE) + 14 (Ethernet II) bytes.

# 3 虚拟网络设备–VETH pair #

Veth pair 是一对虚拟网卡，从一张veth网卡发出的数据包可以直接到达它的peer veth,两者之间存在着虚拟链路。  
Veth 网卡和常规的以太网区别仅在于xmit接口：将数据发送到其peer,触发peer的Rx 过程。  
Veth 的原理示意图如下：  
![这里写图片描述][SouthEast]  
实验：

#!/bin/sh
    echo "create net namespace net0 and net1"
    ip netns add net0
    ip netns add net1
    echo "list net namespace"
    ip netns list
    echo "add veth pair v1 and vp1"
    ip link add veth_0 type veth peer name veth_0_peer
    ip link
    echo "set veth_0 in net0"
    ip link set veth_0 netns net0
    echo "set veth_0_peer in net1"
    ip link set veth_0_peer netns net1
    ip netns exec net0 ip addr add local 10.0.78.3/24 dev veth_0
    ip netns exec net0 ifconfig veth_0 up
    ip netns exec net1 ip addr add local 10.0.78.4/24 dev veth_0_peer
    ip netns exec net1 ifconfig veth_0_peer up
    echo "show ip netns net0"
    ip netns exec net0 ip addr
    echo "show ip netns net1"
    ip netns exec net1 ip addr
    ip netns exec net1 ping 10.0.78.3

veth pair是用于不同network namespace间进行通信的方式，veth pair将一个network namespace数据发往另一个network namespace的veth。如下：  
![这里写图片描述][SouthEast 1]  
操作

# add the namespaces
    ip netns add ns1
    ip netns add ns2
    # create the veth pair
    ip link add tap1 type veth peer name tap2
    # move the interfaces to the namespaces
    ip link set tap1 netns ns1
    ip link set tap2 netns ns2
    # bring up the links
    ip netns exec ns1 ip link set dev tap1 up
    ip netns exec ns2 ip link set dev tap2 up

如果多个network namespace需要进行通信，则需要借助bridge：  
![这里写图片描述][SouthEast 2]  
操作：

# add the namespaces
    ip netns add ns1
    ip netns add ns2
    
    # create the switch
    BRIDGE=br-test
    brctl addbr $BRIDGE
    brctl stp   $BRIDGE off
    ip link set dev $BRIDGE up
    
    #
    #### PORT 1
    # create a port pair
    ip link add tap1 type veth peer name br-tap1
    
    # attach one side to linuxbridge
    brctl addif br-test br-tap1
    
    # attach the other side to namespace
    ip link set tap1 netns ns1
    
    # set the ports to up
    ip netns exec ns1 ip link set dev tap1 up
    ip link set dev br-tap1 up
    #
    
    #### PORT 2
    # create a port pair
    ip link add tap2 type veth peer name br-tap2
    
    # attach one side to linuxbridge
    brctl addif br-test br-tap2
    
    # attach the other side to namespace
    ip link set tap2 netns ns2
    
    # set the ports to up
    ip netns exec ns2 ip link set dev tap2 up
    ip link set dev br-tap2 up
    
    #

内核实现，veth的实现与loopback interface类似，比较简单：

//drivers/net/veth.c
    static netdev_tx_t veth_xmit(struct sk_buff *skb, struct net_device *dev)
    {
        struct net_device *rcv = NULL;
        struct veth_priv *priv, *rcv_priv;
        priv = netdev_priv(dev);
        rcv = priv->peer;
        rcv_priv = netdev_priv(rcv);
        stats = this_cpu_ptr(priv->stats);
        length = skb->len;
       //转发给peer
        if (dev_forward_skb(rcv, skb) != NET_RX_SUCCESS)
            goto rx_drop;

# 4 tun/tap #

参考：  
1 [http://backreference.org/2010/03/26/tuntap-interface-tutorial/][http_backreference.org_2010_03_26_tuntap-interface-tutorial]  
2 [http://blog.csdn.net/zhaihaifei/article/details/23168621][http_blog.csdn.net_zhaihaifei_article_details_23168621]

# 5 bridge #

参考：  
[http://blog.csdn.net/zhaihaifei/article/details/38581247][http_blog.csdn.net_zhaihaifei_article_details_38581247]

# 6 vlan #

参考： [http://blog.csdn.net/zhaihaifei/article/details/38562047][http_blog.csdn.net_zhaihaifei_article_details_38562047]

# 7 network namespace #

**创建network namespace**

# ip netns add blue
    # ip netns list

**添加网口到namespace**  
先创建veth

# ip link add veth0 type veth peer name veth1

在当前namespace可以看到veth0和veth1

# ip link list
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:b2:cf:72 brd ff:ff:ff:ff:ff:ff
    3: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether ae:0d:00:e1:11:38 brd ff:ff:ff:ff:ff:ff
    4: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 42:e7:50:d4:bb:c5 brd ff:ff:ff:ff:ff:ff

将veth1加到namespace “blue”

# ip link set veth1 netns blue

此时，当前namepapce只能看到veth0。  
通过如下命令可以查看blue namespace的网口

# ip netns exec blue ip link list

**配置network namespace的网口**  
通过ip netns exec可以配置namespace的网口

# ip netns exec blue ifconfig veth1 172.17.42.2/16 up

**network namespace的网口与物理网卡的通信**

通过bridge来实现。参见veth pair一节。

参考 ：[http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/][http_blog.scottlowe.org_2013_09_04_introducing-linux-network-namespaces]

[http_www.ibm.com_developerworks_cn_linux_1310_xiawc_networkdevice]: http://www.ibm.com/developerworks/cn/linux/1310_xiawc_networkdevice/
[SouthEast]: /images/20220709/46e5c20d5ad24d0394fdeaa3c76831d0.png
[SouthEast 1]: /images/20220709/1e728e4320ea4ad6a38dc8c7bda2fe1d.png
[SouthEast 2]: /images/20220709/45bfdfc630964563a70feac448ae1d11.png
[http_backreference.org_2010_03_26_tuntap-interface-tutorial]: http://backreference.org/2010/03/26/tuntap-interface-tutorial/
[http_blog.csdn.net_zhaihaifei_article_details_23168621]: http://blog.csdn.net/zhaihaifei/article/details/23168621
[http_blog.csdn.net_zhaihaifei_article_details_38581247]: http://blog.csdn.net/zhaihaifei/article/details/38581247
[http_blog.csdn.net_zhaihaifei_article_details_38562047]: http://blog.csdn.net/zhaihaifei/article/details/38562047
[http_blog.scottlowe.org_2013_09_04_introducing-linux-network-namespaces]: http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/