Search results

i have a 2724 feeding a pfsense interface with multiple vlans. the switch port wired to pfsense is 'T'agged on the VLAN Membship for each of the vlans to trunk to pfsense. this is the tricky part that I was stuck on, under Port Settings, for the switch port wired to pfsense, i had to give it a...

yup same here. although an OEM part, $35 IBM br10i :)

bad news. my SuperMicro X9SCM-F shows a single onboard SATA controller under Configuration > Advanced Settings > Edit... (where you mark devices for passthrough) for me it reads as 00:1f.2 | Intel Cougar Point 6 port SATA AHCI Controller every other line is accounted for in terms of hardware...

that is a great question that I don't have an immediate answer to. let me do some sleuthing over lunch.

absolutely. i said "you need at least 2 controllers" which certainly can include the onboard controller. and later even said so that should sum that up.

hyper-v offers physical disk passthrough; http://www.servethehome.com/hyperv-disk-passthrough-quick-guide/. thats what confused me at first. i read about that first and then saw passthrough in ESXi and assumed it was the same. sounds like you have a good plan!

danswartz and i have both similar builds (i went the X9SCM-F route though) and similar [H] browsing/reply schedules :D

unfortunately ESXi cannot passthrough a single disk directly to a VM. what you can do is pass a whole (supported) controller through to a VM. in the case of your onboard controller, I believe that works to passthrough. the kicker is that all disks attached to the controller get passed to the VM...

danswartz's points on memory is what i'd recommend as well, however, OP should that he is talking about the system RAM where OP's 8GB was a USB stick for the ESXi partitions. regarding the USB stick, the install is right around 1GB, but some USB drives dont have exactly 1GB of space or maybe...

same as aaronearles but with a Dell PowerConnect 2724. here's a thread from couple weeks ago talking about setting up the vlan interfaces in pfSense: http://hardforum.com/showthread.php?t=1613226 if you need some help in that area.

that said, each provider (comcast, twc, etc) is responsible for setting the copy-once flag on the content. i don't have use WMC to record shows, but i've read numerous places that say many providers just don't set this flag to restrict copying the file (or being played by other instances of WMC).

perfect. sometimes the easiest solution slips the mind when you are crunchin' on a problem, you know? thanks

what a great response! I was planning on having all my management interfaces (ESXi, switch, and IPMI) on a different vlan and use pfSense to apply routing rules to that vlan (i.e. allow traffic from my workstation to that subnet). I will now have the DHCP service turned off for that interface...

i should also add, that in my head, the ESXi management NIC is cabled to the switch and VLANed to a management VLAN which is then part of the trunk to the physical internal NIC of the pfSense VM for routing

this thread is not meant to be a battle over the virtues of a virtual routing appliance. been there, done that. This might be as philosophical as a networking forum can get, but here it goes. I am working on upgrading my standard nerd home network. So far, I have only been planning in my head...

pfsense processes firewall rules top down. so say you have a packet. if it matches to top rule, the rule is applied (pass or deny). if it doesnt match, it tries the second rule and does the same thing on down the list. should the packet not match any firewall rule the packet is dropped.

