I fixed my problem. I downloaded the newest source code and compiled it and ran DHCRELAY -i eth1 -i eth2 192.168.1.70 and now it is working. Thanks for all of the help. ----- Original Message ----- From: "Antony Stone" <Antony@Soft-Solutions.co.uk> To: <netfilter@lists.netfilter.org> Sent: Tuesday, October 29, 2002 7:41 PM Subject: Re: DHCRELAY through IPTABLES Firewall > On Wednesday 30 October 2002 12:30 am, bigman@monster-solutions.net wrote: > > > when I run DHCRELAY -i eth2 it tells me that it is listening on eth2 and > > sending on eth2. I assume this is wrong? > > Sounds wrong to me. Sounds kinda pointless to me. If you wanted the > requests to go out on the same network they came in on, you wouldn't need a > relay.... > > > how do I fix it? is it my routing table? > > Could be - what does your routing table say ? > > My copy of "man dhcrelay" says: > > dhcrelay [ -p port ] [ -d ] [ -q ] [ -i if0 [ ... -i ifN ] ] server0 > [ ...serverN ] > > The DHCP Relay Agent listens for DHCP requests on all interfaces attached to > a host, unless one or more interfaces are specified on the command line > with the -i flag. > > When a query is received, dhcrelay forwards it to the list of DHCP servers > specified on the command line. When a reply is received, it is broadcast or > unicast on the network from whence the original request came. > > Therefore I think your command should be: > > dhcrelay -i eth2 192.168.1.70 > > If this sends packets to 192.168.1.70 out of eth2, try pinging 192.168.1.70 > and see where the packets come out of then. > > Antony. > > -- > > In science, one tries to tell people > in such a way as to be understood by everyone > something that no-one ever knew before. > > In poetry, it is the exact opposite. > > - Paul Dirac >
