S
S
slava_ch2013-02-19 15:47:51
Computer networks
slava_ch, 2013-02-19 15:47:51

Request outside, using an internal address

It's probably normal, but I'm the first to come across this.
Situation: The hoster has our server, with an external IP, it is not connected to any other network. The server does not have any VPN or other tunnels. To put it mildly, I was surprised when I saw this in the dump: The “source” is the internal address of the client, which is located behind the Dlink-320 router. Can you explain this behavior, and how correct is it?



Answer the question

In order to leave comments, you need to log in

2 answer(s)
A
alz, 2013-02-19
@slava_ch

The packet slipped through the router (didn't get picked up) and ran to your server. This is possible if there were no special filters anywhere along the way.

M
merlin-vrn, 2013-02-19
@merlin-vrn

Actually, what's the deal with the server? If it has a (reverse) route, it will boldly send the address along that reverse route, and that's it. Packets with "gray" addresses are exactly the same as with "white" ones and work in exactly the same way. The whole difference comes from the fact that there are no (should not be) routes to them in the global routing tables.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question