Bug 22768

Summary:	USB network cards don't get firewall rules when "hotplugged"
Product:	Mageia	Reporter:	Asimov Solensan <tl16887>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	basesystem, marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://forums.mageia.org/en/viewtopic.php?f=25&t=12297&p=72171#p72171
Whiteboard:
Source RPM:	shorewall-5.0.15.6-1.mga6	CVE:
Status comment:

Description Asimov Solensan 2018-03-14 10:10:16 CET

Description of problem:
When you connect a USB network card (wireless or cable) it won't get firewall rules.

It can get an address via DHCP but no traffic is allowed on that interface. So, no network at all.

Version-Release number of selected component (if applicable):
shorewall-5.0.15.6-1.mga6

The only solution is to plug in the device before turning on the computer. Rules created on boot are permanent and from now on the card will work when connected after reboot.

Note that if a different USB port is used the name of this card will change and the problem will just appear again.

How reproducible:
Get any kind of USB network card and just connect once the OS is running.

Check with #iptables -L that there are no rules for this network card.
Reboot the computer and check again.

Comment 1 Marja Van Waes 2018-03-14 10:29:40 CET

Assigning to all packagers collectively, since there is no registered maintainer for shorewall.

CC'ing basesystem maintainers, in case I should have assigned to them.

Assignee: bugsquad => pkg-bugs
CC: (none) => basesystem, marja11

Marja Van Waes 2018-03-14 10:30:47 CET

Summary: USB network cards don't get firewall rules when "hotpulgged" => USB network cards don't get firewall rules when "hotplugged"

Comment 2 Aurelien Oudelet 2020-08-16 16:31:31 CEST

Is this still valid in Mageia 7?

CC: (none) => ouaurelien

Comment 3 Aurelien Oudelet 2020-08-26 10:50:47 CEST

Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED