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
SHOREWALL-TCFILTERS(5)						  [FIXME: manual]					    SHOREWALL-TCFILTERS(5)

NAME
tcfilters - Shorewall u32 classifier rules file SYNOPSIS
/etc/shorewall/tcfilters DESCRIPTION
Entries in this file cause packets to be classified for traffic shaping. Beginning with Shorewall 4.4.15, the file may contain entries for both IPv4 and IPv6. By default, all rules apply to IPv4 but that can be changed by inserting a line as follows: IPV4 Following entries apply to IPv4. IPV6 Following entries apply to IPv6 ALL Following entries apply to both IPv4 and IPv6. Each entry is processed twice; once for IPv4 and once for IPv6. The columns in the file are as follows (where the column name is followed by a different name in parentheses, the different name is used in the alternate specification syntax). CLASS - interface:class The name or number of an interface defined in shorewall-tcdevices[1](5) followed by a class number defined for that interface in shorewall-tcclasses[2](5). SOURCE - {-|address} Source of the packet. May be a host or network address. DNS names are not allowed. DEST - {-|address}} Destination of the packet. May be a host or network address. DNS names are not allowed. You may exclude certain hosts from the set already defined through use of an exclusion (see shorewall-exclusion[3](5)). PROTO - {-|protocol-number|protocol-name|all} Protocol. DEST PORT (dport) - [-|port-name-or-number] Optional destination Ports. A Port name (from services(5)) or a port number; if the protocol is icmp, this column is interpreted as the destination icmp-type(s). SOURCE PORT (sport) - [-|port-name-or-number] Optional source port. TOS (Optional) - [-|tos] Specifies the value of the TOS field. The tos value can be any of the following: o tos-minimize-delay o tos-maximuze-throughput o tos-maximize-reliability o tos-minimize-cost o tos-normal-service o hex-number o hex-number/hex-number The hex-numbers must be exactly two digits (e.g., 0x04)x. LENGTH - [-|number] Optional - Must be a power of 2 between 32 and 8192 inclusive. Packets with a total length that is strictly less than the specified number will match the rule. EXAMPLE
Example 1: Place all 'ping' traffic on interface 1 in class 10. Note that ALL cannot be used because IPv4 ICMP and IPv6 ICMP are two different protocols. #CLASS SOURCE DEST PROTO DEST # PORT IPV4 1:10 0.0.0.0/0 0.0.0.0/0 icmp echo-request 1:10 0.0.0.0/0 0.0.0.0/0 icmp echo-reply IPV6 1:10 ::/0 ::/0 icmp6 echo-request 1:10 ::/0 ::/0 icmp6 echo-reply FILES
/etc/shorewall/tcfilters SEE ALSO
http://shorewall.net/traffic_shaping.htm http://shorewall.net/MultiISP.html http://shorewall.net/PacketMarking.html http://shorewall.net/configuration_file_basics.htm#Pairs shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-ecn(5), shorewall-exclusion(5), shorewall-hosts(5), shorewall_interfaces(5), shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5), shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5), shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5) NOTES
1. shorewall-tcdevices http://www.shorewall.net/manpages/shorewall-tcdevices.html 2. shorewall-tcclasses http://www.shorewall.net/manpages/shorewall-tcclasses.html 3. shorewall-exclusion http://www.shorewall.net/manpages/shorewall-exclusion.html [FIXME: source] 06/28/2012 SHOREWALL-TCFILTERS(5)
All times are GMT -4. The time now is 07:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy