Having to run the troubleshooter for the ~30 seconds or so it takes upon boot-up is a little on the tedious side, though. It seems as though the troubleshooter allows for the computer to be assigned a DHCP lease each time.
#IS EA3500 ABLE TO BRIDGE WINDOWS#
I had some difficulty figuring out why this was, but funnily enough (and for the first and probably last time, ever) the Windows Troubleshooter was able to resolve the issue while stating " 'Ethernet' does not have a valid IP configuration' ". It is running Gargoyle 1.2.9 and has been working perfectly even prior to my configuring pfSense last week, except with one small issue (both before and after pfSense) when I boot up the computer to which it is connected, it initially cannot connect to the Internet. I have a Fonera 2100 serving as a wireless bridge (it receives the wifi signal from the AP, and is plugged in via ethernet to a client computer to which it provides connectivity). All seems to be working soundly, and has been stable since it first went up 6 days ago.
#IS EA3500 ABLE TO BRIDGE PC#
I configured my network as suggested (with pfSense running on the PC and the router serving as an AP). Yes, you will notice additional lag when playing online FPSes while simultaneously saturating your link with BT traffic, but it will be still usable. Not quite easy to set up, but quite rewarding, IMHO. Of course, the BT traffic will occuoy most of your WAN bandwidth, so the next thing you will be interested in is the traffic shaper. With 2GB in you pfSense box, you can set most option in Vuze to "unlimited" and get hundred torrents running at the same time. BitTorrent traffic, for example: when installed, Vuze is configured to "play it easy" in order not to overload your router.
Plus, with decent hardware, pfSense can easily outperform the typical home router in many situations. In other words, you either already know everything about routing and stuff and can put the knowledge tp work with pfSense - or you can learn a lot about routing and stuff. One of the many nice things about pfSense is that it is rather easy to setup (provided you have some basic understanding about TCP/IP and how your ISP want you to connect), but, at the same time, provides many advanced features which you play around with. There are no major issues with the present hardware in terms of wireless drops. My question is, would this be worth it? I am wondering whether or not the trouble of configuring everything would actually provide tangible performance/consistency benefits over the current setup.
I would add in an ASUS PCE-N53 card (I haven't yet opened up the PC to see if there is a PCI-E x1 slot for it, but if there were not I would be willing to purchase a card) to provide it with wireless capabilities. The computer to be potentially used as the pfSense machine is an HP Compaq small form factor, with an Intel Core 2 Duo and generally decent specs given the demands of pfSense. To my knowledge, the chipset in this router is not currently hackable with either DD-WRT or OpenWRT. It features the stock Linksys Smart Wi-fi firmware, which is fairly primitive and a little on the gimmicky side. I currently have a Linksys EA3500 router running and serving as my primary firewall/ethernet+wireless router.
I'm thinking of setting up a pfSense machine this weekend, as (for once) I am not overloaded with schoolwork and feel up to the challenge of configuring a new network system.
0 kommentar(er)
