iscsiadm: cannot make connection to : No route to host
up vote
1
down vote
favorite
when I try iscsiadm discovery:
iscsiadm -m discovery -t sendtargets -p <IP>
I get this error:
iscsiadm: cannot make connection to <IP>: No route to host
however, I can ping the IP fine.
I have added following rule in route:
ip route add <IP>/32 via 10.10.10.1 dev eth1
and i can confirm that ping pings through eth1 interface:
ping -I eth1 <IP>
but for some reason, it looks as if iscsiadm is not using my route settings ?
and traceroute works as well:
# traceroute <IP>
traceroute to <IP>, 30 hops max, 60 byte packets
1 10.10.10.1 0.555 ms 0.776 ms 0.973 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 myhost (<IP>) 0.714 ms !X 0.657 ms !X 0.674 ms !X
networking ping route iscsi
asked Nov 29 at 6:48
Martin Vegter
16634119234
add a comment |
up vote
1
down vote
favorite
when I try iscsiadm discovery:
iscsiadm -m discovery -t sendtargets -p <IP>
I get this error:
iscsiadm: cannot make connection to <IP>: No route to host
however, I can ping the IP fine.
I have added following rule in route:
ip route add <IP>/32 via 10.10.10.1 dev eth1
and i can confirm that ping pings through eth1 interface:
ping -I eth1 <IP>
but for some reason, it looks as if iscsiadm is not using my route settings ?
and traceroute works as well:
# traceroute <IP>
traceroute to <IP>, 30 hops max, 60 byte packets
1 10.10.10.1 0.555 ms 0.776 ms 0.973 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 myhost (<IP>) 0.714 ms !X 0.657 ms !X 0.674 ms !X
networking ping route iscsi
asked Nov 29 at 6:48
Martin Vegter
16634119234
What doestraceroute <IP>say?
– Mark Plotnick
Nov 29 at 7:20
@Mark Plotnick - traceroute works. Please see my edit.
– Martin Vegter
Nov 29 at 7:32
OK, routing was the first thing to check, but this error message can also be caused by iptables. Do you have rules restricting tcp input or output?
– Mark Plotnick
Nov 30 at 2:37
I have no firewall
– Martin Vegter
Nov 30 at 6:05
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
when I try iscsiadm discovery:
iscsiadm -m discovery -t sendtargets -p <IP>
I get this error:
iscsiadm: cannot make connection to <IP>: No route to host
however, I can ping the IP fine.
I have added following rule in route:
ip route add <IP>/32 via 10.10.10.1 dev eth1
and i can confirm that ping pings through eth1 interface:
ping -I eth1 <IP>
but for some reason, it looks as if iscsiadm is not using my route settings ?
and traceroute works as well:
# traceroute <IP>
traceroute to <IP>, 30 hops max, 60 byte packets
1 10.10.10.1 0.555 ms 0.776 ms 0.973 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 myhost (<IP>) 0.714 ms !X 0.657 ms !X 0.674 ms !X
networking ping route iscsi
asked Nov 29 at 6:48
Martin Vegter
16634119234
when I try iscsiadm discovery:
iscsiadm -m discovery -t sendtargets -p <IP>
I get this error:
iscsiadm: cannot make connection to <IP>: No route to host
however, I can ping the IP fine.
I have added following rule in route:
ip route add <IP>/32 via 10.10.10.1 dev eth1
and i can confirm that ping pings through eth1 interface:
ping -I eth1 <IP>
but for some reason, it looks as if iscsiadm is not using my route settings ?
and traceroute works as well:
# traceroute <IP>
traceroute to <IP>, 30 hops max, 60 byte packets
1 10.10.10.1 0.555 ms 0.776 ms 0.973 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 myhost (<IP>) 0.714 ms !X 0.657 ms !X 0.674 ms !X
networking ping route iscsi
networking ping route iscsi
asked Nov 29 at 6:48
Martin Vegter
16634119234
asked Nov 29 at 6:48
Martin Vegter
16634119234
edited Nov 29 at 7:31
asked Nov 29 at 6:48
Martin Vegter
16634119234
asked Nov 29 at 6:48
Martin Vegter
16634119234
asked Nov 29 at 6:48
Martin Vegter
16634119234
16634119234
What doestraceroute <IP>say?
– Mark Plotnick
Nov 29 at 7:20
@Mark Plotnick - traceroute works. Please see my edit.
– Martin Vegter
Nov 29 at 7:32
OK, routing was the first thing to check, but this error message can also be caused by iptables. Do you have rules restricting tcp input or output?
– Mark Plotnick
Nov 30 at 2:37
I have no firewall
– Martin Vegter
Nov 30 at 6:05
add a comment |
What doestraceroute <IP>say?
– Mark Plotnick
Nov 29 at 7:20
@Mark Plotnick - traceroute works. Please see my edit.
– Martin Vegter
Nov 29 at 7:32
OK, routing was the first thing to check, but this error message can also be caused by iptables. Do you have rules restricting tcp input or output?
– Mark Plotnick
Nov 30 at 2:37
I have no firewall
– Martin Vegter
Nov 30 at 6:05
What does
traceroute <IP> say?– Mark Plotnick
Nov 29 at 7:20
What does
traceroute <IP> say?– Mark Plotnick
Nov 29 at 7:20
@Mark Plotnick - traceroute works. Please see my edit.
– Martin Vegter
Nov 29 at 7:32
@Mark Plotnick - traceroute works. Please see my edit.
– Martin Vegter
Nov 29 at 7:32
OK, routing was the first thing to check, but this error message can also be caused by iptables. Do you have rules restricting tcp input or output?
– Mark Plotnick
Nov 30 at 2:37
OK, routing was the first thing to check, but this error message can also be caused by iptables. Do you have rules restricting tcp input or output?
– Mark Plotnick
Nov 30 at 2:37
I have no firewall
– Martin Vegter
Nov 30 at 6:05
I have no firewall
– Martin Vegter
Nov 30 at 6:05
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f484835%2fiscsiadm-cannot-make-connection-to-ip-no-route-to-host%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
What does
traceroute <IP>say?– Mark Plotnick
Nov 29 at 7:20
@Mark Plotnick - traceroute works. Please see my edit.
– Martin Vegter
Nov 29 at 7:32
OK, routing was the first thing to check, but this error message can also be caused by iptables. Do you have rules restricting tcp input or output?
– Mark Plotnick
Nov 30 at 2:37
I have no firewall
– Martin Vegter
Nov 30 at 6:05