Issues with second lan
I have the following setup
Superhub3 192.168.0.1
eth1 192.168.0.10
CISCO ASA 5505 internal 192.168.1.1
eth2 169.254.x.x
When directly plugging ASA into eth1, i can access 192.168.1.1
However, when the ASA is connected to eth2, it results in 169.254.x.x address.
Under Network Settings on Win10 eth2 is connected / Unidentified network.
I tried the manual settings shown below, but no change.
Q. How can i get the eth2 working simultaneously so i can access 192.168.1.1 from eth2, on the same machine as eth1 on 192.168.0.1?
Diagram Added
networking ethernet cisco-router
asked Dec 19 '18 at 22:40
DerpleDerple
1096
add a comment |
I have the following setup
Superhub3 192.168.0.1
eth1 192.168.0.10
CISCO ASA 5505 internal 192.168.1.1
eth2 169.254.x.x
When directly plugging ASA into eth1, i can access 192.168.1.1
However, when the ASA is connected to eth2, it results in 169.254.x.x address.
Under Network Settings on Win10 eth2 is connected / Unidentified network.
I tried the manual settings shown below, but no change.
Q. How can i get the eth2 working simultaneously so i can access 192.168.1.1 from eth2, on the same machine as eth1 on 192.168.0.1?
Diagram Added
networking ethernet cisco-router
asked Dec 19 '18 at 22:40
DerpleDerple
1096
You don't appear to be running DHCP on your ASA, from what I understand. Can you draw a diagram, or better document exactly what you're trying to do.
– djsmiley2k
Dec 19 '18 at 22:46
@djsmiley2k Hi, thanks for reply, diagram added.
– Derple
Dec 19 '18 at 23:16
add a comment |
I have the following setup
Superhub3 192.168.0.1
eth1 192.168.0.10
CISCO ASA 5505 internal 192.168.1.1
eth2 169.254.x.x
When directly plugging ASA into eth1, i can access 192.168.1.1
However, when the ASA is connected to eth2, it results in 169.254.x.x address.
Under Network Settings on Win10 eth2 is connected / Unidentified network.
I tried the manual settings shown below, but no change.
Q. How can i get the eth2 working simultaneously so i can access 192.168.1.1 from eth2, on the same machine as eth1 on 192.168.0.1?
Diagram Added
networking ethernet cisco-router
asked Dec 19 '18 at 22:40
DerpleDerple
1096
I have the following setup
Superhub3 192.168.0.1
eth1 192.168.0.10
CISCO ASA 5505 internal 192.168.1.1
eth2 169.254.x.x
When directly plugging ASA into eth1, i can access 192.168.1.1
However, when the ASA is connected to eth2, it results in 169.254.x.x address.
Under Network Settings on Win10 eth2 is connected / Unidentified network.
I tried the manual settings shown below, but no change.
Q. How can i get the eth2 working simultaneously so i can access 192.168.1.1 from eth2, on the same machine as eth1 on 192.168.0.1?
Diagram Added
networking ethernet cisco-router
networking ethernet cisco-router
asked Dec 19 '18 at 22:40
DerpleDerple
1096
asked Dec 19 '18 at 22:40
DerpleDerple
1096
edited Dec 19 '18 at 23:16
Derple
asked Dec 19 '18 at 22:40
DerpleDerple
1096
asked Dec 19 '18 at 22:40
DerpleDerple
1096
asked Dec 19 '18 at 22:40
DerpleDerple
1096
1096
You don't appear to be running DHCP on your ASA, from what I understand. Can you draw a diagram, or better document exactly what you're trying to do.
– djsmiley2k
Dec 19 '18 at 22:46
@djsmiley2k Hi, thanks for reply, diagram added.
– Derple
Dec 19 '18 at 23:16
add a comment |
You don't appear to be running DHCP on your ASA, from what I understand. Can you draw a diagram, or better document exactly what you're trying to do.
– djsmiley2k
Dec 19 '18 at 22:46
@djsmiley2k Hi, thanks for reply, diagram added.
– Derple
Dec 19 '18 at 23:16
You don't appear to be running DHCP on your ASA, from what I understand. Can you draw a diagram, or better document exactly what you're trying to do.
– djsmiley2k
Dec 19 '18 at 22:46
You don't appear to be running DHCP on your ASA, from what I understand. Can you draw a diagram, or better document exactly what you're trying to do.
– djsmiley2k
Dec 19 '18 at 22:46
@djsmiley2k Hi, thanks for reply, diagram added.
– Derple
Dec 19 '18 at 23:16
@djsmiley2k Hi, thanks for reply, diagram added.
– Derple
Dec 19 '18 at 23:16
add a comment |
1 Answer
1
active
oldest
votes
The problem is when the access was working to the ASA, windows added a default route for all traffic to go via it, rather than via your original default route to the superhub.
Connect up everything, then print the routing table:
route print in a command prompt.
You'll likely see 2 default routes.
Delete the default routes:
route delete default x2
Then add the correct default route manually:
route add default gw 192.168.0.1
Now everything 'should' just work.
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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%2fsuperuser.com%2fquestions%2f1386078%2fissues-with-second-lan%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
The problem is when the access was working to the ASA, windows added a default route for all traffic to go via it, rather than via your original default route to the superhub.
Connect up everything, then print the routing table:
route print in a command prompt.
You'll likely see 2 default routes.
Delete the default routes:
route delete default x2
Then add the correct default route manually:
route add default gw 192.168.0.1
Now everything 'should' just work.
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
add a comment |
The problem is when the access was working to the ASA, windows added a default route for all traffic to go via it, rather than via your original default route to the superhub.
Connect up everything, then print the routing table:
route print in a command prompt.
You'll likely see 2 default routes.
Delete the default routes:
route delete default x2
Then add the correct default route manually:
route add default gw 192.168.0.1
Now everything 'should' just work.
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
add a comment |
The problem is when the access was working to the ASA, windows added a default route for all traffic to go via it, rather than via your original default route to the superhub.
Connect up everything, then print the routing table:
route print in a command prompt.
You'll likely see 2 default routes.
Delete the default routes:
route delete default x2
Then add the correct default route manually:
route add default gw 192.168.0.1
Now everything 'should' just work.
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
The problem is when the access was working to the ASA, windows added a default route for all traffic to go via it, rather than via your original default route to the superhub.
Connect up everything, then print the routing table:
route print in a command prompt.
You'll likely see 2 default routes.
Delete the default routes:
route delete default x2
Then add the correct default route manually:
route add default gw 192.168.0.1
Now everything 'should' just work.
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
answered Dec 31 '18 at 16:02
djsmiley2kdjsmiley2k
4,96312335
4,96312335
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
add a comment |
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
i shall try this and respond with outcome, regards.
– Derple
Jan 10 at 19:07
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1386078%2fissues-with-second-lan%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
You don't appear to be running DHCP on your ASA, from what I understand. Can you draw a diagram, or better document exactly what you're trying to do.
– djsmiley2k
Dec 19 '18 at 22:46
@djsmiley2k Hi, thanks for reply, diagram added.
– Derple
Dec 19 '18 at 23:16