[opensuse] configure jumbo frames
How do I configure my IG nic to use jumbo frames? Neither ifconfig nor ip work for me. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Feustel wrote:
How do I configure my IG nic to use jumbo frames? Neither ifconfig nor ip work for me.
Does your NIC support jumbo frames? The usual way to configure it seems to be "ifconfig ethX mtu 9000". /Per -- Per Jessen, Zürich (9.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen wrote:
Dave Feustel wrote:
How do I configure my IG nic to use jumbo frames? Neither ifconfig nor ip work for me.
Does your NIC support jumbo frames?
The usual way to configure it seems to be "ifconfig ethX mtu 9000".
I just tried configuring a Broadcom 5782 gigabit nic to jumbo frames, but it doesn't appear to support it. The tg3 drivers checks a certain flag to work out the max MTU size. /Per -- Per Jessen, Zürich (9.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Apr 23, 2009 at 08:44:35AM +0200, Per Jessen wrote:
Dave Feustel wrote:
How do I configure my IG nic to use jumbo frames? Neither ifconfig nor ip work for me.
Does your NIC support jumbo frames?
The usual way to configure it seems to be "ifconfig ethX mtu 9000".
/Per
This command worked on Fedora 9, but not on suse. f9: MSI K9N NEO motherboard with 1G nic SUSE MSI K9N NEO V3 motherboard with 1G nic That command also failed on OpenBSD which seems to want 'mtu=X' instead of 'mtu X'. 1G Nic is Netgear 311. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Feustel wrote:
On Thu, Apr 23, 2009 at 08:44:35AM +0200, Per Jessen wrote:
Dave Feustel wrote:
How do I configure my IG nic to use jumbo frames? Neither ifconfig nor ip work for me.
Does your NIC support jumbo frames?
The usual way to configure it seems to be "ifconfig ethX mtu 9000".
/Per
This command worked on Fedora 9, but not on suse. f9: MSI K9N NEO motherboard with 1G nic SUSE MSI K9N NEO V3 motherboard with 1G nic
The error I get (when jumbos aren't supported by the NIC) is "SIOCSIFMTU invalid argument". Any chance you have different version of drivers on Fedora/openSUSE?
That command also failed on OpenBSD which seems to want 'mtu=X' instead of 'mtu X'. 1G Nic is Netgear 311.
And it does actually run with jumbo frames - did you test it? /Per -- Per Jessen, Zürich (15.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Apr 23, 2009 at 02:21:29PM +0200, Per Jessen wrote:
Dave Feustel wrote:
On Thu, Apr 23, 2009 at 08:44:35AM +0200, Per Jessen wrote:
Dave Feustel wrote:
How do I configure my IG nic to use jumbo frames? Neither ifconfig nor ip work for me.
Does your NIC support jumbo frames?
The usual way to configure it seems to be "ifconfig ethX mtu 9000".
/Per
This command worked on Fedora 9, but not on suse. f9: MSI K9N NEO motherboard with 1G nic SUSE MSI K9N NEO V3 motherboard with 1G nic
The error I get (when jumbos aren't supported by the NIC) is "SIOCSIFMTU invalid argument". Any chance you have different version of drivers on Fedora/openSUSE?
I get two different errors on OpenBSD and Suse 'mtu X' gives invalid argument. 'mtu=X' gives invalid value.
That command also failed on OpenBSD which seems to want 'mtu=X' instead of 'mtu X'. 1G Nic is Netgear 311.
And it does actually run with jumbo frames - did you test it?
I don't know how to test if jumbo frames work. F9 took an mtu 9000 command. Fedora: eth0 Link encap:Ethernet HWaddr 00:16:17:47:3F:9E inet addr:192.168.6.32 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::216:17ff:fe47:3f9e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:115502 errors:0 dropped:0 overruns:0 frame:0 TX packets:96557 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:101806631 (97.0 MiB) TX bytes:15754608 (15.0 MiB) Interrupt:23 Base address:0xc000 Suse: i 4/home/dave}ifconfig eth0 Link encap:Ethernet HWaddr 00:19:DB:D0:23:BC inet addr:192.168.6.33 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::219:dbff:fed0:23bc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41631 errors:0 dropped:0 overruns:0 frame:0 TX packets:39144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13634227 (13.0 Mb) TX bytes:13886152 (13.2 Mb) Interrupt:250 Base address:0xe000 OpenBSD: 1/home/daf}ifconfig re0 re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 lladdr 00:22:3f:db:f3:90 media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.6.1 netmask 0xffffff00 broadcast 192.168.6.255 inet6 fe80::222:3fff:fedb:f390%re0 prefixlen 64 scopeid 0x1 1/home/daf} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Feustel wrote:
That command also failed on OpenBSD which seems to want 'mtu=X' instead of 'mtu X'. 1G Nic is Netgear 311.
And it does actually run with jumbo frames - did you test it?
I don't know how to test if jumbo frames work. F9 took an mtu 9000 command.
Try pinging with an 8000 byte packet.
Fedora: eth0 Link encap:Ethernet HWaddr 00:16:17:47:3F:9E inet addr:192.168.6.32 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::216:17ff:fe47:3f9e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:115502 errors:0 dropped:0 overruns:0 frame:0 TX packets:96557 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:101806631 (97.0 MiB) TX bytes:15754608 (15.0 MiB) Interrupt:23 Base address:0xc000
Suse: i 4/home/dave}ifconfig eth0 Link encap:Ethernet HWaddr 00:19:DB:D0:23:BC inet addr:192.168.6.33 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::219:dbff:fed0:23bc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41631 errors:0 dropped:0 overruns:0 frame:0 TX packets:39144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13634227 (13.0 Mb) TX bytes:13886152 (13.2 Mb) Interrupt:250 Base address:0xe000
Uh, those are actually two different cards/NICs you're displaying here? 00:16:17:47:3F:9E and 00:19:DB:D0:23:BC - also they're both MSI, not Netgear. Are you sure they're _exactly_ the same hardware? /Per -- Per Jessen, Zürich (17.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Apr 23, 2009 at 03:11:59PM +0200, Per Jessen wrote:
Dave Feustel wrote:
That command also failed on OpenBSD which seems to want 'mtu=X' instead of 'mtu X'. 1G Nic is Netgear 311.
And it does actually run with jumbo frames - did you test it?
I don't know how to test if jumbo frames work. F9 took an mtu 9000 command.
Try pinging with an 8000 byte packet.
Fedora: eth0 Link encap:Ethernet HWaddr 00:16:17:47:3F:9E inet addr:192.168.6.32 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::216:17ff:fe47:3f9e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 RX packets:115502 errors:0 dropped:0 overruns:0 frame:0 TX packets:96557 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:101806631 (97.0 MiB) TX bytes:15754608 (15.0 MiB) Interrupt:23 Base address:0xc000
Suse: i 4/home/dave}ifconfig eth0 Link encap:Ethernet HWaddr 00:19:DB:D0:23:BC inet addr:192.168.6.33 Bcast:192.168.6.255 Mask:255.255.255.0 inet6 addr: fe80::219:dbff:fed0:23bc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:41631 errors:0 dropped:0 overruns:0 frame:0 TX packets:39144 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13634227 (13.0 Mb) TX bytes:13886152 (13.2 Mb) Interrupt:250 Base address:0xe000
Uh, those are actually two different cards/NICs you're displaying here? 00:16:17:47:3F:9E and 00:19:DB:D0:23:BC - also they're both MSI, not Netgear. Are you sure they're _exactly_ the same hardware?
/Per
F9 and Suse are running on different versions of MSI K9N motherboards (v1,v3) with builtin 1G nics. The v3 motherboard has a dual processor. The Netgear card is plugged into a 10-year-old Dell. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Feustel wrote:
F9 and Suse are running on different versions of MSI K9N motherboards (v1,v3) with builtin 1G nics. The v3 motherboard has a dual processor.
The Netgear card is plugged into a 10-year-old Dell.
I suspect what you have is this: 1) MSI K9N v1 - NICs support jumbo frames 2) MSI K9N v3 - NICs do not support jumbo frames 3) Netgear - does not support jumbo frames I can't think of a reason why there would be such a difference between your MSI boards, so I could be way off here. /Per -- Per Jessen, Zürich (16.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Apr 23, 2009 at 03:24:29PM +0200, Per Jessen wrote:
Dave Feustel wrote:
F9 and Suse are running on different versions of MSI K9N motherboards (v1,v3) with builtin 1G nics. The v3 motherboard has a dual processor.
The Netgear card is plugged into a 10-year-old Dell.
I suspect what you have is this:
1) MSI K9N v1 - NICs support jumbo frames 2) MSI K9N v3 - NICs do not support jumbo frames
The v3 motherboard has a Realtek RTL8111b nic chip. I found the data sheet (RTL8111B_8168B_Registers_DataSheet_1.0.pdf) and the Jumbo frame support goes to 7552 bytes. Why Suse doesn't support the Jumbo setting is a mystery.
3) Netgear - does not support jumbo frames
Netgear GA311 supports jumbo frames to 7500. http://kb.netgear.com/app/answers/detail/a_id/222 Netgear strongly advises setting jumbo frames on all adapters to the same value.
I can't think of a reason why there would be such a difference between your MSI boards, so I could be way off here.
/Per
-- Per Jessen, Zürich (16.3°C)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Feustel wrote:
On Thu, Apr 23, 2009 at 03:24:29PM +0200, Per Jessen wrote:
Dave Feustel wrote:
F9 and Suse are running on different versions of MSI K9N motherboards (v1,v3) with builtin 1G nics. The v3 motherboard has a dual processor.
The Netgear card is plugged into a 10-year-old Dell.
I suspect what you have is this:
1) MSI K9N v1 - NICs support jumbo frames 2) MSI K9N v3 - NICs do not support jumbo frames
The v3 motherboard has a Realtek RTL8111b nic chip. I found the data sheet (RTL8111B_8168B_Registers_DataSheet_1.0.pdf) and the Jumbo frame support goes to 7552 bytes. Why Suse doesn't support the Jumbo setting is a mystery.
According to the kernel source, the latest driver version supports only "baby" jumbo frames, size <= 7200. (assuming the driver is r8169).
3) Netgear - does not support jumbo frames
Netgear GA311 supports jumbo frames to 7500. http://kb.netgear.com/app/answers/detail/a_id/222
Netgear strongly advises setting jumbo frames on all adapters to the same value.
Yeah :-) /Per -- Per Jessen, Zürich (13.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Apr 23, 2009 at 05:38:34PM +0200, Per Jessen wrote:
Dave Feustel wrote:
On Thu, Apr 23, 2009 at 03:24:29PM +0200, Per Jessen wrote:
Dave Feustel wrote:
F9 and Suse are running on different versions of MSI K9N motherboards (v1,v3) with builtin 1G nics. The v3 motherboard has a dual processor.
The Netgear card is plugged into a 10-year-old Dell.
I suspect what you have is this:
1) MSI K9N v1 - NICs support jumbo frames 2) MSI K9N v3 - NICs do not support jumbo frames
The v3 motherboard has a Realtek RTL8111b nic chip. I found the data sheet (RTL8111B_8168B_Registers_DataSheet_1.0.pdf) and the Jumbo frame support goes to 7552 bytes. Why Suse doesn't support the Jumbo setting is a mystery.
According to the kernel source, the latest driver version supports only "baby" jumbo frames, size <= 7200. (assuming the driver is r8169).
That worked! Thanks!
3) Netgear - does not support jumbo frames
Netgear GA311 supports jumbo frames to 7500. http://kb.netgear.com/app/answers/detail/a_id/222
Netgear strongly advises setting jumbo frames on all adapters to the same value.
Yeah :-)
/Per
-- Per Jessen, Zürich (13.4°C)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Dave Feustel -
Per Jessen