thank you
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 MenuQuote from: shymega on September 18, 2021, 08:45:03 PM
I did a Hyper-V update when I first installed the server, to keep up to date. Wondering if that has something to do with it... I'm using the standalone Hyper-V Server from Microsoft.
Quote from: syndac on December 31, 2019, 08:32:03 PM
I want to separate my network devices into two networks: one for my regular devices (LAN) and one for devices that really have no business on the LAN (ISO). I'd also like any guests connecting to the network to be DHCP'd onto the ISO network. I have wired and wireless connections for both device categories. For example:
Desktop: wired (LAN)
Phone: wireless (LAN)
TV: wired (ISO)
Alexa: wireless (ISO)
Guests: wireless (ISO)
LAN: 192.168.1.0/24
ISO: 192.168.2.0/24
I'm having trouble wrapping my head around how to set up VLANs and bridging to make this possible. So far, I've tried:
1. Connect AP and wired devices to switch
2. Connect switch to firewall port 1
3. Create VLAN off port 1
4. Static-assign all IPs as necessary between the networks
5. Turn DHCP off of LAN and on for ISO
The issue that I run into is that anything that comes onto the network later ends up getting an address on the LAN network (192.168.1.x) instead of the ISO network as intended. Additionally, even though devices are statically assigned IP address on the ISO network, the devices--themselves--show that their IP address is on the LAN network (for some devices, this causes connection issues).
I'm not sure what's causing this. Am I going about this the wrong way?
Quote from: kagbasi-wgsdac on August 26, 2019, 11:26:40 AM
Thanks, I will definitely go through the official documentation that you've pointed me to.
The problem I'm running into, though, is not the setup of the Guest Network per-say. But rather, the VLAN. It seems after I create the VLAN and assign it to a physical interface then create a DHCP pool on it, for some strange reason, the inbound DHCP Request (i.e., 0.0.0.0:68) is getting blocked by the "Default Deny All" policy. I've done everything I know to do but can't seem to get past this - I must be missing something.
Quote from: franco on January 31, 2019, 11:18:19 AM
Just install the snort vrt plugin again and you'll be more happy.
Cheers,
Franco
Quote from: Monocle on January 22, 2019, 09:51:29 AM
Anyone?
Quote from: bmail on November 28, 2018, 12:08:20 PM
Hello,
Could someone explain to me the difference between the type "URL (IPs)" and "URL Table (IPs)" when creating a new alias for the firewall ?
thanks a lot !
Have a good day.
Quote from: walkerx on November 29, 2018, 10:42:30 AMQuote from: Ren on November 28, 2018, 11:01:53 PMwhat would the need be for the custom options to be set?
If you are using unbond DNS remember to set custom options