[Bug 1541544] Re: ubuntu-installer makes a contradictional statement regarding layer2/layer3

[Dimitri John Ledkov]

Is the card type at all exposed anywhere?

E.g:
cat /sys/bus/ccwgroup/devices/0.0.0600/card_type

For me says - Virt.NIC QDIO, which sounds like case 3 (this is z/VM). I
don't think i have access to OSA-card direct, or Hipersockets.

I guess we could sense on card_type and use it in the question. However
there are a few, aren't there looking at the source code there are a
few:

https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable/tree/drivers/s390/net/qeth_core_main.c#n137

Virt.NIC QDIO
Virt.NIC Hiper
Virt.NIC OSM
Virt.NIC OSX
unknown
OSD_100
HSTR
OSD_1000
OSD_10GIG
OSD_FE_LANE
OSD_TR_LANE
OSD_GbE_LANE
OSD_ATM_LANE
OSD_Express
HiperSockets
OSN
OSM_1000
OSX_10GIG

I guess layer2 is a good default for most of them. Which of the above do
you believe layer3 is a better guess? And then working that into the
question would be good:

(In d-i "question" comes first, then decription, then answers. This
particular question is a boolean yes/no question -> true (l2) or false
(l3), changing this will result in breaking compatibility with preseed
files)

"""
-> Select layer for Virt.Nic Hiper card

The qeth network driver is about to be configured for the Virt.Nic Hiper
card. The driver and the card can use either OSI model Layer 2 or Layer
3 modes. And this setting should match the network configuration this
card is attached to. Using the card in Layer 2 mode will make it keep
the MAC addresses of the IPv4 packets. Alternative is to use Layer 3
mode, in that mode LLC headers are removed from the incoming IPv4
packets. Incorrect mode may lead to lack of connectivity. Use this card
in Layer 2 mode?

Default [Y]: Yes / No
""

The Virt.Nic Hiper card is just an example, as actually variable will be
replaced with the contents of card_type sysfs property, which should be
available at that point. The full list of possible card types, from
current kernel sources, is shown above.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1541544

Title:
  ubuntu-installer makes a contradictional statement regarding
  layer2/layer3

Status in debian-installer package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Thorsten Diehl <thorsten.diehl at de.ibm.com> - 2016-02-03 12:05:19 ==
  When I configure a qeth OSA device, the installer asks for device type, device and protocol layer:

  Please choose the type of your primary network interface that you will need for 
   
  installing the Debian system (via NFS or HTTP). Only the listed devices are   
  supported.  
  Network device type:  
    1: ctc: Channel to Channel (CTC) or ESCON connection,      
    2: qeth: OSA-Express in QDIO mode / HiperSockets,      
    3: iucv: Inter-User Communication Vehicle - available for VM guests only,     
   
    4: virtio: KVM VirtIO,      
  Prompt: '?' for help> 2
  2  
    
  Please select the OSA-Express QDIO / HiperSockets device.  
  Device:  
    1: 0.0.f5f0-0.0.f5f1-0.0.f5f2  [*],  
  Prompt: '?' for help, default=1> 1
  1  
    
  By default OSA-Express cards use layer3 mode. In that mode LLC headers are   
  removed from incoming IPv4 packets. Using the card in layer2 mode will make it
  keep the MAC addresses of IPv4 packets.  
  Use this device in layer2 mode?  
    1: Yes [*]  2: No  
  Prompt: '?' for help, default=1> 

  The last question experienced a change according to https://bugs.launchpad.net/ubuntu/+source/s390-netdevice/+bug/1526801
  Layer2 is the default, which is correct, since the qeth driver uses layer2 as default as well.

  However, the introductional text says: "By default OSA-Express cards
  use layer3 mode."

  And this is wrong and needs to be fixed. Correct wording is:

  "By default OSA-Express cards use layer2 mode. In layer3 mode LLC headers are   
  removed from incoming IPv4 packets. Using the card in layer2 mode will make it   
  keep the MAC addresses of IPv4 packets."

  == Comment: #2 - Thorsten Diehl <thorsten.diehl at de.ibm.com> - 2016-02-03 12:08:52 ==
  Although LP 1526801 deals with this subject, it is different.
  LP 1526801 is implemented and closed. Now the documentational part in the installer needs to follow that. Thus I recommend to treat this as a separate bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1541544/+subscriptions