can my topics be moved to
26.7 Series section
i just noticed i posting in the wrong section
i have a vm of opnsense
and 2 virtual nics
only way i can access it is both LAN and WAN set to DHCP
on the WAN if i set it to my LAN network i can get an ip address of 192.168.0.x but i cant access through the WAN only through the LAN
on WAN interface i disabled the both Bogon and Block private networks
in firewall rules under WAN i set WAN to any for all of it to open it all up
and once i change my LAN network like 192.168.5.1/24 to static so its not my network
so it forces only access through the WAN
i can not access through the WAN
but once in the console i reset the LAN to dhcp mode and get a regular ip off the network im able to access opnsense gui
is there some other setting that is blocking access to opnsense from then WAN side
as my firewall rule is in the pic.. even tried gateway DHCP_192.168.0.1 doesnt help
so in the pics you see if i set it to static for the LAN network i can not access from the WAN side
Ensure that WAN and LAN are not connected to the same network segment.
Go into the console and disable the Firewall:
pfctl -d
If you have access then, it's just the firewall rules, but routing should be fine.
@viragomann not sure how to disable the firewall
and ya the both lan and wan are on 2 different subnets
but if i change LAN to like 192.168.5.1 i loose access and cant acess the wan ip but i can access the WAn ip when the lAN network is reachable like 192.168.0.x
and that pfctl is disabled
so in the pic you will see i set up the 192.168.0.150 for wan
and its accessable
but once i change the LAN from a vlan i dont have like 192.168.5.1 then my local lan cant reach 192.168.0.150 on the wan.. so its still blocked
so here in this pic i changed the LAN ip to 192.168.5.1/24 in the gui and applied changes and i no longer have access to the gui through 192.168.0.150
Quote from: comet424 on Today at 05:08:38 PMbut once i change the LAN from a vlan i dont have like 192.168.5.1 then my local lan cant reach 192.168.0.150 on the wan.. so its still blocked
This let me suspect, that you access the WAN IP through the LAN interface.
Ensure that your computer is connected to the WAN network.
When the firewall is disabled try to ping the OPNsense WAN. If it doesn't work, check if the IP is in your ARP table.
Also ensure that access isn't blocked by Proxmox?
my local network is 192.168.0.x so my pfsense router is 192.168.0.1
and i running Unraid Server running Open as a VM and 2 virtual nics both in the gui are setup as DHCP
so thats why i got 192.168.0.150 from pfsense for WAN (which is my Lan) and i got 192.168.40.50 which is my DMZ vlan coming from pfsense
so i can ping 192.168.0.150 from my desktop PC that i access the gui from.. i can pig 150 from shell in opnsense
i cant ping 150 from pfsense box...
and the desktop pc and the unraid server are both on the same 10gig fiber switch.. where pfsense is upstream from that
and i cant access the gui
sorry my dyslexia
my desktop PC cant ping it it i get 192.168.0.1
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
sorry for that ugh i hate dyslexia i read it wrong
frustrating i cant post pics really its over the limit so i trying best with these screen shots to limit them
Quote from: comet424 on Today at 05:28:55 PMmy desktop PC cant ping it it i get 192.168.0.1
So I'm wondering, why your router replies to the ping.
Are your network settings on your PC correctly? Check the mask, if it's manually set.
Is the IP in your ARP table??
You will also have to check Firewall:
Settings: Advanced > Disable reply-to. But disabling the firewall should disable this as well.
ya shes in the arp table of pfsense
as for the desktop ya like its dhcp address
so its
192.168.0.49
192.168.0.1
255.255.255.0
i tried a
ipconfig /flushdns
but still get
Pinging 192.168.0.150 with 32 bytes of data:
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
Reply from 192.168.0.1: TTL expired in transit.
and cant ping from pfsense either still 100% packet loss
in about 500 seconds i going to see if the lease renews
so the arp expired and disappeared it.. but then like 10 seconds later it renewed it 1180 seconds for 192.168.0.150
the dchp leases showed it was down but then its back up again
and from the opensense shell
i can ping 192.168.0.150 opsense
i can ping 192.168.0.1 pfsense
i can ping 192.168.0.49 my desktop
i cant ping google.ca or 1.1.1.1 i get
no route to host
maybe opnsense just doesnt like vms
and its blocking it all.. once i change the LAN to dhcp back i can now access the gui but not the wan ip gui.. weird
i guess i need to try take one of my desktop pcs and install opensense on it and then plug a laptop in the desktop pc and plug the lan in the wan of the desktop so it least has internet i doing this to try to transition over from pfsense but i having multiple issues like the gui... the vpn, pia vpn, Trust/Authorities this transition is going badly at the moment
so maybe i need a physical computer and skip trying to go through the WAN as it would be easier but i frustrated... or i have to go through the LAN but i didnt wanna as i didnt want it conflicting with my current pfsense.. sure not a smooth transisiton thats for sure
its sure a learning experience
I recently installed two OPNsense instances in a public cloud. It's KVM-based.
The VM had only a single network interface, and this was connected to the internet.
I just allowed access from my IP in the SG, went into the console and disabled the firewall. Then got access to the GUI and did all the settings.
I've no idea, why this shouldn't work in your case.
If your WAN is an Ethernet (broadcast network) and you are trying to access OPNsense from a system connected to that same network, did you disable reply-to?
i have no idea what that is? i only started opense yesterday as i trying to transition from pfsense to opensense incase they can the CE version
and what was all above was Vitual Cards
so now i found a computer to use
i shoved a Dual Intel 1Gb nic in
if i plug into the LAN i get 192.168.0.152 and i can access the gui
if i plug into the WAN port i get 192.168.0.156 and i can not access the gui
ill have to look up what a reply-to is
Quote from: comet424 on Today at 07:44:23 PMill have to look up what a reply-to is
In mentioned it in #7.
I think, I'm out here...
ah ok
ya its still checked
and under Firewall Nat
is Source NAT the same as Port Forward?
as there is no + option to say open a port 80 under Source NAT
Destination NAT is port forward. Source NAT is just regular outbound masquerading.
ok so Source NAT is Outbound NAT then
so then this should open up the thing
well that didnt work i can not port forward through the darn wan connection ugh... so much headache to just simply open up port 80 to access the gui