thats a good point aaronearles. the routing is already setup by pfSense (assuming you have the auto config (i think thats what it's called, not in front of a box with now) enabled in the NAT setup, which it is by default). and so the only hurdle to jump is telling the firewall to let that...

i would change the rule to allow all traffic to all destinations and then place rules before it (in pfsense, above it) that deny access to other vlan's subnets to control the flow within your network. if a vlan should have access to other internal vlan (other interfaces) but not internet...

now that danswartz mentions it.....what i remember reading was about passthrough, not RDM. my bad. I suppose it may be worth a test given no passthrough is available. poor performance > no performance.

the quotes were for sarcasm. we have the house to paint and 200 feet of fence to stain (both sides!). "breaking the internet" does not fit into those weekend plans :)

agreed....i knew going into this exercise that more NICs on untangle would get around its tagging limitations. the pfSense vlan --> interface feature is quite awesome. you've given me plenty of options to play around with next weekend. my wife "thanks" you :)

makes perfect sense! thanks so much for the patience do you have any pros/cons of this setup over the OP describing the multiple vlan-ed interfaces in pfsense? here are what i can manage for pros/cons pro: makes vlans doable with untangle con: no logical (subnetting) segregation of clients...

here's the mental roadblock for me: why doesn't traffic from vlan1 find a route to a machine in vlan2 through the gateway (i.e. untangle's internal NIC)? i'm thinking of untangle's internal gateway as acting like another switch to which each vlan is uplinked thereby giving a route (since...

ah, so this is my bad.....i thought that this was trunking. doesn't port 1 need egress packets tagged with which vlan they are from? with the setup you describe in the quote above, can untangle distinguish one vlan from another (i believe the answer is no). if not, then how does this...

thanks for the reply! so even if i didnt care about the NATing screwing up the reporting, it wouldn't work anyways? is a transparent bridge untangle applying its WAN's gateway IP to its internal NIC and then manage the routing transparently? if thats the case then i dont see why it wouldn't...

the thread here http://hardforum.com/showthread.php?t=1613226 brought up a side-topic that I'd like to explore further and not muck up the thread's OP. note: this is home use, nothing critical. I have a pfSense 2.0 box acting as a firewall. It has two physical interfaces, one WAN, one trunked...

yup, the resolution is to not use a USB key as a datastore.

yeah, alright. that is awesome and something that i can't wait to try out in the real world. i have cable, so no sweat there. the third management nic is a very clever idea and I have just the vlan for that :)

ooo....another option to get around the requirements for VMDirectPath (which it looks like your procs won't support) is to Raw Disk Mapping (RDM). I have 0 personal experience with this, but I hear it is very good performance (close to native) and is logically giving a guest access to a disk (or...

ugo, once you add the vlan to the internal NIC, you are correct, go back to the interfaces screen and add them there. however, I had problems if i had an interface (OPT1, OPT2, etc...) and the NIC directly as another interface (i.e. LAN) my setup is eth0 --> WAN VLAN100 on eth1 --> LAN...

no way, a transparent bridged untangled box can sit outside my firewall? that would certainly solve all the problem i can think of. but my gut is saying that its not secure, but my mind doesnt know why :) does a transparent bridge take an IP on the internal interface? without that how would i...

i'll also add that another solution (should you have an extra expansion slot) is to get a second supported controller. use one for the local ESXi install and its datastore (for VM storage) and configure the other for passthrough to your guest VM. take a look at...

Passthrough is what you will want to accomplish your goals. However, there are the typical caveats. 1) the controller (onboard perc5i) needs to be either supported by ESXi 4.1 U1 for passthrough, or verfied to work by the community 2) the processor/chipset need to support VT-d which ultimately...

yeah, as soon as i discovered that i could have a 2 NIC pfsense box but utilize multiple internal networks on a single NIC, well, that was a pretty big sway from using untangle. granted i'm still trying to figure out I can use untangle behind pfsense for its benefits, but i think i'd only be...

exactly the use case for vlans in pfsense. I have multiple VLANS trunked from a single port on my dell powerconnect 2724 to a nic on my pfsense box. in pfsense, setup multiple VLANs on the nic, and then attach each VLAN to a pfsense interface(LAN, OPT1, OPT2, etc) the trick that i didnt know...

see that other thread by Chilly, http://hardforum.com/showthread.php?t=1607992, to get that 82574L NIC working in ESXi. my x9scm-f is humming along with both onboard NICs recognized and usable 1by ESXi. let us know if you having problems with the oem.tgz swap!

durianmy, I was able to boot the ESXi 4.1 U1 CD via the Virtual Storage over IPMI. Things that I would try if its hanging like you say (in no particular order): 1) redownload the ISO 2) reseat the memory modules 3) reset the BIOS to factory defaults 4) strip the hardware down to the bare...

I updated the firmware last night on my 2724 so if you are looking to do that and running into walls, let me know and i'll help you out

I dont have an answer for you regarding TLER on that drive, but since you are sourcing the disks for raid, you are likely looking at buying more than 2. the mail in rebate has a limit of 2. I hate when I miss things like that, so just informing in case you did not see that.

weird. i literally just did this 30 minutes ago on a 2724. i can confirm dashpuppy's instructions. additionally, the default user is admin and leave the password field blank. logging in failed in Chrome, but IE9 worked for me. i'm googling up some info on vlans and untangle/pfsense...