No connection with VLAN via OPT2 (Urgent)
-
Hello everyone, I have created an OPT2 interface with the VLAN-ID 33.
The settings are identical, rules, etc. correspond to OPT1 except for the IP circle.
A VM is used for testing; it works with VLAN22 but not with 33.
Does the firewall need to be restarted after creating the interface (OPT2)?
cheers
ron -
@jogovogo no you do not need to restart.. Does your vm get an IP from the new network? If your testing device is on a vm, you would have to make sure the vm host is setup correctly to pass the new network to your vm.
Is pfsense on the vm host as well?
-
@johnpoz said in No connection with VLAN via OPT2 (Urgent):
@jogovogo no you do not need to restart.. Does your vm get an IP from the new network? If your testing device is on a vm, you would have to make sure the vm host is setup correctly to pass the new network to your vm.
Is pfsense on the vm host as well?
It is now possible that an IP address is assigned from the VLAN, but there is no internet...
Do any rules still need to be entered?
-
@jogovogo I don't see any hits to any of those rules.. See the 0/0 under states - none of those rules have trigged not even once.
Can you ping pfsense opt2 IP from from your test device?
-
@jogovogo said in No connection with VLAN via OPT2 (Urgent):
Does the firewall need to be restarted after creating the interface
Unbound (DNS Resolver) probably does.
-
@SteveITS even if unbound wasn't listening on the interface after he created it.. If client tried to go to pfsense IP on opt2 for dns - the states would show that traffic. even if was 0/32bits or something..
I mean no dns could explain browser not working or something - but wouldn't you atleast try pinging say 8.8.8.8 or something to see if you had internet, or pinging pfsense IP on the opt2 interface.
-
Hi all!
Thank you for your quick answers!
It was connected to the PFBlocker NG; once it has been deactivated and reactivated, it works.
cheers!
