All of lore.kernel.org
 help / color / mirror / Atom feed
* DNAT udp 192.163.1.2:514 -> 127.0.0.1:1514 -- from local box
@ 2003-07-16 19:58 Graham Swallow
  0 siblings, 0 replies; 2+ messages in thread
From: Graham Swallow @ 2003-07-16 19:58 UTC (permalink / raw)
  To: LIST-netfilter


VERSION: uptables-1.2.1.a

I Type:
	iptables
		-t nat -A OUTPUT
		-p udp -d 192.168.1.2 --dport 514
		-j DNAT --to 127.0.0.1:1514
It replies:
	iptables: Invalid argument


The traffic is to ORIGINATE from a local process (this is 192.168.1.46),
heading out to a ficticious 192.168.1.2, and DNAT'd to localport 1514

syslogd reuses to log to a port other than 514, but using DNAT as a
kludge should work. I've tried a range of options, and got REDIRECT
to almost work, but after the first packet it gave connection refused.
NAT-HOWTO.txt 6.3.7 says must be OUTPUT and 127  

I am using socat  http://www.dest-unreach.org/socat/  to test

	socat UDP4-LISTEN:1514 -	# server

	socat -  UDP4:127.0.0.1:1514	# client


   regards
--
   Graham
   Information-Cascade -at- ntlworld.com


^ permalink raw reply	[flat|nested] 2+ messages in thread

* RE: DNAT udp 192.163.1.2:514 -> 127.0.0.1:1514 -- from local box
@ 2003-07-16 21:43 George Vieira
  0 siblings, 0 replies; 2+ messages in thread
From: George Vieira @ 2003-07-16 21:43 UTC (permalink / raw)
  To: Graham Swallow, LIST-netfilter

Update your iptables firstly, and secondly use the p-o-m patch to fix the OUTPUT NAT problem.

Thanks,
____________________________________________
George Vieira
Systems Manager
georgev@citadelcomputer.com.au

Citadel Computer Systems Pty Ltd
http://www.citadelcomputer.com.au

-----Original Message-----
From: Graham Swallow [mailto:Information-Cascade@ntlworld.com]
Sent: Thursday, July 17, 2003 5:59 AM
To: LIST-netfilter
Subject: DNAT udp 192.163.1.2:514 -> 127.0.0.1:1514 -- from local box



VERSION: uptables-1.2.1.a

I Type:
	iptables
		-t nat -A OUTPUT
		-p udp -d 192.168.1.2 --dport 514
		-j DNAT --to 127.0.0.1:1514
It replies:
	iptables: Invalid argument


The traffic is to ORIGINATE from a local process (this is 192.168.1.46),
heading out to a ficticious 192.168.1.2, and DNAT'd to localport 1514

syslogd reuses to log to a port other than 514, but using DNAT as a
kludge should work. I've tried a range of options, and got REDIRECT
to almost work, but after the first packet it gave connection refused.
NAT-HOWTO.txt 6.3.7 says must be OUTPUT and 127  

I am using socat  http://www.dest-unreach.org/socat/  to test

	socat UDP4-LISTEN:1514 -	# server

	socat -  UDP4:127.0.0.1:1514	# client


   regards
--
   Graham
   Information-Cascade -at- ntlworld.com



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-07-16 21:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-07-16 19:58 DNAT udp 192.163.1.2:514 -> 127.0.0.1:1514 -- from local box Graham Swallow
2003-07-16 21:43 George Vieira

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.