Using firewalld on a gateway certain websites are not accessible over HTTPS












0















I'm building a firewall / gateway on a raspberry PI (Debian 9)



I'm using firewalld to create firewall rules.



So far, most sites and services are working fine. However there are a few sites that are not accessible, one example is Netflix. However, Facebook and Google work perfectly over HTTPS.



So I have 3 interfaces configured, lan0, ppp0, and vpn0




lan0 = Local lan interface 192.168.1.2/24
ppp0 = PPPoE connection to my internet provider
vpn0 = Openconnect connection to a work VPN



Starting off with an unconfigured firewall, these are the only commands I used to set things up:




firewall-cmd --zone=external --change-interface=ppp0
firewall-cmd --zone=external --change-interface=vpn0
firewall-cmd --zone=trusted --change-interface=lan0
firewall-cmd --zone=public --add-service=http



I then browse the internet from a local client (192.168.1.5) and most sites are working. But I'm having a problem with Netflix and Skype (so far).



Here is what happens when I used curl from the same client, it just hangs forever.




curl -v https://www.netflix.com
* Rebuilt URL to: https://www.netflix.com/
* Hostname was NOT found in DNS cache
* Trying 52.19.56.133...
* Connected to www.netflix.com (52.19.56.133) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* SSLv3, TLS unknown, Certificate Status (22):
* SSLv3, TLS handshake, Client hello (1):



The same command from the gateway works (RPI) just fine.



Looks like the client is stuck waiting for a server response? Did I miss something?










share|improve this question























  • Does the client have openssl installed and a default set of certs created?

    – Michael Prokopec
    Feb 5 at 13:33
















0















I'm building a firewall / gateway on a raspberry PI (Debian 9)



I'm using firewalld to create firewall rules.



So far, most sites and services are working fine. However there are a few sites that are not accessible, one example is Netflix. However, Facebook and Google work perfectly over HTTPS.



So I have 3 interfaces configured, lan0, ppp0, and vpn0




lan0 = Local lan interface 192.168.1.2/24
ppp0 = PPPoE connection to my internet provider
vpn0 = Openconnect connection to a work VPN



Starting off with an unconfigured firewall, these are the only commands I used to set things up:




firewall-cmd --zone=external --change-interface=ppp0
firewall-cmd --zone=external --change-interface=vpn0
firewall-cmd --zone=trusted --change-interface=lan0
firewall-cmd --zone=public --add-service=http



I then browse the internet from a local client (192.168.1.5) and most sites are working. But I'm having a problem with Netflix and Skype (so far).



Here is what happens when I used curl from the same client, it just hangs forever.




curl -v https://www.netflix.com
* Rebuilt URL to: https://www.netflix.com/
* Hostname was NOT found in DNS cache
* Trying 52.19.56.133...
* Connected to www.netflix.com (52.19.56.133) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* SSLv3, TLS unknown, Certificate Status (22):
* SSLv3, TLS handshake, Client hello (1):



The same command from the gateway works (RPI) just fine.



Looks like the client is stuck waiting for a server response? Did I miss something?










share|improve this question























  • Does the client have openssl installed and a default set of certs created?

    – Michael Prokopec
    Feb 5 at 13:33














0












0








0








I'm building a firewall / gateway on a raspberry PI (Debian 9)



I'm using firewalld to create firewall rules.



So far, most sites and services are working fine. However there are a few sites that are not accessible, one example is Netflix. However, Facebook and Google work perfectly over HTTPS.



So I have 3 interfaces configured, lan0, ppp0, and vpn0




lan0 = Local lan interface 192.168.1.2/24
ppp0 = PPPoE connection to my internet provider
vpn0 = Openconnect connection to a work VPN



Starting off with an unconfigured firewall, these are the only commands I used to set things up:




firewall-cmd --zone=external --change-interface=ppp0
firewall-cmd --zone=external --change-interface=vpn0
firewall-cmd --zone=trusted --change-interface=lan0
firewall-cmd --zone=public --add-service=http



I then browse the internet from a local client (192.168.1.5) and most sites are working. But I'm having a problem with Netflix and Skype (so far).



Here is what happens when I used curl from the same client, it just hangs forever.




curl -v https://www.netflix.com
* Rebuilt URL to: https://www.netflix.com/
* Hostname was NOT found in DNS cache
* Trying 52.19.56.133...
* Connected to www.netflix.com (52.19.56.133) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* SSLv3, TLS unknown, Certificate Status (22):
* SSLv3, TLS handshake, Client hello (1):



