Oct 26 2005 c. 20:42 Graham Toal wrote: > I wanted to set up a system which has two ether cards (it's part of > a transparent bridge so it'll be inline with someone's connection) > such that it'll pick up a DHCP address on *both* cards ... the > trick comes from not knowing in advance whether the DHCP server > will be on the inside connection or the net-facing one. (i.e. if > the bridge is deployed near the network edge, the DHCP server is > inside; but if it is deployed immediately in front of a single > server, then it will see DHCP facing outwards). > > It *ought* to be possible to configure both hostname.xl0 and > hostname.fxp1 as dhcp, and whichever one comes up first, will then > bridge through the DHCP server for the other. Unfortunately it > just happens by luck of alphabetical order, that the one which > comes up first is *not* looking at a DHCP server. So after a > relatively short period of retries it goes to sleep. Then the > other interface asks for its dhcp address and gets it quickly. > What I expected was that the first would sleep for a short time > then ask again, and get it OK. I haven't seen that happen - about > 30 minutes later and the interface still has no IP. > > What's the best way to ensure that they both get IPs as quickly as > possible? I can think of some dirty hacks, but I don't like the > solutions I've come up with. (For example, if I kick off the dhcp > client requests in the background, that interferes with the rest of > the boot sequence). > > Has anyone had this configuration before and come up with an > elegant solution?
May be I'm wrong (only one OBSD box with two NICs with different networks attached I heve this time is production box and cannot be switched off now), but maybe this helps: 1) Disable sysctl net.inet.ip.forwarding in sysctl.conf Then, in rc.local: 2) Initialize network manually (call dhclient) 3) Enable forwarding 4) Configure and wake up bridge IMHO, this'll look like static IP address given to bridge interfaces... -- With my best, Pereresus ne Vlezaet Buggy