Hi Simon,
Thanks for taking the time to write, sorry timezone and business have delayed
my acknowledgement...
No problem blocking PPPoE from the loc zone, I'm just not sure the protocol
number(s) I would use to achieve that.
I don't know how the device is spoofing the packets, I presume it's not
I've been using shorewall for awhile with net0 on the WAN and net1 on
the LAN. I just switched to PPPoE so now I have ppp0 in addition to
net0 and net1. I've replaced net0 with ppp0 everywhere in my
shorewall config and added net0 as a second interface in the loc zone
along with net1. Everything
Brian Marshall wrote:
> No problem blocking PPPoE from the loc zone, I'm just not sure the protocol
> number(s) I would use to achieve that.
They aren't even IP packets, and as far as I can see should not be getting
forwarded at all. As below, they are ether type 0x8863 or 0x8864 vs 0x0800 for
Grant wrote:
> I've been using shorewall for awhile with net0 on the WAN and net1 on
> the LAN. I just switched to PPPoE so now I have ppp0 in addition to
> net0 and net1. I've replaced net0 with ppp0 everywhere in my
> shorewall config and added net0 as a second interface in the loc zone
> alo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/19/2016 07:50 PM, Steven Kiehl wrote:
>
> So I adding that address as a hard-coded gateway in the
> shorewall/providers configuration. I basically followed the
> multi-isp directions and skipped the multi part of it. Seems
> functional, f
