Reaction score: 95
hostname="myserver.host.com" zfs_enable="YES" powerd_enable="NO" powerdxx_enable="YES" powerdxx_flags="-n adaptive -a hiadaptive -b adaptive -m 800 -M 1600" rc_fast="YES" rc_info="NO" rc_startmsgs="NO" devfs_system_ruleset="system" autoboot="YES" background_dhclient="YES" defaultroute_delay="0" ifconfig_re0="DHCP" ifconfig_re0_ipv6="inet6 accept_rtadv" sshd_enable="YES" moused_enable="YES" ntpd_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="NO" firewall_enable="YES" firewall_type="workstation" firewall_logging="YES" firewall_quiet="YES" cupsd_enable="YES" dbus_enable="YES" hald_enable="YES" sddm_enable="YES"
ifconfig_re0="inet 192.168.0.25 netmask 255.255.255.0" defaultrouter="192.168.0.1"
Reaction score: 7,372
Old leases are kept around in case the DHCP server is unavailable when dhclient is first invoked (generally during the initial system boot process). In that event, old leases from the dhclient.leases.IFNAME file which have not yet expired are tested, and if they are determined to be valid, they are used until either they expire or the DHCP server becomes available. A mobile host which may sometimes need to access a network on which no DHCP server exists may be preloaded with a lease for a fixed address on that network. When all attempts to contact a DHCP server have failed, dhclient will try to validate the static lease, and if it succeeds, it will use that lease until it is restarted.
service dhclient restart re0.
Your login actually has nothing to do with it.I'm still somewhat new to BSD and I wouldn't know about environment variables set by the login script.
There is no magic, I already explained above: when you have your switch connected to the PC, the OS detects physical connection and tries to get an IP address by sending DHCP requests. After timeout it doesn't try anymore since the status of physical connection doesn't change. When your modem is connected to the PC and it's off, there is no actual physical connection (no carrier), the DHCP client doesn't even try sending anything out. When the modem is up, the OS detects carrier and starts DHCP communication.I have no problems using DHCP ... if the modem is plugged directly into the motherboard's Ethernet connector. ... Not sure if there is a conflict with LinkSys.
$ ifconfig: re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE> ether e0:d5:5e:d0:b9:c2 inet6 fe80::e2d5:5eff:fed0:b9c2%re0 prefixlen 64 scopeid 0x1 inet 192.168.1.47 netmask 0xffffff00 broadcast 255.255.255.255 media: Ethernet autoselect (100baseTX <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6> inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 groups: lo nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> $ netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 192.168.1.1 UGS re0 127.0.0.1 link#2 UH lo0 192.168.1.0/24 link#1 U re0 192.168.1.47 link#1 UHS lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 ::1 link#2 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRS lo0 fe80::/10 ::1 UGRS lo0 fe80::%re0/64 link#1 U re0 fe80::e2d5:5eff:fed0:b9c2%re0 link#1 UHS lo0 fe80::%lo0/64 link#2 U lo0 fe80::1%lo0 link#2 UHS lo0 ff02::/16 ::1 UGRS lo0 [code] In my [file]rc.conf[/file] I had: [code] ifconfig_re0="inet 192.168.1.47 netmask 255.255.255.0" defaultrouter="192.168.1.1"