Bug 50773 - [patch] NFS problems by jumbo frames to mention in bge(4) man page
Summary: [patch] NFS problems by jumbo frames to mention in bge(4) man page
Status: Closed Not Accepted
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-doc (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-10 10:40 UTC by Konrad Heuer
Modified: 2018-02-02 22:04 UTC (History)
1 user (show)

See Also:

Attachments
file.diff (643 bytes, patch)
2003-04-10 10:40 UTC, Konrad Heuer 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Konrad Heuer 2003-04-10 10:40:02 UTC 
	The bge driver allows to use jumbo frames by setting an MTU value
	of e.g. 8192. This works well in most cases. If NFS client and
	server are both capable to use jumbo frames, perfect! But clients
	with different adapters and standard MTUs can't access files on
	an NFS server if the latter one uses jumbo frames. Thus possible
	NFS problems should be mentioned in the man page.

How-To-Repeat: 	Try to setup client and server as explained above.
Comment 1 John-Mark Gurney freebsd_committer freebsd_triage 2004-09-20 21:15:40 UTC 
Responsible Changed
From-To: freebsd-doc->jmg

I'm going to take over this..  information that is general to to all 
ethernet cards supporting jumbo frames should not be in a card specific 
man page..
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:52 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Eugene Grosbein freebsd_committer freebsd_triage 2018-02-02 22:04:14 UTC 
The problem is not bge-specific and it is not NFS-specific too as inconsistent MTU within a network is just beginner administrator's mistake.