On 8/21/20 8:31 PM, James Knott wrote:
On 8/21/20 9:25 PM, David C. Rankin wrote:
Whatever you do, if you can, put a routing device between you and your ISP that will maintain the IP from your ISP and serve as a gateway for your home network -- solves many, many problems...
But he might no longer have a public address on that box. BTW, I used to use Suse for my firewall¹. What should I have put in front of it, when it was already my firewall/router?
1. I changed to pfSense, as Suse couldn't handle DHCPv6-PD.
No, no, There are many ways to do it and all are fine. What I understood was the problem was the loss of IP and replacement of public IP on reboot for kernel update. Whether you use a suse box as a firewall/router or a piece of hardware (both have pluses and minuses), if the problem was the IP handed out by the ISP on reboot -- then putting something between the network and ISP that doesn't have as frequent kernel updates will help (of course you have to question the security of the kernel it is running then....) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org