Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - LegendaryJello

#1
Thank you, the PC's Ethernet adapter was indeed the cause. I found in the adapter's advanced properties that there was a vlan ID configured and this was from when I was experimenting last week with the switch and didn't change it back to default. Thanks all for the support in working through this.
#2
When I try that, the PC picks up an APIPA address.
#3
Indeed, yes. In the simplified topology, I still cannot access the web gui and pings return destination host unreachable. When I perform a packet capture on the lan gateway, I am seeing a bunch of arp requests from the PC asking for the lan default gateway address but no replies. When I check the arp table on the PC I do not see the gateway. When I view the firewall log (option 10 from the console), nothing shows when I ping the gateway.
#4
It's the TP-Link TL-SG108E. It has default settings so only the default vlan is active which should pass untagged traffic. I didn't configure any vlans yet on OPNsense. Had a look at the rules.debug file and I'm not seeing anything apparent that would block traffic from lan. I see the block bogons and private IP rules which are commented out. I also see the 'default allow lan to any' rules are uncommented. Just to be sure, I reset OPNsense to factory defaults (option four) from console to rule out any issues with the fw rules.

Since earlier, I added another host which is a pi-hole and changed the IP scheme to a 10.0.100.0/24 network because I thought there may have been some conflict with addressing on a virtual interface on the PC but I still cannot access OPNsense web gui.

So now the network is configured with the modem going to OPNsense wan port and the lan port going to the switch where the PC and pi-hole are connected. All hosts are configured in the 10.0.100.0/24 network. From the PC I can access the switch only (pings successful and can get to the web gui) but cannot get to OPNsense or pi-hole (pings unsuccessful and cannot access web guis). From OPNsense, I can ping the switch, pi-hole, and the internet but cannot ping the PC. From pi-hole, I can ping the switch, OPNsense, and the internet but cannot ping the PC.

This is beginning to look like an issue with a configuration on the PC itself, perhaps?

Thanks for the continued help.
#5
Thanks for your reply. Everyone is configured with a /24 mask. I was researching if it is possible to see the mac table of the switch but I don't think it is. I also don't think it's possible to ping from the switch either. The most I can see is that both ports on the switch are enabled and are seeing traffic, no errors, and I can perform a cable test which both come back normal. I did the web gui reset via OPNsense shell (option eight from console) and that returned OK but it didn't resolve either issue. Is there somewhere I can go via the shell to check firewall rules?
#6
Hi I just installed OPNsense and am trying to access the web GUI for further configuration however I am receiving connection timeout. I tried both HTTP and HTTPS. Trying to ping the LAN gateway, I am receiving timeout and some destination unreachable responses. My current setup is modem to igc0, igc1 to switch, and switch to computer. Both interfaces have IPv4 and IPv6 addresses per information in console. The WAN interface was picked up via DHCP from ISP and the LAN interface is the default. Switch is 192.168.1.7 and computer is 192.168.1.20. I can ping the switch from both the computer and OPNsense. The arp table of the computer shows the IP addresses of both the switch and OPNsense which were both dynamically learned. I am a little lost what to do next. Does anyone have any other suggestions? Should I be checking firewall / nat rules next? Is there a way to do from console?