scip/udpxd
1
0
Fork 0
mirror of https://codeberg.org/scip/udpxd.git synced 2025-12-16 19:40:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

txt tweaks

Browse Source
This commit is contained in:
TLINDEN
2015-04-21 20:14:13 +02:00
parent 544bb68bd0
commit d30d8496b0
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
udpxd.pod
View File

@@ -46,23 +46,23 @@ with two interfaces: eth0 on the inside, eth1 on the outside:
foo:
eth0: 192.168.1.1
eth0: 10.0.0.1
eth1: 10.0.0.1
And let's say, you have a client in network 10.0.0.0/24 who whiches to reach
an ntp server in network 192.168.1.1; and you dont operate a
an ntp server in network 192.168.1.0/24; and you dont operate a
firewall, nat or routing on 'foo'. Run udpxd like this:
udpxd -l 10.0.0.1:123 -d 192.168.1.199:123
Now, if a client with the source ip address 10.0.0.110 sends
an ntp request to 10.0.0.1:123, udpxd will forward that
request to 192.168.1.199:123 with the source ip address
a ntp request to 10.0.0.1:123, udpxd will forward that
packet to 192.168.1.199:123 with the source ip address
192.168.1.1 (because this is where the route points to: eth0).
Responses from the ntp server will reach udpxd, which in turn
sends them back to the client, where they arrive with the source
address (and port) where udpxd is listening.
As you can see, udpxd canbe used to implement hiding nat for
As you can see, udpxd can be used to implement hiding nat for
udp services in user space.
Another example would be, if 'foo' has multiple ip addresses
@@ -80,7 +80,7 @@ B<-b> parameter:
In this case for the client everything looks as before, but the
ntp server on the other end will see ntp requests coming from
192.168.1.45.
192.168.1.45 instead.
=head1 FILES