Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: "'netfilter@lists.netfilter.org'" <netfilter@lists.netfilter.org>
Subject: Re: AW: bootp problems
Date: Wed, 7 Apr 2004 10:29:32 +0100	[thread overview]
Message-ID: <200404071029.32757.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <D3DD55FDB74AD511BA5100500416368053E843@ORION>

On Wednesday 07 April 2004 8:50 am, Jochen Vogel wrote:

> > > [DialIn]2.2.2.2----2.2.2.1[FW]1.1.1.1---1.1.1.2[DHCP]
> > >
> > > the DialIn tries to get an IP from the DHCP Server.
> >
> > You need a DHCP relay on the 2 network to do this.
> >
> > DHCP requests do not cross routers (they are ethernet broadcasts).
>
> Hi antony,
>
> The DialIN should play Relay
>
> FIRST the DialIn try it DIRECTLY to the DHCP Server
> with tcpdump on 2.1 i can see 0.0.0.0:68 > 1.1.1.2:67
> It doesnt work and i CANT see any entry in the iptables log

How is Linux supposed to route a reply packet from 1.1.1.2:67 back to 
0.0.0.0:68?

> SECOND the DialIn try it with BROADCAST
> with tcpdump on 2.1 i can see 0.0.0.0:68 > 255.255.255.255:67
> It doesnt work and i CAN see an entry in the iptables log

Broadcasts do not cross routers.   That is nothing to do with netfilter (and 
no, you cannot create any netfilter rules to make a broadcast cross to the 
other side).

Maybe your firewall needs to be a bridge?

Regards,

Antony.

-- 
Christmas was just an opportunity to upgrade to kernel 2.6 while no-one was 
around to notice the downtime.

                                                     Please reply to the list;
                                                           please don't CC me.



      reply	other threads:[~2004-04-07  9:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07  7:50 AW: bootp problems Jochen Vogel
2004-04-07  9:29 ` Antony Stone [this message]

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=200404071029.32757.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox