How can two interface communicate between them with different subnet
up vote
1
down vote
favorite
R1 and R2 are connected with serial cable interface but both of them having different subnet and i know they will not communicate so what are other options two communicate between them without the concept of multiple ip's
router interface
asked 10 hours ago
Adil Bashrahil
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
favorite
R1 and R2 are connected with serial cable interface but both of them having different subnet and i know they will not communicate so what are other options two communicate between them without the concept of multiple ip's
router interface
asked 10 hours ago
Adil Bashrahil
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Welcome to Network Engineering! For two IP hosts in different networks to communicate, you need to route between them. What you're asking to do can't be done without a lot of "magical" configuration.
– Ron Trunk
10 hours ago
I beg to differ! See answer below.
– jonathanjo
9 hours ago
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
R1 and R2 are connected with serial cable interface but both of them having different subnet and i know they will not communicate so what are other options two communicate between them without the concept of multiple ip's
router interface
asked 10 hours ago
Adil Bashrahil
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
R1 and R2 are connected with serial cable interface but both of them having different subnet and i know they will not communicate so what are other options two communicate between them without the concept of multiple ip's
router interface
router interface
asked 10 hours ago
Adil Bashrahil
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
Adil Bashrahil
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
Adil Bashrahil
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 10 hours ago
Adil Bashrahil
61
asked 10 hours ago
Adil Bashrahil
61
61
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Adil Bashrahil is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1
Welcome to Network Engineering! For two IP hosts in different networks to communicate, you need to route between them. What you're asking to do can't be done without a lot of "magical" configuration.
– Ron Trunk
10 hours ago
I beg to differ! See answer below.
– jonathanjo
9 hours ago
add a comment |
1
Welcome to Network Engineering! For two IP hosts in different networks to communicate, you need to route between them. What you're asking to do can't be done without a lot of "magical" configuration.
– Ron Trunk
10 hours ago
I beg to differ! See answer below.
– jonathanjo
9 hours ago
1
1
Welcome to Network Engineering! For two IP hosts in different networks to communicate, you need to route between them. What you're asking to do can't be done without a lot of "magical" configuration.
– Ron Trunk
10 hours ago
Welcome to Network Engineering! For two IP hosts in different networks to communicate, you need to route between them. What you're asking to do can't be done without a lot of "magical" configuration.
– Ron Trunk
10 hours ago
I beg to differ! See answer below.
– jonathanjo
9 hours ago
I beg to differ! See answer below.
– jonathanjo
9 hours ago
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
You can configure them with point-to-point routes as follows, as tested in Packet Tracer (three 2901 routers with HWIC-2T). R1 has default route to interface, R3 has default route to next-hop address, and R2 has a manual route to interface plus an interface route.
R1:
interface Serial0/0/0
ip address 131.43.43.1 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 Serial0/0/0
R2:
interface Serial0/0/0
ip address 131.44.44.2 255.255.255.224
clock rate 2000000
!
interface Serial0/0/1
ip address 140.10.10.2 255.255.255.224
clock rate 2000000
!
ip route 131.43.43.0 255.255.255.224 Serial0/0/0
R3:
interface Serial0/0/1
ip address 140.10.10.3 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 140.10.10.2
answered 9 hours ago
jonathanjo
8,9511630
add a comment |
up vote
2
down vote
A serial interface is (often) an "unnumbered" interface, ie. there's no need for an IP address binding (nor does one usually matter).
Ethernet interfaces and the like require an address because Ethernet's data link layer doesn't work without a layer-2 address, and a layer-3 address is required to find out a router's local layer-2 address. A serial interface simply transmits a packet from source to destination without any need of addressing; it's always point-to-point.
What you do need though are routing table entries for the remote subnets as jonathanjo has already pointed out. These can be set up statically or exchanged via a routing protocol like OSPF.
answered 9 hours ago
Zac67
24.3k21252
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
You can configure them with point-to-point routes as follows, as tested in Packet Tracer (three 2901 routers with HWIC-2T). R1 has default route to interface, R3 has default route to next-hop address, and R2 has a manual route to interface plus an interface route.
R1:
interface Serial0/0/0
ip address 131.43.43.1 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 Serial0/0/0
R2:
interface Serial0/0/0
ip address 131.44.44.2 255.255.255.224
clock rate 2000000
!
interface Serial0/0/1
ip address 140.10.10.2 255.255.255.224
clock rate 2000000
!
ip route 131.43.43.0 255.255.255.224 Serial0/0/0
R3:
interface Serial0/0/1
ip address 140.10.10.3 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 140.10.10.2
answered 9 hours ago
jonathanjo
8,9511630
add a comment |
up vote
3
down vote
You can configure them with point-to-point routes as follows, as tested in Packet Tracer (three 2901 routers with HWIC-2T). R1 has default route to interface, R3 has default route to next-hop address, and R2 has a manual route to interface plus an interface route.
R1:
interface Serial0/0/0
ip address 131.43.43.1 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 Serial0/0/0
R2:
interface Serial0/0/0
ip address 131.44.44.2 255.255.255.224
clock rate 2000000
!
interface Serial0/0/1
ip address 140.10.10.2 255.255.255.224
clock rate 2000000
!
ip route 131.43.43.0 255.255.255.224 Serial0/0/0
R3:
interface Serial0/0/1
ip address 140.10.10.3 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 140.10.10.2
answered 9 hours ago
jonathanjo
8,9511630
add a comment |
up vote
3
down vote
up vote
3
down vote
You can configure them with point-to-point routes as follows, as tested in Packet Tracer (three 2901 routers with HWIC-2T). R1 has default route to interface, R3 has default route to next-hop address, and R2 has a manual route to interface plus an interface route.
R1:
interface Serial0/0/0
ip address 131.43.43.1 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 Serial0/0/0
R2:
interface Serial0/0/0
ip address 131.44.44.2 255.255.255.224
clock rate 2000000
!
interface Serial0/0/1
ip address 140.10.10.2 255.255.255.224
clock rate 2000000
!
ip route 131.43.43.0 255.255.255.224 Serial0/0/0
R3:
interface Serial0/0/1
ip address 140.10.10.3 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 140.10.10.2
answered 9 hours ago
jonathanjo
8,9511630
You can configure them with point-to-point routes as follows, as tested in Packet Tracer (three 2901 routers with HWIC-2T). R1 has default route to interface, R3 has default route to next-hop address, and R2 has a manual route to interface plus an interface route.
R1:
interface Serial0/0/0
ip address 131.43.43.1 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 Serial0/0/0
R2:
interface Serial0/0/0
ip address 131.44.44.2 255.255.255.224
clock rate 2000000
!
interface Serial0/0/1
ip address 140.10.10.2 255.255.255.224
clock rate 2000000
!
ip route 131.43.43.0 255.255.255.224 Serial0/0/0
R3:
interface Serial0/0/1
ip address 140.10.10.3 255.255.255.224
!
ip route 0.0.0.0 0.0.0.0 140.10.10.2
answered 9 hours ago
jonathanjo
8,9511630
edited 4 hours ago
answered 9 hours ago
jonathanjo
8,9511630
answered 9 hours ago
jonathanjo
8,9511630
answered 9 hours ago
jonathanjo
8,9511630
8,9511630
add a comment |
add a comment |
up vote
2
down vote
A serial interface is (often) an "unnumbered" interface, ie. there's no need for an IP address binding (nor does one usually matter).
Ethernet interfaces and the like require an address because Ethernet's data link layer doesn't work without a layer-2 address, and a layer-3 address is required to find out a router's local layer-2 address. A serial interface simply transmits a packet from source to destination without any need of addressing; it's always point-to-point.
What you do need though are routing table entries for the remote subnets as jonathanjo has already pointed out. These can be set up statically or exchanged via a routing protocol like OSPF.
answered 9 hours ago
Zac67
24.3k21252
add a comment |
up vote
2
down vote
A serial interface is (often) an "unnumbered" interface, ie. there's no need for an IP address binding (nor does one usually matter).
Ethernet interfaces and the like require an address because Ethernet's data link layer doesn't work without a layer-2 address, and a layer-3 address is required to find out a router's local layer-2 address. A serial interface simply transmits a packet from source to destination without any need of addressing; it's always point-to-point.
What you do need though are routing table entries for the remote subnets as jonathanjo has already pointed out. These can be set up statically or exchanged via a routing protocol like OSPF.
answered 9 hours ago
Zac67
24.3k21252
add a comment |
up vote
2
down vote
up vote
2
down vote
A serial interface is (often) an "unnumbered" interface, ie. there's no need for an IP address binding (nor does one usually matter).
Ethernet interfaces and the like require an address because Ethernet's data link layer doesn't work without a layer-2 address, and a layer-3 address is required to find out a router's local layer-2 address. A serial interface simply transmits a packet from source to destination without any need of addressing; it's always point-to-point.
What you do need though are routing table entries for the remote subnets as jonathanjo has already pointed out. These can be set up statically or exchanged via a routing protocol like OSPF.
answered 9 hours ago
Zac67
24.3k21252
A serial interface is (often) an "unnumbered" interface, ie. there's no need for an IP address binding (nor does one usually matter).
Ethernet interfaces and the like require an address because Ethernet's data link layer doesn't work without a layer-2 address, and a layer-3 address is required to find out a router's local layer-2 address. A serial interface simply transmits a packet from source to destination without any need of addressing; it's always point-to-point.
What you do need though are routing table entries for the remote subnets as jonathanjo has already pointed out. These can be set up statically or exchanged via a routing protocol like OSPF.
answered 9 hours ago
Zac67
24.3k21252
edited 7 hours ago
answered 9 hours ago
Zac67
24.3k21252
answered 9 hours ago
Zac67
24.3k21252
answered 9 hours ago
Zac67
24.3k21252
24.3k21252
add a comment |
add a comment |
Adil Bashrahil is a new contributor. Be nice, and check out our Code of Conduct.
Adil Bashrahil is a new contributor. Be nice, and check out our Code of Conduct.
Adil Bashrahil is a new contributor. Be nice, and check out our Code of Conduct.
Adil Bashrahil is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Network Engineering 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%2fnetworkengineering.stackexchange.com%2fquestions%2f55093%2fhow-can-two-interface-communicate-between-them-with-different-subnet%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
1
Welcome to Network Engineering! For two IP hosts in different networks to communicate, you need to route between them. What you're asking to do can't be done without a lot of "magical" configuration.
– Ron Trunk
10 hours ago
I beg to differ! See answer below.
– jonathanjo
9 hours ago