1 |
On Wednesday 24 October 2007, Etaoin Shrdlu wrote: |
2 |
> On Wednesday 24 October 2007, Mick wrote: |
3 |
> > Thanks guys. The AP has a reserved static LAN IP address on the |
4 |
> > router (10.10.10.13). It also has a MAC. So it is simply a matter of |
5 |
> > forwarding (all) ICMP echo-reply packets that arrive from the Internet |
6 |
> > to that LAN address. (On this implementation the AP is itself a |
7 |
> > Linksys wireless router). |
8 |
> > |
9 |
> > I wonder if I can play tricks with ping's ICMP headers to |
10 |
> > differentiate between them as they come into the router, or something |
11 |
> > clever that I haven't yet figured out. Any ideas? |
12 |
> |
13 |
> Disclaimer: I have not tested what follows. |
14 |
> |
15 |
> Can't you just use traceroute? |
16 |
> If you run tracert from windows, it should already work, since it uses |
17 |
> ICMP echo requests. Otherwise, you should open UDP port 33434 on the |
18 |
> router. |
19 |
|
20 |
I don't have access to a MS Windows machine right now, but using mtr I get: |
21 |
==================================================== |
22 |
[snip . . .] |
23 |
|
24 |
23. XX-XX-XXX-XX.dhcp.kgpt.tn.cha 6.7% 15 145.5 145.4 143.2 146.9 1.3 |
25 |
24. ??? 100.0 15 0.0 0.0 0.0 0.0 0.0 |
26 |
25. XX.XX.XXX.XXX 6.7% 15 155.9 156.2 154.2 159.1 1.3 |
27 |
==================================================== |
28 |
|
29 |
It seems that hop 23 is the dhcp server of the ISP. Hop 25. is the public IP |
30 |
address of the router. I assume that hop 24. is the cable modem which acts |
31 |
as a bridge(?). |
32 |
|
33 |
Since the AP is within the LAN and the connection to it is NAT'ed, it is not |
34 |
shown above. Am I correct in my thinking? |
35 |
-- |
36 |
Regards, |
37 |
Mick |