Messages

Yes - 3852.

If push comes to shove, I'll have to locate my USB/Serial adapter...


Edit: the brand new cable I bought earlier today was the culprit.  Replaced it with another and it's coming up properly now.

I received a new Opnsense device a couple weeks ago and finally had some time to start working with it.  The Quick Start instructions tell me port 0 is configured for the LAN, with DHCP service running on it. 

I've plugged my computer - a Mac Studio - into that port, set for DHCP and it doesn't establish a lease, instead generating a useless self-assigned IP.  Just in case of a configuration error or instruction error, I also connected to port 1 which is supposed to be the WAN port.  No joy on that.

If I manually configure the computer to 192.168.1.10, which is outside the range of the DHCP service, my computer shows that it's connected but when I try to connect via the web interface, it times out.  Even pinging 192.168.1.1 fails (though that could be a default rule being enforced.)

I haven't connected the WAN cable yet because I'm on a static IP, so my plan was to set up those parameters once accessing the web interface, and continuing with the rest of the process.

At this point I have no ethernet access to the firewall.  Any suggestions?

I am about to be new to the ecosystem - I have a DEC3852 sitting in a box here at my home.  Does that purchase benefit the same developers to whom we're discussing donating in this thread, or are the businesses separate?