how to route through specific ip in Multiple IP on one NIC scenari

Hello,

We have 2 VLANS:
VLAN 1 for switch management (192.168.1.0/24)
VLAN 2 for internal use (192.168.0.0/24)

There is a route made on a router (router is managed by another company)
that traffic from 192.168.0.240/32 (vlan2) would be routed to (vlan1)
192.168.1.0.

The purpose of this is that I could manage switches from any machine in my
production environment if i set the ip on it to 192.168.0.240.

I wanted to test if the route made on router by that other company is set
correctly. I connected to my server 192.168.0.250 and set an additional
static ip 192.168.0.240 - so that i could connect to switch management.
However outgoing connections are made from "primary" ip - 192.168.0.250.

i tried to add a static route on my server like that
route add 192.168.1.0 mask 255.255.255.0 192.168.0.240 metric 2

it accepts the input but route print command outputs:
192.168.1.0 255.255.255.0 192.168.0.250 192.168.0.250 2

so it disregards my wish that packets destined for 192.168.1.0 should
originate from 192.168.0.240 (additional static ip address)

Please advice

"Valdas Adomaitis" <(E-Mail Removed)> wrote in message
news:8A084AB9-20BC-4135-80D0-(E-Mail Removed)...
> so it disregards my wish that packets destined for 192.168.1.0 should
> originate from 192.168.0.240 (additional static ip address)

Exactly what it is supposed to do.

Secondary IP#s are used for incomming connections,...they are completetly
irrelevant with outbound connections. 90% of the time secondary IP#s on
regular LAN Hosts is pointless, and in some cases, simply a bad design, a
bad concept.

The *correct* approach is to choose one of these 2 options:

1. Have the "other company" change their device to allow *.250 instead of
*.240. If they are managing the router than that is what managing a router
means. If the config of the router needs to be changed to suit the
environment, then it is their job as "managers" of the router to perform it.

OR

2. Simply re-address your server to *.240 and forget it,...or use a
different machine in the first place that is already running on*.240.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Thank you for your comment.

"Phillip Windell" wrote:

> "Valdas Adomaitis" <(E-Mail Removed)> wrote in message
> news:8A084AB9-20BC-4135-80D0-(E-Mail Removed)...
> > so it disregards my wish that packets destined for 192.168.1.0 should
> > originate from 192.168.0.240 (additional static ip address)
>
> Exactly what it is supposed to do.
>
> Secondary IP#s are used for incomming connections,...they are completetly
> irrelevant with outbound connections. 90% of the time secondary IP#s on
> regular LAN Hosts is pointless, and in some cases, simply a bad design, a
> bad concept.
>
> The *correct* approach is to choose one of these 2 options:
>
> 1. Have the "other company" change their device to allow *.250 instead of
> *.240. If they are managing the router than that is what managing a router
> means. If the config of the router needs to be changed to suit the
> environment, then it is their job as "managers" of the router to perform it.
>
> OR
>
> 2. Simply re-address your server to *.240 and forget it,...or use a
> different machine in the first place that is already running on*.240.
>
>
> --
> Phillip Windell
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
> .
>