|
Home > Archive > Red Hat Networking > January 2004 > Multible subnet route issue.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Multible subnet route issue.
|
|
| Sams News 2004-01-23, 7:34 pm |
|
I have several ip's comming in to my site through D link routers. I have that working but now I can
not ping each other system internally on the lan. I am looking for a linux route command that will
allow me to get back my internal lan.
+------+ +--------+ 192.168.1.2
--------|D-link|------------|System 1| 192.168.1.3
| +------- +--------+
| Wan ip 216.228.19.53
| Wan gw 216.228.19.1
| Lan gw 192.168.1.1
|
|
+---+ +------+ |
|Wan|---|Switch|--+
+---+ +------+ |
|
|
|
|
|
| +------+ +--------+ 192.168.2.21
--------|D-link|------------|System 2| 192.168.2.31
+------- +--------+
Wan ip 216.228.19.185
Wan gw 216.228.19.1
Lan gw 192.168.2.1
System 1 and System 2 can get out to the internet (Wan) ok, But System 1 can not see/ping System 2.
I can tried the follow route command on System 1.
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
This has had no effect.
Please be specific about the commands and which systems they may need to be placed in your replys.
Please to not reply with iptable command as I am only looking for route commands.
| |
| Gregory A. Brown 2004-01-23, 7:34 pm |
| I'm not sure it is possible to do what you want using the configuration you
describe. It appears that you have each router set up to provide NAT for
the systems behind it. Without getting into the particulars (because they
are a little fuzzy to me), I would say that you need to install a "bridge"
between the two subnets. In its simplest form, this would be a computer
with 2 NICs, one connected to the 192.168.1.0 subnet and one connected to
the the 192.168.2.0 subnet. Since both System 1 and System 2 appear to
have dual NICs, you could easily connect either of them to both subnets.
If you do this, then the route command would be:
route add -net 192.168.2.0 netmask 255.255.255.0 gw <IP address of NIC on
192.168.1.0 subnet>
To go from the 192.168.2.0 subnet to the 192.168.1.0 subnet, adjust the
above route command accordingly.
I assume there is a reason for wanting separation between the systems to
the point of running 2 routers. An alternate suggestion might be to run
only 1 router, but still maintain 2 separate subnets (with the router
serving as the gateway between the two).
There are probably better people on here to explain this than I.
Hopefully, what I have written makes sense. Feel free to follow up with
any questions.
Greg
Sams News <srogers@redshift.com> wrote in
news:vk2ufd499o6b19@corp.supernews.com:
quote:
>
> I have several ip's comming in to my site through D link routers. I
> have that working but now I can not ping each other system internally
> on the lan. I am looking for a linux route command that will allow me
> to get back my internal lan.
>
>
> +------+ +--------+ 192.168.1.2
> --------|D-link|------------|System 1| 192.168.1.3
> | +------- +--------+
> | Wan ip 216.228.19.53
> | Wan gw 216.228.19.1
> | Lan gw 192.168.1.1
> |
> |
> +---+ +------+ |
> |Wan|---|Switch|--+
> +---+ +------+ |
> |
> |
> |
> |
> |
> | +------+ +--------+ 192.168.2.21
> --------|D-link|------------|System 2| 192.168.2.31
> +------- +--------+
> Wan ip 216.228.19.185
> Wan gw 216.228.19.1
> Lan gw 192.168.2.1
>
>
>
> System 1 and System 2 can get out to the internet (Wan) ok, But System
> 1 can not see/ping System 2.
>
> I can tried the follow route command on System 1.
>
> route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
>
> This has had no effect.
>
> Please be specific about the commands and which systems they may need
> to be placed in your replys. Please to not reply with iptable command
> as I am only looking for route commands.
>
>
>
| |
| Gregory A. Brown 2004-01-23, 7:34 pm |
| I'm not sure it is possible to do what you want using the configuration you
describe. It appears that you have each router set up to provide NAT for
the systems behind it. Without getting into the particulars (because they
are a little fuzzy to me), I would say that you need to install a "bridge"
between the two subnets. In its simplest form, this would be a computer
with 2 NICs, one connected to the 192.168.1.0 subnet and one connected to
the the 192.168.2.0 subnet. Since both System 1 and System 2 appear to
have dual NICs, you could easily connect either of them to both subnets.
If you do this, then the route command would be:
route add -net 192.168.2.0 netmask 255.255.255.0 gw <IP address of NIC on
192.168.1.0 subnet>
To go from the 192.168.2.0 subnet to the 192.168.1.0 subnet, adjust the
above route command accordingly.
I assume there is a reason for wanting separation between the systems to
the point of running 2 routers. An alternate suggestion might be to run
only 1 router, but still maintain 2 separate subnets (with the router
serving as the gateway between the two).
There are probably better people on here to explain this than I.
Hopefully, what I have written makes sense. Feel free to follow up with
any questions.
Greg
Sams News <srogers@redshift.com> wrote in
news:vk2ufd499o6b19@corp.supernews.com:
quote:
>
> I have several ip's comming in to my site through D link routers. I
> have that working but now I can not ping each other system internally
> on the lan. I am looking for a linux route command that will allow me
> to get back my internal lan.
>
>
> +------+ +--------+ 192.168.1.2
> --------|D-link|------------|System 1| 192.168.1.3
> | +------- +--------+
> | Wan ip 216.228.19.53
> | Wan gw 216.228.19.1
> | Lan gw 192.168.1.1
> |
> |
> +---+ +------+ |
> |Wan|---|Switch|--+
> +---+ +------+ |
> |
> |
> |
> |
> |
> | +------+ +--------+ 192.168.2.21
> --------|D-link|------------|System 2| 192.168.2.31
> +------- +--------+
> Wan ip 216.228.19.185
> Wan gw 216.228.19.1
> Lan gw 192.168.2.1
>
>
>
> System 1 and System 2 can get out to the internet (Wan) ok, But System
> 1 can not see/ping System 2.
>
> I can tried the follow route command on System 1.
>
> route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
>
> This has had no effect.
>
> Please be specific about the commands and which systems they may need
> to be placed in your replys. Please to not reply with iptable command
> as I am only looking for route commands.
>
>
>
| |
| Gregory A. Brown 2004-01-23, 7:34 pm |
| I'm not sure it is possible to do what you want using the configuration you
describe. It appears that you have each router set up to provide NAT for
the systems behind it. Without getting into the particulars (because they
are a little fuzzy to me), I would say that you need to install a "bridge"
between the two subnets. In its simplest form, this would be a computer
with 2 NICs, one connected to the 192.168.1.0 subnet and one connected to
the the 192.168.2.0 subnet. Since both System 1 and System 2 appear to
have dual NICs, you could easily connect either of them to both subnets.
If you do this, then the route command would be:
route add -net 192.168.2.0 netmask 255.255.255.0 gw <IP address of NIC on
192.168.1.0 subnet>
To go from the 192.168.2.0 subnet to the 192.168.1.0 subnet, adjust the
above route command accordingly.
I assume there is a reason for wanting separation between the systems to
the point of running 2 routers. An alternate suggestion might be to run
only 1 router, but still maintain 2 separate subnets (with the router
serving as the gateway between the two).
There are probably better people on here to explain this than I.
Hopefully, what I have written makes sense. Feel free to follow up with
any questions.
Greg
Sams News <srogers@redshift.com> wrote in
news:vk2ufd499o6b19@corp.supernews.com:
quote:
>
> I have several ip's comming in to my site through D link routers. I
> have that working but now I can not ping each other system internally
> on the lan. I am looking for a linux route command that will allow me
> to get back my internal lan.
>
>
> +------+ +--------+ 192.168.1.2
> --------|D-link|------------|System 1| 192.168.1.3
> | +------- +--------+
> | Wan ip 216.228.19.53
> | Wan gw 216.228.19.1
> | Lan gw 192.168.1.1
> |
> |
> +---+ +------+ |
> |Wan|---|Switch|--+
> +---+ +------+ |
> |
> |
> |
> |
> |
> | +------+ +--------+ 192.168.2.21
> --------|D-link|------------|System 2| 192.168.2.31
> +------- +--------+
> Wan ip 216.228.19.185
> Wan gw 216.228.19.1
> Lan gw 192.168.2.1
>
>
>
> System 1 and System 2 can get out to the internet (Wan) ok, But System
> 1 can not see/ping System 2.
>
> I can tried the follow route command on System 1.
>
> route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
>
> This has had no effect.
>
> Please be specific about the commands and which systems they may need
> to be placed in your replys. Please to not reply with iptable command
> as I am only looking for route commands.
>
>
>
| |
| Gregory A. Brown 2004-01-23, 7:34 pm |
| I'm not sure it is possible to do what you want using the configuration you
describe. It appears that you have each router set up to provide NAT for
the systems behind it. Without getting into the particulars (because they
are a little fuzzy to me), I would say that you need to install a "bridge"
between the two subnets. In its simplest form, this would be a computer
with 2 NICs, one connected to the 192.168.1.0 subnet and one connected to
the the 192.168.2.0 subnet. Since both System 1 and System 2 appear to
have dual NICs, you could easily connect either of them to both subnets.
If you do this, then the route command would be:
route add -net 192.168.2.0 netmask 255.255.255.0 gw <IP address of NIC on
192.168.1.0 subnet>
To go from the 192.168.2.0 subnet to the 192.168.1.0 subnet, adjust the
above route command accordingly.
I assume there is a reason for wanting separation between the systems to
the point of running 2 routers. An alternate suggestion might be to run
only 1 router, but still maintain 2 separate subnets (with the router
serving as the gateway between the two).
There are probably better people on here to explain this than I.
Hopefully, what I have written makes sense. Feel free to follow up with
any questions.
Greg
Sams News <srogers@redshift.com> wrote in
news:vk2ufd499o6b19@corp.supernews.com:
quote:
>
> I have several ip's comming in to my site through D link routers. I
> have that working but now I can not ping each other system internally
> on the lan. I am looking for a linux route command that will allow me
> to get back my internal lan.
>
>
> +------+ +--------+ 192.168.1.2
> --------|D-link|------------|System 1| 192.168.1.3
> | +------- +--------+
> | Wan ip 216.228.19.53
> | Wan gw 216.228.19.1
> | Lan gw 192.168.1.1
> |
> |
> +---+ +------+ |
> |Wan|---|Switch|--+
> +---+ +------+ |
> |
> |
> |
> |
> |
> | +------+ +--------+ 192.168.2.21
> --------|D-link|------------|System 2| 192.168.2.31
> +------- +--------+
> Wan ip 216.228.19.185
> Wan gw 216.228.19.1
> Lan gw 192.168.2.1
>
>
>
> System 1 and System 2 can get out to the internet (Wan) ok, But System
> 1 can not see/ping System 2.
>
> I can tried the follow route command on System 1.
>
> route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
>
> This has had no effect.
>
> Please be specific about the commands and which systems they may need
> to be placed in your replys. Please to not reply with iptable command
> as I am only looking for route commands.
>
>
>
|
|
|
|
|