iptables blocking local traffic
up vote
1
down vote
favorite
My local machine IP: 192.168.0.35
What I did: Answer that i tried here!!
sudo iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
The error:
Now I can not access any more IP's from my local machine and I do not know why it happened.
Any IP that is: 123.123.123.123, etc ... The result of any attempt is the default page "Apache2 Debian Default Page". Now I can't access my router page to make changes in port forwarding. I don't know how undo this iptables
command.
What i want:
I was looking for a way to: Expose my Webserver, from the router on the Internet over port 80 and 443. Deploy httpd
(apache2) on port 1337 and continue dev on 8000,8080. From my router to my Raspbian, I'm trying to:
INTERNET IPx:80,443<===>80,443 router <===> IP-local-web-httpd (raspbian):
iptables port-forwarding ufw netfilter
New contributor
add a comment |
up vote
1
down vote
favorite
My local machine IP: 192.168.0.35
What I did: Answer that i tried here!!
sudo iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
The error:
Now I can not access any more IP's from my local machine and I do not know why it happened.
Any IP that is: 123.123.123.123, etc ... The result of any attempt is the default page "Apache2 Debian Default Page". Now I can't access my router page to make changes in port forwarding. I don't know how undo this iptables
command.
What i want:
I was looking for a way to: Expose my Webserver, from the router on the Internet over port 80 and 443. Deploy httpd
(apache2) on port 1337 and continue dev on 8000,8080. From my router to my Raspbian, I'm trying to:
INTERNET IPx:80,443<===>80,443 router <===> IP-local-web-httpd (raspbian):
iptables port-forwarding ufw netfilter
New contributor
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My local machine IP: 192.168.0.35
What I did: Answer that i tried here!!
sudo iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
The error:
Now I can not access any more IP's from my local machine and I do not know why it happened.
Any IP that is: 123.123.123.123, etc ... The result of any attempt is the default page "Apache2 Debian Default Page". Now I can't access my router page to make changes in port forwarding. I don't know how undo this iptables
command.
What i want:
I was looking for a way to: Expose my Webserver, from the router on the Internet over port 80 and 443. Deploy httpd
(apache2) on port 1337 and continue dev on 8000,8080. From my router to my Raspbian, I'm trying to:
INTERNET IPx:80,443<===>80,443 router <===> IP-local-web-httpd (raspbian):
iptables port-forwarding ufw netfilter
New contributor
My local machine IP: 192.168.0.35
What I did: Answer that i tried here!!
sudo iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
The error:
Now I can not access any more IP's from my local machine and I do not know why it happened.
Any IP that is: 123.123.123.123, etc ... The result of any attempt is the default page "Apache2 Debian Default Page". Now I can't access my router page to make changes in port forwarding. I don't know how undo this iptables
command.
What i want:
I was looking for a way to: Expose my Webserver, from the router on the Internet over port 80 and 443. Deploy httpd
(apache2) on port 1337 and continue dev on 8000,8080. From my router to my Raspbian, I'm trying to:
INTERNET IPx:80,443<===>80,443 router <===> IP-local-web-httpd (raspbian):
iptables port-forwarding ufw netfilter
iptables port-forwarding ufw netfilter
New contributor
New contributor
edited yesterday
SouravGhosh
371210
371210
New contributor
asked yesterday
Anderson Bosa
61
61
New contributor
New contributor
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Be careful using iptables command.
To have access again you have to delete the iptables command you performed.
So do with -D option and not -A to undo the command.
sudo iptables -t nat -D OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
add a comment |
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',
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
});
}
});
Anderson Bosa is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487949%2fiptables-blocking-local-traffic%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
up vote
0
down vote
Be careful using iptables command.
To have access again you have to delete the iptables command you performed.
So do with -D option and not -A to undo the command.
sudo iptables -t nat -D OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
add a comment |
up vote
0
down vote
Be careful using iptables command.
To have access again you have to delete the iptables command you performed.
So do with -D option and not -A to undo the command.
sudo iptables -t nat -D OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
add a comment |
up vote
0
down vote
up vote
0
down vote
Be careful using iptables command.
To have access again you have to delete the iptables command you performed.
So do with -D option and not -A to undo the command.
sudo iptables -t nat -D OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
Be careful using iptables command.
To have access again you have to delete the iptables command you performed.
So do with -D option and not -A to undo the command.
sudo iptables -t nat -D OUTPUT -p tcp --dport 80 -j DNAT --to-destination 192.168.0.35:80
answered yesterday
Sylla
603
603
add a comment |
add a comment |
Anderson Bosa is a new contributor. Be nice, and check out our Code of Conduct.
Anderson Bosa is a new contributor. Be nice, and check out our Code of Conduct.
Anderson Bosa is a new contributor. Be nice, and check out our Code of Conduct.
Anderson Bosa is a new contributor. Be nice, and check out our Code of Conduct.
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487949%2fiptables-blocking-local-traffic%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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