Back to bug 1297445
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Tomáš Hozza | 2016-01-12 09:54:07 UTC | CC | thozza | |
| Petr Janda | 2016-01-12 14:23:41 UTC | CC | pjanda | |
| Jiri Popelka | 2016-01-13 15:13:31 UTC | Status | ASSIGNED | MODIFIED |
| CC | praiskup | |||
| Jiri Popelka | 2016-01-13 15:14:34 UTC | Doc Text | Previously, when using the "dhclient" DHCP protocol client on a host with two network interfaces connected to the same subnet, "DHCPREQUEST" packets were only being sent to one of the interfaces. Consequently, the IP address lease of the other interface was not being renewed. With this update, "dhclient" sends "DHCPREQUEST" and "DHCPRELEASE" packets to both interfaces, even if they are on the same subnetwork. |
|
| errata-xmlrpc | 2016-01-13 15:16:42 UTC | Status | MODIFIED | ON_QA |
| Jiri Kortus | 2016-02-23 14:01:55 UTC | CC | jikortus | |
| Jiri Kortus | 2016-03-01 14:23:46 UTC | Status | ON_QA | ASSIGNED |
| noah davids | 2016-03-01 20:56:44 UTC | CC | ndavids | |
| Tomas Mlcoch | 2016-06-22 09:11:20 UTC | Assignee | jpopelka | psimerda |
| Chris Williams | 2016-07-14 15:26:32 UTC | Blocks | 1269194 | |
| Pavel Šimerda (pavlix) | 2016-07-21 12:36:31 UTC | Blocks | 1356054 | |
| Tomáš Hozza | 2016-08-17 15:57:05 UTC | Blocks | 1359261 | |
| Tomáš Hozza | 2016-09-06 18:18:57 UTC | Doc Type | Bug Fix | If docs needed, set a value |
| Pavel Šimerda (pavlix) | 2016-10-05 09:27:31 UTC | Flags | needinfo?(ndavids) | |
| Pavel Šimerda (pavlix) | 2016-10-05 09:27:48 UTC | CC | jpopelka | |
| Flags | needinfo?(jpopelka) | |||
| Pavel Šimerda (pavlix) | 2016-10-13 06:56:47 UTC | Flags | needinfo?(pjanda) | |
| Petr Janda | 2016-10-18 13:04:26 UTC | Flags | needinfo?(ndavids) needinfo?(jpopelka) needinfo?(pjanda) | |
| Petr Janda | 2016-10-18 13:32:53 UTC | Flags | needinfo?(jpopelka) | |
| Jiri Popelka | 2016-10-18 13:56:21 UTC | Flags | needinfo?(jpopelka) | |
| Tomáš Hozza | 2016-11-08 13:36:02 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Pavel Šimerda (pavlix) | 2016-11-08 13:42:44 UTC | Doc Text | Previously, when using the "dhclient" DHCP protocol client on a host with two network interfaces connected to the same subnet, "DHCPREQUEST" packets were only being sent to one of the interfaces. Consequently, the IP address lease of the other interface was not being renewed. With this update, "dhclient" sends "DHCPREQUEST" and "DHCPRELEASE" packets to both interfaces, even if they are on the same subnetwork. | Cause: DHCP client doesn't support multiple interfaces on the same subnet and doesn't ensure that unicast requests go through the right interface. Consequence: DHCP client fails to renew a lease and network configuration stops working. Workaround (if any): Result: DHCP client cannot be used in configuration with two interfaces connected to the same subnet. |
| Tomáš Hozza | 2016-11-08 15:08:11 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | CANTFIX | ||
| Last Closed | 2016-11-08 10:08:11 UTC | |||
| Lenka Špačková | 2016-12-12 13:32:38 UTC | Docs Contact | mjahoda | |
| Mirek Jahoda | 2017-01-04 13:58:07 UTC | Doc Text | Cause: DHCP client doesn't support multiple interfaces on the same subnet and doesn't ensure that unicast requests go through the right interface. Consequence: DHCP client fails to renew a lease and network configuration stops working. Workaround (if any): Result: DHCP client cannot be used in configuration with two interfaces connected to the same subnet. | *DHCP* client sends unicast requests through the wrong interface *DHCP* client does not support multiple interfaces on the same subnet and it is not able to ensure that unicast requests go through the right interface. Consequently, *DHCP* client fails to renew a lease, and network configuration stops working. There is no known workaround at this point, *DHCP* client cannot be used in configuration with two interfaces connected to the same subnet. |
| Mirek Jahoda | 2017-01-04 15:12:06 UTC | Doc Text | *DHCP* client sends unicast requests through the wrong interface *DHCP* client does not support multiple interfaces on the same subnet and it is not able to ensure that unicast requests go through the right interface. Consequently, *DHCP* client fails to renew a lease, and network configuration stops working. There is no known workaround at this point, *DHCP* client cannot be used in configuration with two interfaces connected to the same subnet. | *DHCP* client sends unicast requests through the incorrect interface *DHCP* client does not support multiple interfaces on the same subnet and it is not able to ensure that unicast requests go through the right interface. Consequently, *DHCP* client fails to renew a lease, and network configuration stops working. There is no known workaround at this point. *DHCP* client cannot be used in configuration with two interfaces connected to the same subnet. |
Back to bug 1297445