Messages

1

General Discussion / Device connected but doesnt show anywhere (no lease?)

« on: August 19, 2024, 06:10:33 pm »

So I have a device that is taking bandwidth, not much but it is active. It shows under reporting/traffic as device 10.1.3.251

I have vlan'd subnets: 10.1.1.* as the LAN, 10.1.2.*, 10.1.3.* and 10.1.4.* are vlans on a separate port on my opnsense device.

Now for the subnet "3" which is my business private network (2 is for IoT and 4 is for guests), most devices are hard mapped (dhcp ranges *.100 to *.199) and .10 to .99 are the dynamic dhcp leases if needed. What I dont understand is when I go to leases, I dont see anything that is 10.1.3.251, and I looked out on every physical device I know, and none have this IP... Also it cant be an outsider connecting to the network as I have setup a password that would take 12 years to decrypt... something like that.

How can I know which device is this ghostly 251 ? I cant have its Mac address or anything and it's taking bandwidth every 10 seconds to every minute (variable).

Thanks...

Running version 23.1.11_2 amd64 of OPNsense (if it could be version related issue?)

2

General Discussion / VLANS: Tagged and untagged ports. Yes, again. (resolved)

« on: October 26, 2023, 12:14:40 am »

Hi everyone,

Second post on here and first time setting things up this way for me, so (again) please bear with me.

Here is a summary of my networks physical connections with vlans setup:

Protectli device:
WAN/igb0: to ISP Gateway (bridged)
LAN/igb1: Connected to a single computer for setting up the FW appliance
igb2 & igb3: hold Lagg0 to 8-port managed switch 1. (I followed a youtuber (homenetworkguy) and found his idea of putting all vlans on a lagg is a clever idea.)

Switch 1:
- port1: to lagg0 / igb2 *
- p2: to lagg0 / igb3 *
- p3: tagged "10, 20, 99" to switch 2
- p4: untagged 10 to wifi AP
- p5-p8: untagged 30 to IoT

Switch 2:
- p1: tagged "10, 20, 99" (to switch 1) **
- p2: untagged 10 to wifi AP
- p3: untagged 20
- p4: untagged 99
- p5-p8 not in use

I know. Two switches daisy chained... Not the best.
But believe me, it's the best in my case. I got 2 places where the tech stuff is, and the two places are separated by like 60 ft. And no, it's not realistic nor possible nor desirable to "move" any of those two physical places to the other.
That being said, I wonder about vlans as its my first time with this stuff...

* First question: Should these 2 ports on switch 1 be tagged with all my vlans to go through? Is that considered trunk?
** Second question: Should this port also be tagged?

I kinda figured out that any port going to a single host will be untagged and ports going to another switch/router/etc will be tagged, but is it the case in both ways for tagged ports (ie both my switches)?
I'm confused as I'm not sure if I should see the network as directional or not... if it makes sense.

Thanks for the help out there

3

General Discussion / Re: Does it not route? (can't acces webGUI via LAN)

« on: October 25, 2023, 02:01:17 pm »

is the old router still in place when you're connected via the switch? That would still hand out IPs via DHCP while nobody does it on a direct link.

and

I would check that DHCP is enabled and configured for your LAN in OPNsense.  From there, plug your machine directly into the LAN port and confirm that you get an IP address from OPNsense.  At that point, you should be able to get to the webui on the gateway IP; likely http://x.x.x.1.

No, basically I unplug the device from the network, unplug my "main" computer (which is configured to receive an IP via DHCP without arguing), and plug only the computer to the LAN port of device. On my computer, it receives an IP, then I can see the device's IP as the gateway, but I cannot access it via web browser, I cant ping it either from console. It says something like network is down.

Or other issue: Is LAN already mapped to a VLAN or to the plain interface in OPNsense?

Plain interface, I have 4 ports, the other two ports are a LAGG where all the vlans reside.

**EDIT**: I finally went the painful route to re-do everything again, I'm not even sure what I did wrong, I sure did something to lock myself out... Now everything works out fine. Note to myself: Make more backups, especially when I feel confident.

4

General Discussion / Does it not route? (can't acces webGUI via LAN)

« on: October 24, 2023, 05:08:43 pm »

Hi everyone,
I'm pretty new to this stuff and no solid background in IT except experience and general geekiness, so please bear with me.

So here's the CONTEXT:
I want to reinforce my network security against mostly IoT and guests. My network serves my house (where the IoT is mostly) and my business (where I want to offer free and easy wifi access to guests). The core network where I have my computers, business related hardware such as my point of sale etc. will be its own vlan for the purpose. Knowing that OPNsense was the way to go, I bought myself a protectli device (will now refer to it as "the DEVICE"), reassigned wan/lan properly, set up some vlans, etc. following the homenetworkguy's instructions on youtube. My plan is to setup everything, then remove my old underpowered router and replace it with my new badboy.

Here's the PROBLEM:
I cannot access my device when not connected to another router.
While doing initial setup, I had connected the device from LAN port to a port on my small managed switch (which is not configured for vlans yet). I had assigned xxx.xxx.xxx.2 to the LAN port and could access it from my computer which is wired to the same switch (which itself is wired to my router). Now, whenever I unplug the device from switch, and plug my computer directly into the LAN port, I cannot access my device at all!

Is there anything I missed? Should the device be put in another "mode" when unplugging from the already routed switch, so it becomes a "router" itself? Does it not route? I'm pretty confused as to what I'm missing here.

BTW i already put all the FW rules that were mandatory as explained by the youtuber mentioned above for LAN.

Thanks for any help!