Yes, I know! Another OPT1 and OPT2 no internet connection!
-
[2.7.1-RELEASE][admin@trakka.midge.home.arpa]/root: sockstat -4l | grep 'dhcpd'
dhcpd dhcpd 32156 13 udp4 *:48463So, no TCP?!
Unfortunately I cannot bring my network down now. There are important, to me, processes running, and the router is my perimeter firewall and router.. I will restart the router and pull the logs of boot, system general, firewall and dhcp a few minutes after a reboot. That will be in about 12 -13 hours from now.
The log are so long now and I can't quite remember at which times I made what changes. The only thing I can say is that they look normal.
-
DHCP is a UDP protocol, it shouldn't be listening for TCP.
But why yours is not listening on port 67 is very odd.
You shouldn't need to change the dhcp client settings on the hosts and in fact setting it to 'address only' is probably going to break stuff as they won't be passed dns or time servers etc.
Do you see leases in Status > DHCP Leases? Perhaps you have a rogue DHCP server somewhere else.
@MidGe48 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
the correct (I hope) network port
You need to know they are the correct ports because they may be the cause of all the problems here. Check with ifconfig as you connect or disconnect links.
Steve
-
@MidGe48 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
dhcpd dhcpd 32156 13 udp4 *:48463
As above : this explains everything.
A dhcpd server has to listen on port '67' - UDP.
Bacause DHCP clients will use that port '67' as their destination.Why your dhcpd uses port 48463 is .... never seen that before.
I've checked my dhcpd config file ( here /var/dhcpd/etc/dhcpd.conf ) and 'use port 67' command isn't even an option or mentioned, it the the de facto standard.
Looking at the GUI => Services > DHCP Server > LAN page, I couldn't even find a settings that permits me to change that.If dhcpd elected to use another port, like your 48463, it should at least mention this its log file.
Just restart it, and look the the DHCP logs
Don't worry to break your networks, they are already pretty 'down' any way.DHCP functionality is of course non mandatory, I can image that if you set up all network devices with a static IP, static gateway, and static DNS, and the network (/24) used, you don't any DHCP server to work.
-
Indeed I've never seen that before. Speculation but perhaps it uses a random port if 67 is in use? Maybe Kea was somehow still running?
I've switched back and forth between ISC and Kea many times and never managed to trigger anything like that but....I would restart the dhcpd service. Failing that reboot.
Steve
-
J jimp moved this topic from Problems Installing or Upgrading pfSense Software on
-
OK, I re-installed 4 times from the downloaded image.
I finally found out about one problem and got that fixed on the last and current install.
sockstat -l | grep ':53'
unbound unbound 4119 3 udp6 *:53 :
unbound unbound 4119 4 tcp6 *:53 :
unbound unbound 4119 5 udp4 *:53 :
unbound unbound 4119 6 tcp4 *:53 :sockstat -4l | grep ':67'
root kea-dhcp4 7840 19 udp4 10.10.10.1:67 :
root kea-dhcp4 7840 21 udp4 10.88.88.1:67 :
root kea-dhcp4 7840 23 udp4 10.44.44.1:67 :But, whereas everything works fine on LAN, OPT1 and OPT2 are still giving me some problems.
They both serve me via DHCP, the same subnet when they are different in the settings.
-
@MidGe48 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
They both serve me via DHCP, the same subnet when they are different in the settings.
You don't have your networks actually isolated then..
You can't just plug into the same dumb switch.
-
It is not a switch it is a pfSense router with different physical ports assigned to different interfaces, different DHCP servers and different subnets. So where in pfSense do I see/change the isolation??
-
@MidGe48 what do you have plugged into pfsense interfaces? Your saying you have a single device plugged into Opt1 and it gets an IP from dhcp on a lan or opt2 network?
What plugs into pfsense interfaces where you setup these networks and are running dhcp.. You can not just plug in lan, opt and opt2 into the same dumb switch.. And then plug a PC into one of the other ports.
-
I am well aware of what you say.
I have a relatively complex topology for my whole network including 3 routers and 4 switches. But what plugs in the ports of my perimeter router (pfsense) are physical networks totally isolated from each other. I don't know where you got the idea that I was converging things via a dumb switch.
Anyway, I am done for now, here.
I have other tasks awaiting and will use a workaround for the time being.
Thanks all.
-
@MidGe48 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
totally isolated from each other. I
Clearly they are not - because there is NO possible way for you to get a dhcp address from some other network that is on different layer 2 network.
Or your network is so complex you don't know what is plugged into where, and what you think is connected to opt1 is connected to lan or opt2 or whatever network you device is suppose to get dhcp from opt1 is on
-
@MidGe48 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
root kea-dhcp4 7840 19 udp4 10.10.10.1:67 :
root kea-dhcp4 7840 21 udp4 10.88.88.1:67 :
root kea-dhcp4 7840 23 udp4 10.44.44.1:67 :Looking far better.
One suggestion : stay away from 10.10.10.1/24, as that one is by default used by pfBlockerng.About these networks, they are set up with a /24 each, right ?
Like : my OPT1 called PORTAL :
and dhcp :
When I check my DHCP logs, I can see :
So, on the igc0 (my LAN) (network 192.168.1.1/24) and the 192.168.1.31 is served.
on the igc1 (my OPT1) (network 192.168.2.1/24) and the 192.168.2.6 is served. -
@MidGe48 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
I finally found out about one problem and got that fixed on the last and current install.
What was the problem? I'd love to know what could possible cause dhcpd to listen on a different port like that.
Steve
-
@stephenw10 said in Yes, I know! Another OPT1 and OPT2 no internet connection!:
what could possible cause dhcpd to listen on a different port like that.
Yeah - what would be the point, if dhcpd can not bind to 67, it should just fail with an error could not bind, etc.
Not like dhcpd could work if not listening on 67
