Hello, > I tried to set the correct IP address with > SNAT, but it seems that SNAT refuses to use the same port where some > application is listening on. So, if I use "iptables -t nat -A POSTROUTING > ... --to-source 129.217.14.81:67", nothing is sent, in contrast to other > ports. For some experiments, I added an iptables-rule, so that the mark is not only set if the source port is bootps, but also if the destination port is bootpc. And now, I am completely confused, because I found out that though there is a relation between the port I use in "iptables -t nat ..." and if a message is sent, there must also be another reason why messages are not sent with this kind of NAT. When a DHCP client sends a unicast request to port bootps, the DHCP unicast reply is never sent when I use port 67 in SNAT. But when I use netcat sessions in a command line on the DHCP server to send messages to port bootpc of a client, messages are sent in some netcat sessions, but in other sessions, they do not, no matter which port I use in SNAT. Maybe the OS sometimes decides that the port is already in use and refuses to send messages from that port? Regards Christoph -- To unsubscribe from this list: send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
