无来

不管你来还是不来
我都在这里，夜夜点亮
不是为了守候
只是为了做好我自己

0%

发表于 更新于 分类于 
1
2
3
4
5
6
7
8
9
$ networksetup -listallnetworkservices  
An asterisk (*) denotes that a network service is disabled.  
SAMSUNG Modem  
Bluetooth DUN  
Thunderbolt Ethernet  
Wi-Fi  
Bluetooth PAN  
Thunderbolt Bridge  
$ networksetup -setv6off Wi-Fi

发表于 更新于 分类于 
1
2
3
Author: Dude
Date: 01-Jun-2013
Version: B
1
2
Last updates:
23-Jul-2013, changes required due to forum upgrade

https://community.oracle.com/thread/2546040

What is Linux network interface bonding? Simply put, the Linux system provides a kernel driver, which can create a logical network device (bond) using 2 or more Network Interface Controllers (NIC) to accomplish link-aggregation and adapter fault-tolerance. For more information, please see the Deployment Guide at https://linux.oracle.com/documentation/

The channel bonding interface supports several modes of operation. In a typical active-backup set up for fault-tolerance, the system performs MII-based health monitoring of the network interface slaves (eth0, eth1) and assigns them according to bond options and interface availability. In active-backup mode (mode 1), only the current active network device is seen externally.

Linux bonding for fault-tolerance under Oracle VM VirtualBox does not seem to function as advertised. Searching the Internet for more information shows that other people have tried to set up Linux bonding using various virtualization products, virtual host network adapter and bonding options, but without success.

It appears the management of Media Access Control addresses (MAC) interferes with internal routing methods between the host and the virtual machine guest. Using the modinfo bonding command (fig. 1) shows a listing of available parameters for the bonding kernel module. The fail_over_mac parameter addresses the Mac address issue in VirtualBox.

1
2
3
4
5
6
7
# modinfo bonding
filename:       /lib/modules/2.6.39-400.17.1.el6uek.x86_64
                /kernel/drivers/net/bonding/bonding.ko
parm:           fail_over_mac:For active-backup,
                do not set all slaves to the same MAC;
                0 for none (default), 1 for active, 2 for follow (charp)

Configuration Example

1
2
Virtualization Product: Oracle VM VirtualBox 4.2.10
VM Guest OS: Oracle Linux 6.4 (x64)

VM adapter settings: Bridged Adapter, Paravirtualized Network (virtio-net)

1
2
Adapter1 (eth0): 080027436617, en0, Ethernet 1
Adapter2 (eth1): 08002708F36A, en0, Ethernet 1

Note: If you wish to reset the network adapter names and MAC addresses used by the Oracle Linux guest system, erase the content of /etc/udev/rules.d/70-persistent-net.rules and restart the virtual machine.

1. Create or modify the following configuration files:

/etc/modprobe.d/bonding-eth0_eth1.conf

alias bond0 bonding

/etc/sysconfig/network-scripts/ifcfg-bond0

1
2
3
4
5
6
7
8
9
10
DEVICE=bond0
IPADDR=10.0.2.12
NETMASK=255.0.0.0
GATEWAY=10.0.0.138
DNS1=10.0.0.138
DNS2=8.8.8.8
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
BONDING_OPTS="mode=1 miimon=100 fail_over_mac=1"

/etc/sysconfig/network-scripts/ifcfg-eth0

1
2
3
4
5
6
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no

/etc/sysconfig/network-scripts/ifcfg-eth1

1
2
3
4
5
6
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no

2. Restart the system or network services (root):

# service network restart

Configuration Test

Enter the following commands as user root to verify proper operation of NIC bonding:

1
2
3
4
5
6
7
8
9
10
11
# tail /var/log/messages
bond0: setting mode to active-backup (1).
bond0: Setting MII monitoring interval to 100.
bond0: Setting fail_over_mac to active (1).
bond0: Adding slave eth0.
bond0: making interface eth0 the new active one.
bond0: first active interface up!
bond0: enslaving eth0 as an active interface with an up link.
bond0: Adding slave eth1.
bond0: enslaving eth1 as a backup interface with an up link.

1
2
3
4
5
6
7
8
9
10
11
12
# ifconfig
bond0     Link encap:Ethernet  HWaddr 08:00:27:43:66:17  
          inet addr:10.0.2.12  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::a00:27ff:fe43:6617/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr 08:00:27:43:66:17  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 08:00:27:08:F3:6A  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1

