-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 1/9/20 12:13 PM, José Sarabia wrote:
> My question is, why did I do wrong? I literally did a copy-paste on
> the information I had from an older router using an older shorewall
> version.
>
>
>
> On Thu, Jan 9, 2020 at 12:11 PM José Sarabia
> ma
Thank you, I was able to fix this issue by rebooting the router, then I had
to set a static IP on my PC on the segment than the router and finally I
was able to login to the router.
On Thu, Jan 9, 2020 at 12:45 PM Justin Pryzby wrote:
> On Thu, Jan 9, 2020 at 12:10 PM José Sarabia
> wrote:
>
My question is, why did I do wrong? I literally did a copy-paste on the
information I had from an older router using an older shorewall version.
On Thu, Jan 9, 2020 at 12:11 PM José Sarabia
wrote:
> Also, it won't give me any IPv4 address when I wire the router to my
> computer
>
>
>
> On Thu,
On Thu, Jan 9, 2020 at 12:10 PM José Sarabia wrote:
> Hi, I installed shorewall 5.2.3.4 to a router using openwrt 18.06 firmware.
>
> After I configured the vi zones, rules, policy, etc, I started the
> shorewall by using the shorewall start command, but after that I wasn't
> able to logging to th
Hi, I installed shorewall 5.2.3.4 to a router using openwrt 18.06 firmware.
After I configured the vi zones, rules, policy, etc, I started the
shorewall by using the shorewall start command, but after that I wasn't
able to logging to the router through SSH, and also, I wasn't able to
connect to th
Also, it won't give me any IPv4 address when I wire the router to my
computer
On Thu, Jan 9, 2020 at 12:10 PM José Sarabia
wrote:
> Hi, I installed shorewall 5.2.3.4 to a router using openwrt 18.06 firmware.
>
> After I configured the vi zones, rules, policy, etc, I started the
> shorewall by
