From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: forward udp broadcast packets on same subnet /interface with diff source
Date: Wed, 14 Jul 2004 10:03:22 +0100 [thread overview]
Message-ID: <200407141003.22689.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <3063e5040713225778147c4d@mail.gmail.com>
On Wednesday 14 July 2004 6:57 am, George Alexandru Dragoi wrote:
> One more thingg, you'll have to set ip_forward to 1
Won't help. The packets addressed to 192.168.1.255 have already reached
their destination, therefore the routing table won't forward them further
through the netfilter machine.
Regards,
Antony.
> On Tue, 13 Jul 2004 22:02:47 -0700 (PDT), Tom Thumb
>
> <tomthumb888@yahoo.com> wrote:
> > Hi,
> >
> > Can I use iptables to forward UDP broadcast packets on
> > the same subnet and interface but just change the
> > source IP?
> >
> > That is, the forwarding machine is 192.168.1.5, with
> > mask 255.255.255.0 and has a single NIC.
> >
> > A machine with IP 192.168.1.6 with the same mask sends
> > a UDP broadcast to 192.168.1.255.
> >
> > The forwarding machine receives this packet. Can it be
> > configured to resend it out on the same interface that
> > it received it on (its only interface) and just change
> > the source IP to be a 3rd address, like 192.168.1.7,
> > but also as a UDP broadcast to 192.168.1.255?
> >
> > Is there any way to do this without adding a physical
> > NIC? Do I need to add a "virtual" NIC to do it? How?
> >
> > Thanks
--
Tax inspectors are just accountants who work for the evil dictators of
democracy.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-07-14 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 5:02 forward udp broadcast packets on same subnet /interface with diff source Tom Thumb
2004-07-14 5:57 ` George Alexandru Dragoi
2004-07-14 9:03 ` Antony Stone [this message]
2004-07-14 9:01 ` Antony Stone
[not found] ` <3063e50407132231c03fefc@mail.gmail.com>
2004-07-14 12:18 ` George Alexandru Dragoi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200407141003.22689.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.