10-20-2015
ifconfig eth - errors after certain packets received
Hi,
I am facing an issue with one of the 10G fiber link. After certain packets received. I am seeing errors in ifconfig eth* output.
MTU is set to 9000.
any idea?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
HI,
When I do 'service network restart' , I am getting the following error.
"3c501 device eth0 does not seem to be present, delaying initialization"
Can any one suggest me the cause/solution for this?
When I do 'lspci' it is showing the ehternet card as
" Ethernet controller"Marvell... (2 Replies)
Discussion started by: praveen_b744
2 Replies
2. Linux
Hi
I had a DL380 with two two port eth cards. I now replaced one with a four port eth card and my interfaces seemed to have jumped around.
Is there a method of moving eth ports... eg making port eth4 eth2.:confused: (2 Replies)
Discussion started by: theroncj
2 Replies
3. UNIX for Dummies Questions & Answers
folks;
This might sounds stupid but i hope someone can give me an answer:
On my Linux SUSE boxes, i have 2 NIC cards NIC1 & NIC2. I always assumed that NIC1 is eth0 when i run "ifconfig" and NIC2 is eth1
but i noticed that's not always the case.
Is there a way or a command i can run to find... (1 Reply)
Discussion started by: Katkota
1 Replies
4. IP Networking
hi,
Could some one answer this please
we have a program with client socket declared which connect to a server
for the above program description we wont send an interface information ... let us suppose, I have two interfaces (eth0 , eth1) which are assigned some ip, which interface the... (1 Reply)
Discussion started by: Gopi Krishna P
1 Replies
5. IP Networking
Hi people,
I have a solaris OS system. I configured its interfaces. They are UP but not in RUNNING status except loopback interface. I made the interfaces DOWN and UP again. The other side of the interfaces (switch ports) are UP. Does anyone have any idea? What may cause this problem, How can I... (1 Reply)
Discussion started by: hubatuwang
1 Replies
6. Shell Programming and Scripting
I want to run dhcpclient for all the eth* which has no ip
for example
eth0 Link encap:Ethernet HWaddr 00:1E:67:3E:BA:EF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0... (6 Replies)
Discussion started by: yanglei_fage
6 Replies
7. Red Hat
Hi,
I´ve given only this info to configure a network interface : "port 1 PCI 4"
I´ve been searching for any kind of relationship in the system which allow me to find the etc that must be configured...
Please, could anybody help me?
rhxx:#/root# lspci |grep -i "PCI BRIDGE"
00:01.0 PCI... (0 Replies)
Discussion started by: pabloli150
0 Replies
8. UNIX for Dummies Questions & Answers
hi guys
I have a server which has 2 nics eth0 and eth1
eth0 is used for our email traffic server. everything working fine
some time later a eth1 was added for backup purposes so this new nic sends data to another vlan for backup purposes
all of a sudden our mail server starts to fail... (3 Replies)
Discussion started by: karlochacon
3 Replies
9. UNIX for Advanced & Expert Users
Hi All,
I have dual boot on my laptop - Win8 And linuxMint.
From linuxmint i had copied all my data found on the NTFS partitions (on my laptop) to an
external hard drive (formatted with ext3). i used rsync for this.
Now after my hard disk crashed, am restoring the data back from ext3... (2 Replies)
Discussion started by: coolatt
2 Replies
10. UNIX for Advanced & Expert Users
Dear community,
I'm in trouble with Red Hat Server 5.8. After rebooting the server, I loose two interfaces used for bond2 (eth4 and eth5). I reboot twice the server but the result is always:
# service network restart
Shutting down interface bond0:
Shutting down... (1 Reply)
Discussion started by: Lord Spectre
1 Replies
SL(4) BSD Kernel Interfaces Manual SL(4)
NAME
sl -- Serial Line IP (SLIP) network interface
SYNOPSIS
pseudo-device sl
DESCRIPTION
The sl interface allows asynchronous serial lines to be used as IPv4 network interfaces using the SLIP protocol.
To use the sl interface, the administrator must first create the interface and assign a tty line to it. The sl interface is created using
the ifconfig(8) create subcommand, and slattach(8) is used to assign a tty line to the interface. Once the interface is attached, network
source and destination addresses and other parameters are configured via ifconfig(8).
The sl interface can use Van Jacobson TCP header compression and ICMP filtering. The following flags to ifconfig(8) control these properties
of a SLIP link:
link0 Turn on Van Jacobson header compression.
-link0 Turn off header compression. (default)
link1 Don't pass through ICMP packets.
-link1 Do pass through ICMP packets. (default)
link2 If a packet with a compressed header is received, automatically enable compression of outgoing packets. (default)
-link2 Don't auto-enable compression.
DIAGNOSTICS
sl%d: af%d not supported . The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
SEE ALSO
inet(4), intro(4), ppp(4), strip(4), ifconfig(8), slattach(8), sliplogin(8), slstats(8)
J. Romkey, A Nonstandard for Transmission of IP Datagrams over Serial Lines: SLIP, RFC, 1055, June 1988.
Van Jacobson, Compressing TCP/IP Headers for Low-Speed Serial Links, RFC, 1144, February 1990.
HISTORY
The sl device appeared in NetBSD 1.0.
BUGS
SLIP can only transmit IPv4 packets between preconfigured hosts on an asynchronous serial link. It has no provision for address negotiation,
carriage of additional protocols (e.g. XNS, AppleTalk, DECNET), and is not designed for synchronous serial links. This is why SLIP has been
superseded by the Point-to-Point Protocol (PPP), which does all of those things, and much more.
BSD
July 9, 2006 BSD