The printer uses its fe80:: address to contact the DHCPv6 server which
is handing out 2001:470:?:?::/64 addresses.
The DROP in the mangle table worked.
I still would like to know why fe80:: traffic is neither forwarded nor sent
to the INPUT chain.
Firmware update: I don't want to go this
On Wed, Apr 18, 2018 at 08:39:09AM -0400, Bill Shirley wrote:
> [0:root@c3po my.tables]$ rpm -q shorewall6
> shorewall6-5.0.14.1-1.fc24.noarch
>
> I have a HP printer that's mis-behaving. It gets an IPv4 address from DHCP
> and is happy.
> However for some reason after getting an IPv6 address,
I have a HP printer that's mis-behaving. It gets an IPv4 address from
DHCP and is happy.
A possible non-shorewall fix - is there updated firmware for the printer?
--
Check out the vibrant tech community on one of the
[0:root@c3po my.tables]$ rpm -q shorewall6
shorewall6-5.0.14.1-1.fc24.noarch
I have a HP printer that's mis-behaving. It gets an IPv4 address from DHCP and
is happy.
However for some reason after getting an IPv6 address, it doesn't like what it
got and
asks for an address again. This happens
