From: Frans Luteijn <f.a.g.luteijn@knoware.nl>
To: netfilter@lists.netfilter.org
Subject: Re: NAT Helpers?
Date: Thu, 20 Oct 2005 01:27:37 +0200 [thread overview]
Message-ID: <4356D669.A0B07AAF@knoware.nl> (raw)
In-Reply-To: Pine.LNX.4.60.0509121520360.1296@darkstar.sysinfo.com
Some time ago, I had a similar question. Someone came with a little
program
called udp-proxy.
(See
http://lists.netfilter.org/pipermail/netfilter/2004-December/057580.html)
Search in Google for udpproxy and udprelay.
For dhcp-relay use the program dhcrelay, compiled from the dhcp-source
and
included in most distributions.
R. DuFresne schreef:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> isn't the key to this "solution" a bridge? I mean afterall you are trying
> to join two seperate braodcast domains and the best way to do that is with
> a bridge, or am I missing something here?
>
> Thanks,
>
> Ron DuFresne
>
> On Mon, 12 Sep 2005, Derick Anderson wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: netfilter-bounces@lists.netfilter.org
> >> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of /dev/rob0
> >> Sent: Sunday, September 11, 2005 8:09 AM
> >> To: netfilter@lists.netfilter.org
> >> Subject: Re: NAT Helpers?
> >>
> >> On Saturday 2005-September-10 00:05, James Stickland wrote:
> >>> My problem with this network setup is that when the terminal server
> >>
> >> With WHAT network setup? I saw no information about a network.
> >>
> >>> attempts to join the domain, or do such things as browse all the
> >>> network shares (as opposed to typing in their ip address),
> >> it attempts
> >>> connections to the 10.10.10.7 broadcast address. The problem lies
> >>> within the router - it does not forward broadcasts.
> >>
> >> Why not? A broadcast is just another IP. This is sometimes
> >> true but not always true. It might depend on your rules. A
> >> clear explanation of the issue helps in finding a resolution.
> >
> > I actually tried once to get DHCP to broadcast across two subnets with
> > no success (I allowed the ports to be forwarded, didn't block 0.0.0.0 or
> > 255.255.255.255, etc.). Of course DHCP uses 0.0.0.0 and 255.255.255.255
> > so that may be a special case. But usually broadcast addresses are
> > defined within a subnet (like 10.0.0.255) and so I would think they
> > wouldn't be routed outside the subnet by design.
> >
> > Just my thoughts - or maybe I misunderstood this part of the issue.
> >
> > Derick Anderson
> >
> >
>
> - --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> admin & senior security consultant: sysinfo.com
> http://sysinfo.com
> Key fingerprint = 9401 4B13 B918 164C 647A E838 B2DF AFCC 94B0 6629
>
> ...We waste time looking for the perfect lover
> instead of creating the perfect love.
>
> -Tom Robbins <Still Life With Woodpecker>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFDJdVZst+vzJSwZikRAm4zAJwOTuX1VS9sHnhFCcqRI1zAhihAiQCgx26d
> mY5ZZ/8SmdnXRUJ+awLcPW4=
> =FBgM
> -----END PGP SIGNATURE-----
--
Frans Luteijn
PGP PblKey fprnt=C4 87 CE AF BC B6 98 C1 EF 42 A1 9A E2 C0 42 5B
GPG PblKey fprnt=ED20 0F25 C233 DC59 3FFA 170E D0BF 15F5 0BA6 1355
next prev parent reply other threads:[~2005-10-19 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 11:52 NAT Helpers? Derick Anderson
2005-09-12 19:21 ` R. DuFresne
2005-10-19 23:27 ` Frans Luteijn [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-10 5:05 James Stickland
2005-09-11 12:08 ` /dev/rob0
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=4356D669.A0B07AAF@knoware.nl \
--to=f.a.g.luteijn@knoware.nl \
--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.