Hi Steve,
I've interspersed my comments, but first a preface:
I've never used (although read a bit on) DHCP.
I use Debian (looking at switching to BSD).
I run old hardware boxes so can troubleshoot.
I'm not expecting this to be a definitive answer but I hope its more
help than noise.
Doug.
On Tue, Apr 03, 2007 at 02:21:07PM -0700, [EMAIL PROTECTED] wrote:
> Covad DSL Modem -->[ne3] firewall [xl0] --> switch --> internal network
>
> firewall = PII/256MB running Open BSD 3.5 with 2 NICs
> ne3 = external interface configured using DHCP (192.168.1.1)
> xl0 = internal interface fixed internal network (192.168.0.0/24)
>
> Nobody on the internal network can get out to check email or surf the net.
> Something happended in the hours between Sunday night around 8:30 pm and
> Monday morning at 8:00 am. But what?
>
> Network Cards - substituted known good network cards in firewall - no change.
Where they the same kind (same drivers, or did you change
/etc/hostname.* to match?
>
> Firewall PC - rebooted; then substituted known good backup firewall machine
> no change.
>
Does the modem (never used one) remember hardware ethernet address so
get confused when a different box requests the same stuff? Did you
reset the modem each time you changed boxes or NICs?
Since you know the x10 NIC (internal interface) works, what happens if
you swap them in your configuration? If the ne3 is now internal, does
it work?
In other words, first ensure that you have two NICs funtioning in all
respects.
> ping - I can ping from internal network to the internal interface on the
> firewall. I can SSH into the firewall from the internal network.
>
What happens if you log into the firewall via the console (not ssh)?
> DHCPACK from 192.168.1.1
> New Network Number: 66.166.238.0
> New Broadcast Address: 66.166.238.255
> bound to 66.166.238.189 -- renewal in 30 seconds.
^^^^^^^^^^^
>
> It seems to get the IP address from the COVAD DHCP server but then things go
> haywire. Within a few seconds I start seeing error messages on the console:
>
> Apr 2 14:54:18 gateway dhclient: send_fallback: No route to host
> Apr 2 14:54:18 gateway dhclient: send_fallback: No route to host
>
> #ifconfig ne3
> inet 66.166.238.189 netmask 0xffffff00 broadcast 66.166.238.255
>
> which seems to be correct. But running ifconfig a few times eventually it
> appears to lose the correct IP address and go down:
>
> ifconfig ne3
> inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
>
> interface assignments
> ----------------------
> /etc/hostname.ne3
> dhcp
>
> /etc/hostname.xl0
> inet 192.168.0.1 255.255.255.0 NONE
>
> /etc/sysctl.conf
> net.inet.ip.forwarding=1
> net.inet6.ip6.forwarding=1
> Hardware?
> ----------
> dmesg
> gateway# dmesg
> OpenBSD 3.5 (GENERIC) #1: Sat May 1 08:18:25 PDT 2004
> .
> xl0 at pci0 dev 14 function 0 "3Com 3c905B 100Base-TX" rev 0x30:
> irq 11 address 00:50:da:4f:e1:10
> exphy0 at xl0 phy 24: 3Com internal media interface
> ne3 at pci0 dev 16 function 0 "Winbond Linksys EtherPCI II" rev 0x00: irq 9
> ne3: address 00:20:78:14:f5:ed
