Bug 6530 - `ip ro` advmss option is not supported
Summary: `ip ro` advmss option is not supported
Status: RESOLVED FIXED
Alias: None
Product: Busybox
Classification: Unclassified
Component: Networking (show other bugs)
Version: 1.21.x
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-01 11:44 UTC by ojab
Modified: 2017-04-07 15:01 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
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 ojab 2013-10-01 11:44:11 UTC 
From `man ip`:
>advmss NUMBER (2.3.15+ only)
>              the  MSS  ('Maximal  Segment  Size')  to advertise to these destinations when establishing TCP connections.  If it is not given, Linux uses a default value calculated from the first hop device MTU.  (If the path to these destination is asymmetric, this guess may be wrong.)

But busybox-1.21.1 (and trunk afaiu) doesn't support it:
>$busybox ip ro add default via 1.1.1.1 dev eth1 advmss 8910
>ip: either "to" is duplicate, or "advmss" is garbage
Comment 1 Denys Vlasenko 2017-04-07 15:01:31 UTC 
Fixed in git.