Sponsored Content
Special Forums IP Networking IPV6 very slow, not respecting MTU?? Post 302564426 by Corona688 on Thursday 13th of October 2011 03:40:28 PM
Old 10-13-2011
This bug happened in kernels from 2008 or so. IPv6 transmissions would get their MTU from the wrong interface, I think the loopback.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to change the MTU in Unix registry?

Does anyone know how to or know of a web page where I can find how to change the MTU speed in Unix registry? Any info. would be greatly appreciated. Thanks, Techie (2 Replies)
Discussion started by: Techie_girl
2 Replies

2. Solaris

MTU Value

Hi guys, Do anyone know how to change the MTU value on an interface on Solaris 10 server? (2 Replies)
Discussion started by: shabu
2 Replies

3. Solaris

MTU setting - solaris 9 how to check??

I need to check the mtu setting on my server, I am told I need to use the ndd command and check the tcp setting tcp_mss_max I have done so and all I can see is the below, tcp_mss_def_ipv4 (read and write) tcp_mss_max_ipv4 (read and write) How can I check the... (4 Replies)
Discussion started by: frustrated1
4 Replies

4. Solaris

how to find MTU size on solaris.

How do i find the MTU size on solaris, which file to look into. Please help I'm a newbie to administration. (1 Reply)
Discussion started by: ramky79
1 Replies

5. HP-UX

MTU size

Hi, Just want to ask on how to check and change the MTU size of the nodes from 1500 to 9000? I need to match the MTU size of some cluster nodes which has 1500 to the others with 9000 because they are inconsistent. Thanks (1 Reply)
Discussion started by: criphaze22
1 Replies

6. OS X (Apple)

AFP mount + Chown/Chgrp respecting

Hello all... Does anyone know how to make an AFP mount of home directories (/Volumes/users off of another server) so that any users doing an ssh login retain write permission to their individual folders, read-write permissions to folders chowned to appropriate group... and so that newly created... (0 Replies)
Discussion started by: drkdev
0 Replies

7. UNIX for Dummies Questions & Answers

MTU setting for IRIX

Couldn't find an IRIX forum, so I'm posting to this one... Just had our SAs rebuild an IRIX machine and now I need to set the MTU to 1344 (vice 1500 default). I can set it manually using the ifconfig command, but it won't survive a reboot. I made an entry into the /etc/init.d/ifconfig-1.options... (0 Replies)
Discussion started by: scottwevans
0 Replies

8. UNIX for Dummies Questions & Answers

Assigning ipv6 to bonding interface - getting old as well as changed ipv6 in ifconfig output

Hi, I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Discussion started by: omkar.jadhav
1 Replies

9. Solaris

Set MTU value for ipv6 interfaces

Hi, I am trying to set mtu value for ipv6 interfaces. I know how to set it for ipv4 interfaces ifconfig net1 mtu 1240 Do I need to add any iptype for the above command ? Note: OS:Solaris 10 TIA (3 Replies)
Discussion started by: Sumanthsv
3 Replies
LO(4)                                                      BSD Kernel Interfaces Manual                                                      LO(4)

NAME
lo -- software loopback network interface SYNOPSIS
device loop DESCRIPTION
The loop interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communication. As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which it is to be used. These addresses may be set or changed with the SIOCSIFADDR ioctl(2). The loopback interface should be the last interface configured, as protocols may use the order of configuration as an indication of priority. The loopback should never be configured first unless no hard- ware interfaces exist. If the transmit checksum offload capability flag is enabled on a loopback interface, checksums will not be generated by IP, UDP, or TCP for packets sent on the interface. If the receive checksum offload capability flag is enabled on a loopback interface, checksums will not be validated by IP, UDP, or TCP for packets received on the interface. By default, both receive and transmit checksum flags will be enabled, in order to avoid the overhead of checksumming for local communication where data corruption is unlikely. If transmit checksum generation is disabled, then validation should also be disabled in order to avoid packets being dropped due to invalid checksums. DIAGNOSTICS
lo%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. SEE ALSO
inet(4), intro(4) HISTORY
The lo device appeared in 4.2BSD. The current checksum generation and validation avoidance policy appeared in FreeBSD 8.0. BSD March 15, 2009 BSD
All times are GMT -4. The time now is 05:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy