Project

General

Profile

Error #422

802.1AD have small MTU value

Added by Roger Pueyo Centelles over 2 years ago. Updated about 1 month ago.

Status:
Resolt
Priority:
Normal
Category:
Network
Target version:
Start date:
08/30/2017
Due date:
% Done:

100%

Estimated time:
1.00 h
Spent time:

Description

802.1Q allows to me for use MTU value over 1500 on fragment and network functions normally, transperent. But in 802.1AD this value is 'jammed' on 1430 for me, I tested this with 'ping -s'
Thus, the network doesn't work between two nodes connected over ethernet. I just backed to 802.1Q in config files.

History

#1 Updated by Roger Pueyo Centelles over 1 year ago

  • Category set to Network
  • Assignee set to Roger Pueyo Centelles
  • Target version set to 5.0

Suggestion: remove VLANs for routing?

#2 Updated by guifi pedro about 1 month ago

Roger Pueyo Centelles va escriure:

Suggestion: remove VLANs for routing?

I agree that removing VLANs is better, we had a discussion on libremesh mailing list where there was a problem with a specific device

https://lists.libremesh.org/pipermail/lime-dev/2019-August/thread.html

#3 Updated by Roger Pueyo Centelles about 1 month ago

  • Status changed from Nou to Resolt
  • % Done changed from 0 to 100
  • Estimated time set to 1.00 h

Hi Pedro,

Thanks for your comment and the links. Yes, using different VLANs for the routing protocol[s] was cool back when all interfaces were physical (eth0, eth1...) but started to become a mess with eth0.1 and so. 802.1ad VLANs was a good attempt, but drivers support was varied and mostly bad.

I took the decision of not using VLANs (neither 802.1q nor 802.1ad) for routing by default, as you can see in http://dev.qmp.cat/projects/qmp/repository/revisions/a9e636957d1d5b333759e9e647590a6f51d2ae3f . So, I guess, from qMp v5.0 on, they won't be there anymore.

Also available in: Atom PDF