DHCPd / dhcrelay problems.

From: Phill Harvey-Smith (phill_at_dna.warwick.ac.uk)
Date: 05/27/04


Date: Thu, 27 May 2004 14:26:50 +0000 (UTC)

Hi,

I have setup the masquarade server that I detailed in my other post thus :-

                        eth1 eth0
Private network------------Masq box----------------Campus Network/internet
10.130.5.x 10.130.5.250-137.205.155.250

On our bit of the campus network I have two dhcp servers setup on
137.205.155.2 and .3 these have been working fine for several months serving
IP addresses to our normal non private net clients. What I want to be able
to do is use this server to configure the clients on the private network
too. To do this I configured the dhcp server with the settins of a machine
on the private network :-

ddns-update-style none;
authoritative;

shared-network bio {

        subnet 10.130.5.0 netmask 255.255.255.0
        {

                default-lease-time 86400;
                max-lease-time 86400;
                option subnet-mask 255.255.255.0;
                option broadcast-address 10.130.5.255;
                option routers 10.130.5.250;
                option domain-name-servers 137.205.155.2, 137.205.155.3;
                option domain-name "bio.warwick.ac.uk";
                option netbios-name-servers 137.205.155.2;
                option netbios-node-type 8;
                option slp-directory-agent true 137.205.153.247;
                option nds-tree-name "BIOSCIENCE_TREE";

                host stores-laptop-10-130-5-10 {
                        hardware ethernet 00:10:4B:F7:B4:1E;
                        fixed-address 10.130.5.10;}

        }

}

I have also installed dhcrelay on the masquarade box, with the following
settings :-

            dhcrelay -i eth0 -i eth1 -a protein.bio.warwick.ac.uk

I ran dhcrelay with the -d flag so that I could view the debugging output,
it is definatly receiving and forwarding the dhcpdescover packet, the dhcp
server is recieving this forwarded packet and is trying to correctly hand
out the correct IP address. However instead of forwarding it back to the
dhcrelay machine it is trying to send it via the gateway address for the
private network (10.130.5.250). Is there any way to prevent this behavior,
and make the server send the reply back via the relay machine.

Thanks.

Phill.



Relevant Pages

  • Re: Fully parallel Scheme-based language w/ evaluator
    ... Windows Server 2003 and networks in simple - and irreverent - terms. ... If networking really is a big deal, ... Concepts and Terminology in Part I, and The Design and Deployment of Network ...
    (comp.lang.misc)
  • Re: Outgoing POP3 email missing/lost/not received
    ... Funny thing is that I have had this ISP for 8 years and it has always been ... It looks like when you last ran CEICW, you set the ISP's mail server to: ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.dns)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.networking)
  • Re: Logon Server Unavailable
    ... There are currently no logon servers available to service ... You use a office laptop to connect the office VPN, when you map a network ... you may receive this message: "This account is the ... The server is not configured for transactions"> "A domain controller for your domain could not be contacted" ...
    (microsoft.public.windows.server.general)

Loading