Thanks a lot for your reply
My switch is configured to understand VLAN 1 and VLAN 2, they route all the
packets perfectly. Switch accept tagged packets and route all the packet
correctly. So i have created two different VLANs using the switch. They are
different networks.
But this is on the host.. why windows will route the packets through
10.1.70.39 interface with source IP 10.1.70.39?
Thanks
"Neteng" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> VLAN 1 & 2 are the same network (10.1.70.0/24), that's a problem. What
> does
> your switch think vlan 1 & 2 are?
>
> "Rajesh Gupta" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
>> All,
>>
>> I saw some strange behavior on my Windows Server 2003. My configuration
>> is
>> as follows:
>>
>> Windows server 2003.
>> Dual Intel Gige NIC controller (Both are teamed (LACP 802.3ad) together)
>> I have created 3 Virtual Interface (VLANs) on the network controller.
>> VLAN 1, ID 1 IP address=10.1.70.39
>> VLAN 2, ID 2 IP address=10.1.70.38
>> VLAN 3, ID 3 IP address=169.254.255.255
>> All are on the same subnet. 255:255:255:0
>>
>> I want all my data to go through VLAN 1, so i have updated the Route
> table.
>> In the route table i have two entries
>>
>> Active Routes:
>> Network Destination Netmask Gateway Interface
>> Metric
>> 10.1.70.0 255.255.255.0 10.1.70.39
>> 10.1.70.39 1
>> 10.1.70.0 255.255.255.0 10.1.70.38
>> 10.1.70.38 10
>>
>> As i have lowered the METRIC of the first route, Windows server 2003 will
>> use that interface to route all the packets and that interface is for
>> VLAN
>> 1.
>>
>> Everything works fine. But when i ran Ethereal on VLAN 1, i saw some
> packets
>> with With
>> Source IP = 10.1.70.38... Though this interface has IP address
> 10.1.70.39..
>> but packets originating from Server 2003 with Src IP 10.1.70.38 on
>> 10.1.70.39 interface?
>>
>> So i am not sure how Windows can transfer packets on VLAN 1 (10.1.70.39)
>> with Source IP address of VLAN 2 (10.1.70.38)?
>>
>> Route is calculated on the Destination Address and route selected by
> Windows
>> is correct. It shall route all the packets using 10.1.70.39 route. But
>> inside the packets it had 10.1.70.38 as source address.
>>
>> If Application is binding to 10.1.70.38, then why i am seeing these
> packets
>> on this isnterface? They should be routed through 10.1.70.38 (VLAN 2)
> route.
>>
>> So i am not sure what is happening here? any help will be appreciated.
>>
>> Does applications cache the Bind IP address, but i guess its beyond
>> Applications control and even if they bind they shall go through
> 10.1.70.38
>> interface
>> Thanks Rajesh
>>
>>
>
>
|
Similar Threads
Linear Mode
