(SOLVED)no dhcp on the lan !!!

Konstanti

Check whether the DHCP service is running or not
/status/services

and
check if the pf receives a dhcp request and responds to it
from cli
tcpdump -nettti em1 "udp and (port 67 or port 68)"

ethertype IPv4 (0x0800), length 364: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:be:3b:be:df:59, length 322
,ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.42.68: BOOTP/DHCP, Reply, length 300
ethertype IPv4 (0x0800), length 364: 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:be:3b:be:df:59, length 322
ethertype IPv4 (0x0800), length 342: 192.168.1.1.67 > 192.168.1.42.68: BOOTP/DHCP, Reply, length 300

major501

service dhcp is launch
alt text

sorry I entered the order but nothing is displayed !!
alt text

Konstanti

@major501
if you manually assign the ubuntu server ip address with the default gateway 192.168.12.1, will it be able to ping 192.168.12.1 ? for example, 192.168.12.2

major501

https://i.imgur.com/hBoz6zu.png
i want to automatic assign ip with pfsense

johnpoz

Well it shows dhcp server running... So if your client is not getting dhcp - more than likely its not on the correct network via your VM setup..

Does the dhcp service pfsense show any discover in the logs? Does it show its trying to had out an offer?

The point of setting static on the machines was to actually validate you have connectivity to pfsense where the dhcp server is running.

Konstanti

@major501

show the output of the command ifconfig -m
the picture shows
that interface em1 is down

major501

I do not understand why the wan has a dhcp despite all my setting I would like the dhcp on the lan
alt text

here is the output of the command ifconfig -m em1
alt text

johnpoz

Your EM1 is not up - status = NO CARRIER. kind of hard for anything to talk to it when its not online. Or get a dhcp from it.

Did you setup your VM settings to enable that nic on power up?

major501

thank you for your answer i rule my problem with virtualbox i can make internet networks and on the configuration panel the 2 cards are in green c is vmware-workstation which refuses to connect the card to the internal lan

johnpoz

Not sure what your issue is, but I have run pfsense on pretty much every VM solution out there and not had any issues. VirtualBox, Vmware Workstation, Vmware sphere/esxi, Hyper-V, etc.

All I can tell you if pfsense doesn't see the interface up - then no its not going to be able to do anything with that nic.

major501

it is a problem with vmware i am on fedora and vmware do not want to connect my network cards in lan internet but with virtualbox i optiend my ip address automatically

major501

johnpoz

And what does the log say? Did you actually enable the nic to be on in vmware? It looks like you have it enabled in your previous pic.. So what does the log say?

Lets see your lan segments tab.. Did you configure those - do you have any other vms on this lan segment? Did you actually create a lan segment for vms to connect to? What version of workstation are you running?

major501

i reinstall vmware workstation and now all work i can ping on internet Lan segment
alt text