1
2
3
4
5
6
7
# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
0.0.0.0         10.0.0.138      0.0.0.0         UG        0 0          0 bond0
10.0.0.0        0.0.0.0         255.0.0.0       U         0 0          0 bond0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 bond0

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
# ifconfig eth0 down

# tail /var/log/messages
bond0: link status definitely down for interface eth0, disabling it
bond0: making interface eth1 the new active one.

# ifconfig
bond0     Link encap:Ethernet  HWaddr 08:00:27:08:F3:6A  
          inet addr:10.0.2.12  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::a00:27ff:fe43:6617/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

eth1      Link encap:Ethernet  HWaddr 08:00:27:08:F3:6A  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
# ifconfig eth0 up

# ifconfig eth1 down

# tail /var/log/messages
bond0: link status definitely up for interface eth0, 4294967295 Mbps full duplex.
bond0: link status definitely down for interface eth1, disabling it
bond0: making interface eth0 the new active one.

# ifconfig
bond0     Link encap:Ethernet  HWaddr 08:00:27:43:66:17  
          inet addr:10.0.2.12  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::a00:27ff:fe43:6617/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr 08:00:27:43:66:17  
          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1

During the above test, the client network connection from host 10.0.0.1 (ssh) was maintained without any noticeable interruption. As it can be seen from the syslog and ifconfig command output, the bond0 interface was automatically assigned either the MAC address of eth0 or eth1 and the fail-over worked as advertised.

发表于 更新于 分类于

错误提示

Restarting network (via systemctl): Job for network.service failed. See ‘systemctl status network.service’ and ‘journalctl -xn’ for details.

解决方法

查找原因

systemctl status network.service

 cat /var/log/message |grep network
  1. Could not load file ‘/etc/sysconfig/network-scripts/ifcfg-lo’
    This is generated by command ‘nmcli con load /etc/sysconfig/network-scripts/ifcfg-lo’ executed by ‘ifup’

Tadding the line “TYPE=loopback” to the file /etc/sysconfig/network-scripts/ifcfg-lo

  1. 如果是网卡
    • ip addr get mac address
    • add to /etc/sysconfig/network-scripts/ifcfg-XXXX HWADDR=XXXXXXXXXXX

发表于 更新于 分类于

Ever tried logging into a machine with ssh and found you have to wait much longer than reasonable for the session to start? This happened to me a few times and was especially annoying with machines on my local network (or a VM attached to a virtual network) that should be letting me in immediately.

I eventually got mad enough to strace the SSH daemon and debug what was going on and it turns out it’s a DNS thing. Basically the session is slow to start because the SSH server is trying to lookup the hostname of the SSH client and for whatever reason it’s timing out (e.g., it can’t reach a nameserver, because you happen to be offline)

There are a couple of very simple ways to fix that:

1
2
add "UseDNS no" to /etc/ssh/sshd_config
add the client's net address to the server's /etc/hosts

*** 改项可能会导致远程连接失败

发表于 更新于 分类于

1 先改为可编辑模式

mount -o remount,rw /

2 编辑文件 /etc/fstab

1
vim /etc/fstab

将ro修改为rw

发表于 更新于 分类于
  1. From the Apple menu (upper left corner of your desktop) choose System Preferences…
  • Open Network
  • In the toolbar below all of your network interfaces, click the gear wheel to access a dropdown menu
  • From that dropdown menu, select Manage Virtual Interfaces…
  • Click on + to access another dropdown menu
  • From that dropdown menu, select New VLAN…
  • Enter an appropriate name for your new VLAN, e.g. DMZ
  • Enter the desired tag, e.g. 23
  • Choose the correct physical interface, normally Ethernet
  • Click Create
  • Click Done
  • Configure your new VLAN interface as you would configure a physical interface, e.g. assign it an IP address, network mask, etc.
  • Click Apply
  • Close the network preferences window.

发表于 更新于 分类于

删除这些目录是很简单的，命令如下

find . -type d -name ".svn"|xargs rm -rf

或者

find . -type d -iname ".svn" -exec rm -rf {} \;

发表于 更新于 分类于
个人观点: 现阶段互联网公司普遍盲区在售后服务的体验。

最近想买一个测试雾霾的表，看了一些文章，也看了知乎上姜洋的答复。作为一个互联网的参与者，就选择购买了在天猫旗舰店买了空气果2.物流很快。包装很精美。到这个阶段用户体验还是不错的。

不过打开发现是空气果sport.这个时候不好的体验开始。

  1. 通过阿里旺旺留言。
  • 电话确认无法连接
  • 需要自己把货发过去，然后再给我寄过来
  • 联系人