Windows Routing issue
Donald Pearson
donaldwhpearson at gmail.com
Thu Nov 19 21:35:35 CET 2009
No reason comes to mind for me right now, as to why your traffic would not
get past the LAN interface. I think that Guus certainly has a good point,
your traffic from the client may very well be getting to the server and
beyond, but those devices don't know how to send that traffic back.
Is there any way for you to sniff packet at your server's internet gateway
for example, and see if you can see those ICMP packets from your client
coming down the wire?
On Tue, Nov 17, 2009 at 5:23 PM, Robert Spraggs
<rspraggs at aegissystems.com>wrote:
> Thanks for the help. I am getting closer. I decided to simplify my testing
> and put the server on an XP box and enabled the IP Routing. I can now ping
> from the client to the LAN interface (192.168.2.115) on the server, but it
> is not allowing me to ping anything further than that.
>
> Any suggestions?
>
> Robert
>
>
> Donald Pearson wrote:
>
> True, but it's one piece of the puzzle.
>
> Now I would use pathping<http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/pathping.mspx?mfr=true>with the -i switch sourcing your TAP adapter, and see what happens when you
> try to get out.
>
> On Tue, Nov 17, 2009 at 2:24 PM, Robert Spraggs <rspraggs at aegissystems.com
> > wrote:
>
>> It was not enabled. I enabled it, but I guess I am going to have to figure
>> out how to get the TAP to route through the LAN interface. The server is a
>> Windows 2003 box, so it's likely going to be much more complicated than a
>> simple registry switch.
>>
>> Thanks for the help
>>
>> Robert
>>
>> Donald Pearson wrote:
>>
>> Did you enable IP routing on your server?
>>
>> If you see my ipconfig/all below, you'll see that IP routing is not
>> enabled on my computer, therefore if it will not act as a gateway or a
>> router to other networks.
>>
>> Microsoft Windows [Version 6.1.7100]
>> Copyright (c) 2009 Microsoft Corporation. All rights reserved.
>>
>> C:\Users\Donald>ipconfig /all
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : Cosmos
>> Primary Dns Suffix . . . . . . . :
>> Node Type . . . . . . . . . . . . : Hybrid
>> IP Routing Enabled. . . . . . . . : No
>> WINS Proxy Enabled. . . . . . . . : No
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>>
>> On Tue, Nov 17, 2009 at 1:13 PM, Robert Spraggs <
>> rspraggs at aegissystems.com> wrote:
>>
>>> Hello All,
>>>
>>> I took a break from trying to get Tinc working and have come back to it
>>> now with the release of 1.0.11. I have 2 Windows computers connected
>>> behind firewalls and everything seems to be correct, except I cannot
>>> seem to get any data past the server TAP interface. I can ping the
>>> Server TAP interface from the client, but no data will move through the
>>> TAP interface to the Internet. I have put my information below in hopes
>>> that someone can help find the answer. I know it has to be something
>>> simple, but I can't figure it out.
>>>
>>> Thanks for the help.
>>>
>>> Client:
>>> Firewall Internet Interface: 96.50.224.239
>>> Firewall LAN Interface: 192.168.1.2
>>> LAN: 192.168.1.108 netmask 255.255.255.0 gw 192.168.1.2
>>> TAP: 10.2.1.12 netmask 255.255.0.0
>>>
>>> Address=96.50.224.239
>>> Subnet=10.2.1.12/32
>>>
>>> Routing table:
>>>
>>> ===========================================================================
>>> Interface List
>>> 0x1 ........................... MS TCP Loopback interface
>>> 0x2 ...00 ff d3 00 a9 49 ...... TAP-Win32 Adapter V9
>>> 0x3 ...00 13 20 ab 73 df ...... Intel(R) PRO/100 VE Network Connection -
>>> Packet Scheduler Miniport
>>>
>>> ===========================================================================
>>>
>>> ===========================================================================
>>> Active Routes:
>>> Network Destination Netmask Gateway Interface
>>> Metric
>>> 0.0.0.0 0.0.0.0 10.2.54.1 10.2.1.12 3
>>> 0.0.0.0 0.0.0.0 192.168.1.2 192.168.1.108 10
>>> 10.2.0.0 255.255.0.0 10.2.1.12 10.2.1.12 3
>>> 10.2.1.12 255.255.255.255 127.0.0.1 127.0.0.1 3
>>> 10.255.255.255 255.255.255.255 10.2.1.12 10.2.1.12 3
>>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
>>> 192.168.1.0 255.255.255.0 192.168.1.108 192.168.1.108 10
>>> 192.168.1.108 255.255.255.255 127.0.0.1 127.0.0.1 10
>>> 192.168.1.255 255.255.255.255 192.168.1.108 192.168.1.108 10
>>> 224.0.0.0 240.0.0.0 10.2.1.12 10.2.1.12 3
>>> 224.0.0.0 240.0.0.0 192.168.1.108 192.168.1.108 10
>>> 255.255.255.255 255.255.255.255 10.2.1.12 10.2.1.12 1
>>> 255.255.255.255 255.255.255.255 192.168.1.108 192.168.1.108 1
>>> Default Gateway: 10.2.54.1
>>>
>>> ===========================================================================
>>> Persistent Routes:
>>> None
>>>
>>> Server:
>>> Firewall Internet Interface: 96.50.224.241
>>> Firewall LAN Interface: 192.168.2.2
>>> LAN: 192.168.2.115 netmask 255.255.255.0 gw 192.168.2.2
>>> TAP: 10.2.54.1 netmask 255.255.0.0
>>>
>>> Address=96.50.224.241
>>> Subnet=10.2.54.1/32
>>> Subnet=0.0.0.0/0
>>>
>>>
>>>
>>> IPv4 Route Table
>>>
>>> ===========================================================================
>>> Interface List
>>> 0x1 ........................... MS TCP Loopback interface
>>> 0x70003 ...00 1d 09 a0 c2 03 ...... Intel(R) 82562V-2 10/100 Network
>>> Connection
>>> 0x70004 ...00 ff 9c d2 29 e7 ...... TAP-Win32 Adapter V9
>>>
>>> ===========================================================================
>>>
>>> ===========================================================================
>>> Active Routes:
>>> Network Destination Netmask Gateway Interface
>>> Metric
>>> 0.0.0.0 0.0.0.0 192.168.2.2 192.168.2.115 30
>>> 0.0.0.0 0.0.0.0 192.168.2.115 10.2.54.1 30
>>> 10.2.0.0 255.255.0.0 10.2.54.1 10.2.54.1 30
>>> 10.2.54.1 255.255.255.255 127.0.0.1 127.0.0.1 30
>>> 10.255.255.255 255.255.255.255 10.2.54.1 10.2.54.1 30
>>> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
>>> 192.168.2.0 255.255.255.0 192.168.2.115 192.168.2.115 30
>>> 192.168.2.115 255.255.255.255 127.0.0.1 127.0.0.1 30
>>> 192.168.2.255 255.255.255.255 192.168.2.115 192.168.2.115 30
>>> 224.0.0.0 240.0.0.0 10.2.54.1 10.2.54.1 30
>>> 224.0.0.0 240.0.0.0 192.168.2.115 192.168.2.115 30
>>> 255.255.255.255 255.255.255.255 10.2.54.1 10.2.54.1
>>> 1
>>> 255.255.255.255 255.255.255.255 192.168.2.115 192.168.2.115
>>> 1
>>> Default Gateway: 192.168.2.2
>>>
>>> ===========================================================================
>>> Persistent Routes:
>>> None
>>>
>>> _______________________________________________
>>> tinc mailing list
>>> tinc at tinc-vpn.org
>>> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> tinc mailing listtinc at tinc-vpn.orghttp://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>>
>> ------------------------------
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.5.425 / Virus Database: 270.14.69/2508 - Release Date: 11/17/09 07:40:00
>>
>>
>>
>>
>> _______________________________________________
>> tinc mailing list
>> tinc at tinc-vpn.org
>> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>>
>>
> ------------------------------
>
> _______________________________________________
> tinc mailing listtinc at tinc-vpn.orghttp://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
> ------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.425 / Virus Database: 270.14.69/2508 - Release Date: 11/17/09 07:40:00
>
>
>
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.tinc-vpn.org/pipermail/tinc/attachments/20091119/4e8f03fc/attachment.htm>
More information about the tinc
mailing list