No leases in persistent database/No DHCP offers help

[Kammel78]

Hi,

Can't figure out quite what's going on. No issues for the past year, went on vacation, came back and I can't seem to get FreeNAS back on my network.

I keep getting:

No DHCPOFFERS received.
No working leases in persistent database - sleeping.

I've double checked that my DHCP server is running on my router and I've tried manually assigning my FreeNAS box an IP address, but when I try to ping the box, I get nothing.

What am I missing??

 

[anodos]

Try switching out network cables. Try switching NIC ports (if you have multiple NICs).

 

[jgreco]

DHCP is only going to be useful in an environment with a working network. If you cannot make it work with manual assignments, you need to ascertain why.

"tcpdump" is very useful for monitoring what the system is seeing. Log into the console and run it. Do you see traffic?

You basically need to take the usual network debugging steps. Assign your PC a static IP address. Assign the FreeNAS another IP address. Unplug them both and then directly plug them into each other with a known-good cable. From the PC, ping the FreeNAS host, while running tcpdump on the FreeNAS host. See something? Receiver's good. Ping the PC from the FreeNAS host. Run tcpdump on the PC. See something? Transmitter's good. And your PC should be able to ping the FreeNAS box (maybe not vice versa depending on firewall files). Etc.

 

[Kammel78]

DHCP is only going to be useful in an environment with a working network. If you cannot make it work with manual assignments, you need to ascertain why.

"tcpdump" is very useful for monitoring what the system is seeing. Log into the console and run it. Do you see traffic?

You basically need to take the usual network debugging steps. Assign your PC a static IP address. Assign the FreeNAS another IP address. Unplug them both and then directly plug them into each other with a known-good cable. From the PC, ping the FreeNAS host, while running tcpdump on the FreeNAS host. See something? Receiver's good. Ping the PC from the FreeNAS host. Run tcpdump on the PC. See something? Transmitter's good. And your PC should be able to ping the FreeNAS box (maybe not vice versa depending on firewall files). Etc.

Ok. Tried running tcpdump from the console and got

tcpdump: WARNING: usbus0: no IPv4 address assigned
tcpdump: unsupported data link type USB

 

[anodos]

That's odd. Use ifconfig to identify your NIC (ie "em0") and run "tcpdump -i em0"
If your NIC doesn't appear in ifconfig and its in an expansion slot (PCI or PCIe), try reseating it.

 

[Kammel78]

Ok. I got tcpdump to run using -i nfe01 (my NIC). Weird though, on the FreeNAS host I'm getting:

IP 169.254.158.186 which isn't even close to the static IP I used (192.168.1.120).

Couldn't get a ping either way.

 

[jgreco]

You failed to assign static IP addresses...

 

[Kammel78]

You failed to assign static IP addresses...

No, I assigned them. They show up in ifconfig as I assigned them.

I did NOT assign IPv6, though...

 

[jgreco]

So what device took up the IP address 169.254.158.186? Because you didn't correctly assign a static IP address on that device. <pendantry />

 

[anodos]

No, I assigned them. They show up in ifconfig as I assigned them.

I did NOT assign IPv6, though...

post ifconfig output

 

[Kammel78]

So what device took up the IP address 169.254.158.186? Because you didn't correctly assign a static IP address on that device. <pendantry />

This is what ifconfig tells me:

nfe0: flags=8943<UP, BROADCAST, RUNNING, PROMISC, SIMPLEX, MULTICAST> metric 0 mtu 15
00
options=c219b<RXCSUM, TXCSUM, VLAN_MTU, VLAN_HWTAGGING, VLAN_HWCSUM, TS04, WOL
_MAGICVLAN_HWTSO, LINKSTATE>
ether 00:1b:fc:e2:e2:62
inet 192.168.1.112 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (1000baseT <full-duplex,flowcontrol,rxpause,txpause>)
status: active
nfe1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=c219b<RXCSUM, TXCSUM, VLAN_MTU, VLAN_HWTAGGING, VLAN_HWCSUM, TS04, WOL_MAGIC, VLAN_HWTSO, LINKSTATE>
ether 00:1b:fc:e2:e5:43
media: Ethernet autoselect (none)
status: no carrier
lo0: flags=8049<UP, LOOPBACK, RUNNING, MULTICAST> metric 0 mtu 16384
options=3<RXCSUM, TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x5
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD, ACCEPT_RTADV>

 

[anodos]

Assign a proper static IP address for your client PC. Once you do that continue troubleshooting as jgreco wrote. Run "tcpdump -i nfe0" on your FreeNAS and ping from client.

 

[Kammel78]

Assign a proper static IP address for your client PC. Once you do that continue troubleshooting as jgreco wrote. Run "tcpdump -i nfe0" on your FreeNAS and ping from client.

Ok. When I ping 192.168.1.112 from the client I get:

ARP, Request who-has 192.168.1.112 tell 192.168.1.120, length 46
ARP, Reply 192.168.1.112 is-at 00:1b:fc:e2:e2:62 (oui Unkown), length 28

It repeats a few times and then

ARP, Request who-has 192.168.1.135 tell 192.168.1.120, length 46
IP6 fe80: :993c :90e9 :d5a8 :9eba.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
ARP, Request who-has 192.168.1.135 tell 192.168.1.120, lenght 46

and keeps repeating

On the client side, I just get:

Pinging 192.168.1.112 with 32 bytes of data:
Reply from 192.168.1.120: Destination host unreachable.
Reply from 192.168.1.120: Destination host unreachable.
Reply from 192.168.1.120: Destination host unreachable.
Reply from 192.168.1.120: Destination host unreachable.

Ping statistics for 192.168.1.112:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

 

[cyberjock]

Conflicting IP with another device on the network?

 

[Kammel78]

Conflicting IP with another device on the network?

No other devices with the same IP on the network.

 

[anodos]

To clarify: are you directly connecting the server and client via network cable or is this passing through a switch? Are you running jails? If so turn them off while testing. Have you tried replacing the network cable?

 

[gpsguy]

Buy a new NIC, perhaps the hamsters got tired of trying to keep the nvidia nic operational.

An OEM Intel Pro/1000 CT costs about $30 USD.

 

[jgreco]

I got bored when he failed to provide information and follow directions; debugging ethernet failures is usually child's play but you have to be kind of methodical about it. I don't really have the interest to try to reverse-engineer which instructions aren't being followed and tell him where his problem is. Clients pay me to do that sort of thing...

 

[Kammel78]

I got bored when he failed to provide information and follow directions; debugging ethernet failures is usually child's play but you have to be kind of methodical about it. I don't really have the interest to try to reverse-engineer which instructions aren't being followed and tell him where his problem is. Clients pay me to do that sort of thing...

Not sure which of my 7 posts throughout the day failed to provide the specific info you're looking for, but thanks for restoring my faith in humanity.

 

[Kammel78]

To clarify: are you directly connecting the server and client via network cable or is this passing through a switch? Are you running jails? If so turn them off while testing. Have you tried replacing the network cable?

For the purposes of troubleshooting, I connected the server directly to the client via a cable. I also replaced the cable with a known good cable.

I am running jails, so I'll turn them off.