Setting up new device on LAN
-
No way to see it on the ISP router.
-
@johnpoz @stephenw10
4.1 is not ISP, it's my private device and it has 4.244's correct MAC in its ARP table. All devices had multiple reboots to clear any caches. -
@stephenw10 said in Setting up new device on LAN:
No way to see it on the ISP router.
You sure he stated
" Plus the 4.1 device shows 4.244's MAC in its own ARP table."
You validated this pfsense actual mac for its wan interface?
Change the interface on pfsense so you get a different mac, or clone the mac to something.. But again there is no way your going to talk to 4.1 if pfsense has no mac.
try setting a static mac for 4.1 on pfsense if your saying 4.1 has the mac address of pfsense.
But you got something crazy going on if your saying pfsense arps for 100 and all work fine, but 4.1 has the mac of pfsense but pfsense doesn't have the mac for 4.1.. You see pfsense send out arp for 4.1 but you do not get an answer?
edit:
Can you post the mac address of both your 4.1 device and pfsense interface your connecting.. There is zero reason to hide the mac.. but if you want you can leave off the last 3... Just curious if a multicast mac.. I had a device one time that was like a bridge for a current cost device that measured power usage for whole house. And it had some oddness - they had used a multicast mac on it... Which can cause some weirdness.. -
You can see it here: https://forum.netgate.com/post/1041334
Seems fine.My mistake on the ISP router. What exactly in the router at 4.1 then?
-
@stephenw10 yeah that mac is not multicast - but what is the mac of this 4.1 device?
This should be simple enough to figure out..
Sniff on both devices - arp from 4.1 for 4.244 or 4.99 whatever pfsense IP is.. Now arp from pfsense for 4.1
Do the other devices see the arp from the other device, do they respond or not.. If they respond is the other device actually seeing it in the sniff?
If device is not reply to the arp, or not sending it out the right interface - then there is something wrong with that device..
But not see a mac for 4.1 in your arp table - you are not going to be able to talk to 4.1 that is for damn sure.. You could see if setting static arp in pfsense for 4.1 allows communication - but that wouldn't be an actual fix, that would be just a work around. Understanding why the normal arp function is not working would be the fix, something is odd for damn sure..
if just a dumb switch.. there really is nothing it could be doing.. It would have an arp cache that is how it knows what mac is on what switch port... But that shouldn't really last that long, have you rebooted the switch? And you have moved pfsense to different port on the switch?
-
@johnpoz @stephenw10
I want to give you guys props for being so active in trying to help me with this. This was a very weird problem that was making me doubt myself. I finally gave up and reflashed. Now it works fine, so it must have been some odd setting I changed somewhere but it was escaping me. The reflash also resolved the login and save delays of almost two minutes every time. -
@peterlecki said in Setting up new device on LAN:
I finally gave up and reflashed.
Reflashed what? Your 4.1 device? You did a clean install of pfsense? Not sure I would call that a flash? Flash is something you do to bios or firmware.. Installing pfsense clean is not something I would consider a "flash"
Redoing say dd-wrt firmware on some soho router is a flash ;)
Glad you got it sorted.. But now we will never actually know what was going on..
-
Glad normal reality was resumed.
Weird though. I can't think of anything that would have caused that.
Steve
-
@johnpoz
My bad, I reinstalled pfSense.
