Weird (unsecure?) behaviour when trying IP forwarding.
- From: "mvhaen" <michael.compote@xxxxxxxxx>
- Date: 6 Sep 2006 09:04:44 -0700
Hi,
A colleague of mine already asked this question a while back, but we
are still struggling with this problem and haven't gotten any response.
Perhaps it would be nice to have someone from Microsoft comment on
this.
We have tried the following steps to try and activate the ip
forwarding, in the end the registry looks good and even the call return
that everything should be enabled.
1. Change the registry:
HKEY_LOCAL_MACHINE\Comm\Tcpip\Parms\IpEnableRouter registry value from
0 to 1
2. Perform a soft reset of the PDA! <--- You seem to be missing this
important step. Remember that this is Windows, so you must reboot a lot
;-)
3. Enable forwarding using GetIPStatistics/SetIPStatistics. Step 3 is
only effective after rebooting (step 2).
The weird thing is that the pocket PC devices are showing some really
weird behaviour. When I send a ping from my laptop with the destination
MAC address set to my PDAs mac, but the destination IP address is not
one of the PDA. I just add a host specific route to my laptop saying
that I can reach the host with IP e.g. 169.254.2.1 through my PDA which
has e.g. 169.254.238.239 (same subnet).
If I do it like that the PDA just sends a ping reply to my laptop
acting like packet was meant for him, and not even bothering to check
the destination ip address.
I'm starting to think that maybe the IpEnableRouter does work, but
somehow the packets are always accepted, but then why is this and what
causes this behaviour? It certainly doesn't look secure to me since it
works for just about any UDP or TCP packet and you would get an ICMP
port unreachable back or even worse get connected to the socket if an
app is listening
Don't laugh with the last thing, at one moment we had an app running on
three devices and wanted to try the ip forwarding on a wireless channel
(e.g. A - B - C). The app worked allright but when A tried to connect
to C, B just passed on the packets to its own transport layer and the
receiver side of the app started running on B instead of C which never
saw any of the packets going his way.
Can anybody tell me what we are doing wrong? Is this a device related
issue? If so, are there devices that do offer this functionality?
Regards,
Michael
.
- Prev by Date: Re: VPN, RasDial, WiFi, GPRS coexistence
- Next by Date: Re: How to create bluetooth binary SDP record for a service?
- Previous by thread: Re: VPN, RasDial, WiFi, GPRS coexistence
- Next by thread: I am trying to use raw socket in windows mobile 5.
- Index(es):
Relevant Pages
|
