3 -> 1 routing issue
I've had this working before, but I can't get it right on a new machine. I have the following setup on a ubuntu install as a router.
192.168.2.0/24 p34p1 wifi1 -------------|
192.168.1.0/24 p33p1 wired -------------|------Internet p32p1
192.168.3.0/24 p34p1 wifi2 -------------| 192.168.0.0/24
This might look overly complicated but it keeps the kids gaming traffic off my regular network, which can't use it on a console anyway. At present all three segments can talk to the internet, but cannot talk to each other in different segments as required.
routing
Kernel IP Routing table
Destination Gateway Genmask Iface
0.0.0.0 192.168.0.1 0.0.0.0 p32p1
192.168.0.0 * 255.255.255.0 p32p1
192.168.0.1 * 255.255.255.255 p32p1
192.168.1.0 * 255.255.255.0 p33p1
192.168.2.0 * 255.255.255.0 p34p1
192.168.3.0 * 255.255.255.0 p35p1
iptables -t nat -v -x -n -L
Chain PREROUTING (policy ACCEPT 998 packets, 64328 bytes)
pkts bytes target prot opt in out source destination
Chain INPUT (policy ACCEPT 115 packets, 9157 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 30271 packets, 1701429 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 172 packets, 17314 bytes)
pkts bytes target prot opt in out source destination
30982 1739286 MASQUERADE all -- * p32p1 0.0.0.0/0 0.0.0.0/0
102 8264 all -- * p33p1 0.0.0.0/0 0.0.0.0/0
61 7327 all -- * p34p1 0.0.0.0/0 0.0.0.0/0
7 1603 all -- * p35p1 0.0.0.0/0 0.0.0.0/0
my iptables rules are turning into mush.
Any Assistance appreciated, thank-you
networking iptables routing
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
add a comment |
I've had this working before, but I can't get it right on a new machine. I have the following setup on a ubuntu install as a router.
192.168.2.0/24 p34p1 wifi1 -------------|
192.168.1.0/24 p33p1 wired -------------|------Internet p32p1
192.168.3.0/24 p34p1 wifi2 -------------| 192.168.0.0/24
This might look overly complicated but it keeps the kids gaming traffic off my regular network, which can't use it on a console anyway. At present all three segments can talk to the internet, but cannot talk to each other in different segments as required.
routing
Kernel IP Routing table
Destination Gateway Genmask Iface
0.0.0.0 192.168.0.1 0.0.0.0 p32p1
192.168.0.0 * 255.255.255.0 p32p1
192.168.0.1 * 255.255.255.255 p32p1
192.168.1.0 * 255.255.255.0 p33p1
192.168.2.0 * 255.255.255.0 p34p1
192.168.3.0 * 255.255.255.0 p35p1
iptables -t nat -v -x -n -L
Chain PREROUTING (policy ACCEPT 998 packets, 64328 bytes)
pkts bytes target prot opt in out source destination
Chain INPUT (policy ACCEPT 115 packets, 9157 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 30271 packets, 1701429 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 172 packets, 17314 bytes)
pkts bytes target prot opt in out source destination
30982 1739286 MASQUERADE all -- * p32p1 0.0.0.0/0 0.0.0.0/0
102 8264 all -- * p33p1 0.0.0.0/0 0.0.0.0/0
61 7327 all -- * p34p1 0.0.0.0/0 0.0.0.0/0
7 1603 all -- * p35p1 0.0.0.0/0 0.0.0.0/0
my iptables rules are turning into mush.
Any Assistance appreciated, thank-you
networking iptables routing
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
iptables -Ldoesn't give us your NAT rules, which we need. Please dosudo iptables -t nat -v -x -n -Land edit your question adding the output. Since your default policy for your FORWARD chain is accept, you don't actually need any of those rules.
– Doug Smythies
Feb 4 at 23:10
iptables -t nat -v -x -n -L added
– A.Adverse
Feb 4 at 23:50
I think I found a partial, the networks there, but no gateways. Will look into that next
– A.Adverse
Feb 5 at 2:46
add a comment |
I've had this working before, but I can't get it right on a new machine. I have the following setup on a ubuntu install as a router.
192.168.2.0/24 p34p1 wifi1 -------------|
192.168.1.0/24 p33p1 wired -------------|------Internet p32p1
192.168.3.0/24 p34p1 wifi2 -------------| 192.168.0.0/24
This might look overly complicated but it keeps the kids gaming traffic off my regular network, which can't use it on a console anyway. At present all three segments can talk to the internet, but cannot talk to each other in different segments as required.
routing
Kernel IP Routing table
Destination Gateway Genmask Iface
0.0.0.0 192.168.0.1 0.0.0.0 p32p1
192.168.0.0 * 255.255.255.0 p32p1
192.168.0.1 * 255.255.255.255 p32p1
192.168.1.0 * 255.255.255.0 p33p1
192.168.2.0 * 255.255.255.0 p34p1
192.168.3.0 * 255.255.255.0 p35p1
iptables -t nat -v -x -n -L
Chain PREROUTING (policy ACCEPT 998 packets, 64328 bytes)
pkts bytes target prot opt in out source destination
Chain INPUT (policy ACCEPT 115 packets, 9157 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 30271 packets, 1701429 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 172 packets, 17314 bytes)
pkts bytes target prot opt in out source destination
30982 1739286 MASQUERADE all -- * p32p1 0.0.0.0/0 0.0.0.0/0
102 8264 all -- * p33p1 0.0.0.0/0 0.0.0.0/0
61 7327 all -- * p34p1 0.0.0.0/0 0.0.0.0/0
7 1603 all -- * p35p1 0.0.0.0/0 0.0.0.0/0
my iptables rules are turning into mush.
Any Assistance appreciated, thank-you
networking iptables routing
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
I've had this working before, but I can't get it right on a new machine. I have the following setup on a ubuntu install as a router.
192.168.2.0/24 p34p1 wifi1 -------------|
192.168.1.0/24 p33p1 wired -------------|------Internet p32p1
192.168.3.0/24 p34p1 wifi2 -------------| 192.168.0.0/24
This might look overly complicated but it keeps the kids gaming traffic off my regular network, which can't use it on a console anyway. At present all three segments can talk to the internet, but cannot talk to each other in different segments as required.
routing
Kernel IP Routing table
Destination Gateway Genmask Iface
0.0.0.0 192.168.0.1 0.0.0.0 p32p1
192.168.0.0 * 255.255.255.0 p32p1
192.168.0.1 * 255.255.255.255 p32p1
192.168.1.0 * 255.255.255.0 p33p1
192.168.2.0 * 255.255.255.0 p34p1
192.168.3.0 * 255.255.255.0 p35p1
iptables -t nat -v -x -n -L
Chain PREROUTING (policy ACCEPT 998 packets, 64328 bytes)
pkts bytes target prot opt in out source destination
Chain INPUT (policy ACCEPT 115 packets, 9157 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 30271 packets, 1701429 bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 172 packets, 17314 bytes)
pkts bytes target prot opt in out source destination
30982 1739286 MASQUERADE all -- * p32p1 0.0.0.0/0 0.0.0.0/0
102 8264 all -- * p33p1 0.0.0.0/0 0.0.0.0/0
61 7327 all -- * p34p1 0.0.0.0/0 0.0.0.0/0
7 1603 all -- * p35p1 0.0.0.0/0 0.0.0.0/0
my iptables rules are turning into mush.
Any Assistance appreciated, thank-you
networking iptables routing
networking iptables routing
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
edited Feb 4 at 23:48
A.Adverse
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
asked Feb 4 at 22:38
A.AdverseA.Adverse
438
438
iptables -Ldoesn't give us your NAT rules, which we need. Please dosudo iptables -t nat -v -x -n -Land edit your question adding the output. Since your default policy for your FORWARD chain is accept, you don't actually need any of those rules.
– Doug Smythies
Feb 4 at 23:10
iptables -t nat -v -x -n -L added
– A.Adverse
Feb 4 at 23:50
I think I found a partial, the networks there, but no gateways. Will look into that next
– A.Adverse
Feb 5 at 2:46
add a comment |
iptables -Ldoesn't give us your NAT rules, which we need. Please dosudo iptables -t nat -v -x -n -Land edit your question adding the output. Since your default policy for your FORWARD chain is accept, you don't actually need any of those rules.
– Doug Smythies
Feb 4 at 23:10
iptables -t nat -v -x -n -L added
– A.Adverse
Feb 4 at 23:50
I think I found a partial, the networks there, but no gateways. Will look into that next
– A.Adverse
Feb 5 at 2:46
iptables -L doesn't give us your NAT rules, which we need. Please do sudo iptables -t nat -v -x -n -L and edit your question adding the output. Since your default policy for your FORWARD chain is accept, you don't actually need any of those rules.– Doug Smythies
Feb 4 at 23:10
iptables -L doesn't give us your NAT rules, which we need. Please do sudo iptables -t nat -v -x -n -L and edit your question adding the output. Since your default policy for your FORWARD chain is accept, you don't actually need any of those rules.– Doug Smythies
Feb 4 at 23:10
iptables -t nat -v -x -n -L added
– A.Adverse
Feb 4 at 23:50
iptables -t nat -v -x -n -L added
– A.Adverse
Feb 4 at 23:50
I think I found a partial, the networks there, but no gateways. Will look into that next
– A.Adverse
Feb 5 at 2:46
I think I found a partial, the networks there, but no gateways. Will look into that next
– A.Adverse
Feb 5 at 2:46
add a comment |
1 Answer
1
active
oldest
votes
This missing gateways were the problem to the solution ;) Works much more betterer that way.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
repeat for each nic
Without the gateway even if it knows the network is there it won't work
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1115662%2f3-1-routing-issue%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
This missing gateways were the problem to the solution ;) Works much more betterer that way.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
repeat for each nic
Without the gateway even if it knows the network is there it won't work
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
add a comment |
This missing gateways were the problem to the solution ;) Works much more betterer that way.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
repeat for each nic
Without the gateway even if it knows the network is there it won't work
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
add a comment |
This missing gateways were the problem to the solution ;) Works much more betterer that way.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
repeat for each nic
Without the gateway even if it knows the network is there it won't work
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
This missing gateways were the problem to the solution ;) Works much more betterer that way.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
repeat for each nic
Without the gateway even if it knows the network is there it won't work
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
answered Feb 5 at 21:29
A.AdverseA.Adverse
438
438
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1115662%2f3-1-routing-issue%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
iptables -Ldoesn't give us your NAT rules, which we need. Please dosudo iptables -t nat -v -x -n -Land edit your question adding the output. Since your default policy for your FORWARD chain is accept, you don't actually need any of those rules.– Doug Smythies
Feb 4 at 23:10
iptables -t nat -v -x -n -L added
– A.Adverse
Feb 4 at 23:50
I think I found a partial, the networks there, but no gateways. Will look into that next
– A.Adverse
Feb 5 at 2:46