[Bug 1914740] Comment bridged from LTC Bugzilla

2021-03-17 Thread bugproxy
--- Comment From heinz-werner_se...@de.ibm.com 2021-03-17 08:12 EDT--- IBM bugzilla status-> closed, workaround available, upstream activitiy by Canonical. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-03-01 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-03-01 12:00 EDT--- Works like a charm, thank you xnox! I tested L2 and L3 HiperSockets during reboot. L2 got the IP@ via unicast reply L3 got its IP@ via broadcast reply. -- You received this bug notification because you are a member of Ubuntu Bug

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-03-01 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-03-01 02:53 EDT--- This is the setup I use as DHCP client: root@s83lp72:~# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-25 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-25 10:28 EDT--- (In reply to comment #25) > For netplan yaml of: > > network: > version: 2 > ethernets: > enc8f00: > dhcp4: yes > > It would be interesting to see if L3 dhcp starts to work if one does: > > $ sudo mkdir -p /etc/systemd/network/10-n

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-18 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-18 02:54 EDT--- (In reply to comment #18) > Thx Alexandra and Asha for digging deeply into that issue with the > hipersocket environment. > So the initial reason was to use L3 because of potentially connecting to > z/OS instances? > Yes, that is t

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-17 Thread bugproxy
--- Comment From stefan.ra...@de.ibm.com 2021-02-18 02:39 EDT--- Hi Frank, As for dhclient: Fedora33 ships isc-dhclient-4.4.2b1, and that has the option as part of the binary and described in the man page. -- You received this bug notification because you are a member of Ubuntu Bugs, whi

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-17 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-17 03:43 EDT--- For documentation: 'dhclient -B' is a way to turn on the required flag for Layer3 DHCP at the client side. My Ubuntu 20.04.2 contains only isc-dhclient-4.4.1 Seems that isc-dhclient-4.4.2 is required for this option. Using 'boot

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-16 Thread bugproxy
--- Comment From sankar...@in.ibm.com 2021-02-17 01:19 EDT--- Comment on attachment 148055 DHCP client debug information Yesterday SSC team had a debug session with Alexandra. I have attached the debug info of both server and client here. Each file contains the debug information from M96

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-16 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-16 11:49 EDT--- This morning we had a debug session with Asha and team. The first issues were configuration problems. For documentation purposes: - By default HiperSockets channels (CHPIDs) are isolated network segments, you cannot communicate b

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-12 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-12 07:04 EDT--- I have set up an DHCP server and DHCP client over HiperSockets, both on Ubuntu 20.04.1 and it works just fine. Please provide your config files for dhcp and netplan on server and client side. Is the dhcp server also running on Ub

[Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-11 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-11 08:44 EDT--- Thanks for the information Asha. Can you append any logs? dmesg, journalctl or any DHCP related logs? Do you have any information from the DHCP server? Logs? Network setup? Do you have tcpdump data? -- You received this bug notif