Linux Software Firewall Problem
by danmartinj from LinuxQuestions.org on (#5DG2C)
Hello Everyone,
I have been beating my head against a network problem for the past few days and am basically out of good ideas. Currently I have a Linux Kali 2019.2 image deployed in Azure (I did not deploy it as I have no access to the management environment). If I try to update the VM I get a:
Code:Failed to fetch InRelease 470 status code 470 [IP: X.X.X.X 80] InRelease is no longer signed)At first I thought it might be a proxy problem but within that environment I was told there are no proxy configurations. So, then I tried curl google.com:
Code:HTTP request from X.X.X.X:60632 to google.com:80. Action: Deny. No rule matched. Proceeding with default actionGoogling around it looks like there is an Azure Firewall in the way. I have tried a few work arounds such as setting the repos to use https instead of http but that brings up other problems and basically at this point I was hoping someone could provide me some good solid ideas while I try to wait for Azure support which may or may not come.
Thanks again,
Joe
I have been beating my head against a network problem for the past few days and am basically out of good ideas. Currently I have a Linux Kali 2019.2 image deployed in Azure (I did not deploy it as I have no access to the management environment). If I try to update the VM I get a:
Code:Failed to fetch InRelease 470 status code 470 [IP: X.X.X.X 80] InRelease is no longer signed)At first I thought it might be a proxy problem but within that environment I was told there are no proxy configurations. So, then I tried curl google.com:
Code:HTTP request from X.X.X.X:60632 to google.com:80. Action: Deny. No rule matched. Proceeding with default actionGoogling around it looks like there is an Azure Firewall in the way. I have tried a few work arounds such as setting the repos to use https instead of http but that brings up other problems and basically at this point I was hoping someone could provide me some good solid ideas while I try to wait for Azure support which may or may not come.
Thanks again,
Joe