RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1561339 - No Broadcast address shown inside the containers
Summary: No Broadcast address shown inside the containers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.3
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Matthew Heon
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2018-03-28 07:08 UTC by Suhaas Bhat
Modified: 2020-10-26 08:27 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-03 20:32:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Suhaas Bhat 2018-03-28 07:08:45 UTC 
Description of problem:
There is no broadcast address shown for interfaces inside the containers

Version-Release number of selected component (if applicable):
RHEL 7.4
docker-1.13.1-53.git774336d.el7.x86_64

How reproducible:
Fully reproducible

With docker-ce package, broadcast is set even with the default network

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.xx.xx.x  netmask 255.255.255.0  broadcast 172.xx.xx.255
        ether 02:42:ac:1c:3c:02  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



with docker-1.13.1

eth0      Link encap:Ethernet  HWaddr 02:42:AC:11:00:03  
          inet addr:172.xx.x.x  Bcast:0.0.0.0  Mask:255.255.0.0
          inet6 addr: fe80::42:acff:fe11:3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:90 (90.0 B)  TX bytes:90 (90.0 B)

Actual results: Shows no broadcast address


Expected results: Should show as per the docker-ce package
Comment 4 Daniel Walsh 2019-08-13 19:10:47 UTC 
Is this caused by us or cni?
Comment 5 Daniel Walsh 2020-06-03 14:23:33 UTC 
Matt and
Comment 6 Matthew Heon 2020-06-03 14:30:25 UTC 
@Dan What were you trying to say? Looks like it was cut off.
Comment 8 Daniel Walsh 2020-06-03 20:31:40 UTC 
I read this as they wanted the information in podman inspect.
Comment 9 Matthew Heon 2020-06-03 20:56:43 UTC 
I don't read it that way? I don't see any mention of inspect in the BZ. This looks like the broadcast not being set in interfaces made by CNI, but this very much looks fixed.
Comment 10 mcambria@redhat.com 2020-06-03 22:44:20 UTC 
Agreed.  CNI also doesn't do anything but tell kernel to e.g. "ip addr add 10.89.0.2/16 dev eth0" inside the container.  If that had a problem it wouldn't have slipped under the radar.

I don't know what the real issue was.
Note You need to log in before you can comment on or make changes to this bug.