The same command from the gateway works (RPI) just fine.



Looks like the client is stuck waiting for a server response? Did I miss something?










share|improve this question














I'm building a firewall / gateway on a raspberry PI (Debian 9)



I'm using firewalld to create firewall rules.



So far, most sites and services are working fine. However there are a few sites that are not accessible, one example is Netflix. However, Facebook and Google work perfectly over HTTPS.



So I have 3 interfaces configured, lan0, ppp0, and vpn0




lan0 = Local lan interface 192.168.1.2/24
ppp0 = PPPoE connection to my internet provider
vpn0 = Openconnect connection to a work VPN



Starting off with an unconfigured firewall, these are the only commands I used to set things up:




firewall-cmd --zone=external --change-interface=ppp0
firewall-cmd --zone=external --change-interface=vpn0
firewall-cmd --zone=trusted --change-interface=lan0
firewall-cmd --zone=public --add-service=http



I then browse the internet from a local client (192.168.1.5) and most sites are working. But I'm having a problem with Netflix and Skype (so far).



Here is what happens when I used curl from the same client, it just hangs forever.




curl -v https://www.netflix.com
* Rebuilt URL to: https://www.netflix.com/
* Hostname was NOT found in DNS cache
* Trying 52.19.56.133...
* Connected to www.netflix.com (52.19.56.133) port 443 (#0)
* successfully set certificate verify locations:
* CAfile: none
CApath: /etc/ssl/certs/
* SSLv3, TLS unknown, Certificate Status (22):
* SSLv3, TLS handshake, Client hello (1):



The same command from the gateway works (RPI) just fine.



Looks like the client is stuck waiting for a server response? Did I miss something?







iptables firewalld






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 5 at 12:57









Aditya KAditya K

789821




789821













  • Does the client have openssl installed and a default set of certs created?

    – Michael Prokopec
    Feb 5 at 13:33



















  • Does the client have openssl installed and a default set of certs created?

    – Michael Prokopec
    Feb 5 at 13:33

















Does the client have openssl installed and a default set of certs created?

– Michael Prokopec
Feb 5 at 13:33





Does the client have openssl installed and a default set of certs created?

– Michael Prokopec
Feb 5 at 13:33










1 Answer
1






active

oldest

votes


















0














After much Googling, it turns out this has nothing to do with my firewall at all.



It was all related to what MTU setting I had on my PPPoE link.



The solution was to set it to 1452.



A full explanation can be seen here






share|improve this answer
























  • Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

    – telcoM
    Feb 6 at 10:31











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498791%2fusing-firewalld-on-a-gateway-certain-websites-are-not-accessible-over-https%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














After much Googling, it turns out this has nothing to do with my firewall at all.



It was all related to what MTU setting I had on my PPPoE link.



The solution was to set it to 1452.



A full explanation can be seen here






share|improve this answer
























  • Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

    – telcoM
    Feb 6 at 10:31
















0














After much Googling, it turns out this has nothing to do with my firewall at all.



It was all related to what MTU setting I had on my PPPoE link.



The solution was to set it to 1452.



A full explanation can be seen here






share|improve this answer
























  • Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

    – telcoM
    Feb 6 at 10:31














0












0








0







After much Googling, it turns out this has nothing to do with my firewall at all.



It was all related to what MTU setting I had on my PPPoE link.



The solution was to set it to 1452.



A full explanation can be seen here






share|improve this answer













After much Googling, it turns out this has nothing to do with my firewall at all.



It was all related to what MTU setting I had on my PPPoE link.



The solution was to set it to 1452.



A full explanation can be seen here







share|improve this answer












share|improve this answer



share|improve this answer










answered Feb 6 at 7:13









Aditya KAditya K

789821




789821













  • Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

    – telcoM
    Feb 6 at 10:31



















  • Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

    – telcoM
    Feb 6 at 10:31

















Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

– telcoM
Feb 6 at 10:31





Please check that your firewall rules will allow ICMP messages of type fragmentation-needed through. It allows a technique called Path MTU discovery to automatically determine the optimal MTU value for each connection, and is supported by essentially all operating systems since Windows 95. If you're blocking it, you might also have problems accessing some cloud services or systems behind an IPv6 gateway, as those may restrict the MTU value still further.

– telcoM
Feb 6 at 10:31


















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498791%2fusing-firewalld-on-a-gateway-certain-websites-are-not-accessible-over-https%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

Is this a new Fibonacci Identity?

19世紀