[pfSense Support] Install NIC
Good afternoon, how do I recognize the pfSense an onboard NIC ? Is there any command or some way for him to download the driver from the internet via shell? The card in question is Atheros AR8158 - 10/100 Controller, the offboard Realtekhas been recognized and is usually configured as a WAN, the need to enable Atheros to be onboard LAN. Sds, Ivanildo Galvão - MCP, MCT, MCSA, VSP Consultor de Tecnologia Tel. (84) 3201 2146 | Cel. (84) 9111 8873 ivani...@itservices.com.br| www.itservices.com.br http://www.itservices.com.br/ Twitter: @ivanildogalvao image001.jpg
[pfSense Support] Install NIC Atheros of mainboard
Good afternoon, how do I recognize the pfSense an onboard NIC ? Is there any command or some way for him to download the driver from the internet via shell? The card in question is Atheros AR8158 - 10/100 Controller, the offboard Realtekhas been recognized and is usually configured as a WAN, the need to enable Atheros to be onboard LAN. Sds, Ivanildo Galvão - MCP, MCT, MCSA, VSP Consultor de Tecnologia Tel. (84) 3201 2146 | Cel. (84) 9111 8873 ivani...@itservices.com.br| www.itservices.com.br http://www.itservices.com.br/ Twitter: @ivanildogalvao image001.jpg
RE: [pfSense Support] Install NIC Atheros of mainboard
It doesn’t look like that particular Atheros chipset is supported yet in FreeBSD, which means you will not be able to use it with pfSense at all. (The alc(4) driver supports the Atheros 815x series of devices, but only claims to support the AR8151 and AR8152 so far.) I assume you’re using a BIOSTAR motherboard, since no-one else appears to use the AR8158 yet? This chip is new enough that even Qualcomm/Atheros’ own website does not list it! You might have to wait for pfSense 2.1, which is expected be based on FreeBSD 9, *if* support for the chip is added to FreeBSD 9 prior to release. Most likely, you’ll have to wait for pfSense 2.2, which might be based on FreeBSD 9.1 – whenever that happens. Since FreeBSD 9 is already in beta, I doubt support for that chip will be added before release. -Adam Thompson athom...@athompso.net (204) 291-7950 - direct (204) 489-6515 - fax From: Ivanildo Galvão - IT Services [mailto:ivani...@itservices.com.br] Sent: Tuesday, September 06, 2011 10:13 To: support@pfsense.com Subject: [pfSense Support] Install NIC Atheros of mainboard Good afternoon, how do I recognize the pfSense an onboard NIC ? Is there any command or some way for him to download the driver from the internet via shell? The card in question is Atheros AR8158 - 10/100 Controller, the offboard Realtekhas been recognized and is usually configured as a WAN, the need to enable Atheros to be onboard LAN. Sds, Ivanildo Galvão - MCP, MCT, MCSA, VSP Consultor de Tecnologia Tel. (84) 3201 2146 | Cel. (84) 9111 8873 ivani...@itservices.com.br| www.itservices.com.br http://www.itservices.com.br/ Twitter: @ivanildogalvao image001.jpg
[pfSense Support] IPSEC client behind pfsense nat unable to make particular type traffic
Hello Everyone, I had two guests using IPSEC VPN unable to connect to their exchange servers while connected to their company VPN, when using the old router, a linux machine doing outbound NAT, they were not experiencing this; one of these guests experiences such problem also from its home ADSL link. Apart from the protocol specific problem mentioned above their VPN is working fine. I'm asking you because I cannot figure how there can be different behaviours for the same type of traffic (it is encrypted!). I'm using AON with lan-wan rule for port 500 and after that i have a global lan-wan rule. Thank you, Giacomo. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RES: [pfSense Support] Install NIC Atheros of mainboard
That's right, the motherboard is a Biostar, has said the situation for the client asked him to get an offboard network card that is compatible, such as 3Com and Realtek,or get another computrador that already have network cards compatible . Thanks for your help! Ivanildo Galvão - MCP, MCT, MCSA, VSP Consultor de Tecnologia Tel. (84) 3201 2146 | Cel. (84) 9111 8873 mailto:ivani...@itservices.com.br ivani...@itservices.com.br| http://www.itservices.com.br/ www.itservices.com.br Twitter: @ivanildogalvao De: Adam Thompson [mailto:athom...@athompso.net] Enviada em: terça-feira, 6 de setembro de 2011 12:29 Para: support@pfsense.com Assunto: RE: [pfSense Support] Install NIC Atheros of mainboard It doesn’t look like that particular Atheros chipset is supported yet in FreeBSD, which means you will not be able to use it with pfSense at all. (The alc(4) driver supports the Atheros 815x series of devices, but only claims to support the AR8151 and AR8152 so far.) I assume you’re using a BIOSTAR motherboard, since no-one else appears to use the AR8158 yet? This chip is new enough that even Qualcomm/Atheros’ own website does not list it! You might have to wait for pfSense 2.1, which is expected be based on FreeBSD 9, *if* support for the chip is added to FreeBSD 9 prior to release. Most likely, you’ll have to wait for pfSense 2.2, which might be based on FreeBSD 9.1 – whenever that happens. Since FreeBSD 9 is already in beta, I doubt support for that chip will be added before release. -Adam Thompson athom...@athompso.net (204) 291-7950 - direct (204) 489-6515 - fax From: Ivanildo Galvão - IT Services [mailto:ivani...@itservices.com.br] Sent: Tuesday, September 06, 2011 10:13 To: support@pfsense.com Subject: [pfSense Support] Install NIC Atheros of mainboard Good afternoon, how do I recognize the pfSense an onboard NIC ? Is there any command or some way for him to download the driver from the internet via shell? The card in question is Atheros AR8158 - 10/100 Controller, the offboard Realtekhas been recognized and is usually configured as a WAN, the need to enable Atheros to be onboard LAN. Sds, Ivanildo Galvão - MCP, MCT, MCSA, VSP Consultor de Tecnologia Tel. (84) 3201 2146 | Cel. (84) 9111 8873 ivani...@itservices.com.br| www.itservices.com.br http://www.itservices.com.br/ Twitter: @ivanildogalvao image002.jpgimage003.jpg
[pfSense Support] STP on Redundant Transparent Firewalls
Greetings- We have 2 pfsense machines that are bridged on different vlans operating as a transparent firewall. These machines are setup for CARP replication to each other, which is verified functioning. However, for somereason, the STP is not quite functioning on the secondary PBX. We have to keep one of the interfaces down, or we get in a loop situation. Has anyone experienced this behavior that can advise a work around? What are we missing here? Thank you- Austin Smith, A+, NET+, SMBE, MCSA Director of Information Techology Digital Compass (404) 410-2708 direct (404) 410-2701 fax 949 W. Marietta Street, Suite x104 Atlanta, GA 30318 **For immediate assistance please contact our technical team at 888-640-2260**
[pfSense Support] Outbound port forward
Hi all. I have a pfSense 2.0 box with 1 LAN and two WAN´s; Actually i´m facing a problem: i need to forward all the requests going out by the port 53 (DNS) to a single external DNS server, in dispite off the DNS configured in the clients. Can someone help me in that? Danilo - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] Outbound port forward
On Tue, Sep 6, 2011 at 1:08 PM, Arquivos arqui...@otv.com.br wrote: i need to forward all the requests going out by the port 53 (DNS) to a single external DNS server, in dispite off the DNS configured in the clients. Can someone help me in that? What you want is a NAT Port Forward entry on your LAN interface to destination port 53 and a redirect target IP of the server you want to force. I haven't tried this but I believe it will do what you are asking. db - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] Outbound port forward
What you want is a NAT Port Forward entry on your LAN interface to destination port 53 and a redirect target IP of the server you want to force. I haven't tried this but I believe it will do what you are asking. I´ve tried this config and it didn´t work :( In NAT por forward only internal IP´s can be specified and i need an external DNS server, so i´m still in the dark. Tks.. Danilo - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] Outbound port forward
What if you enabled DNS Forwarder and forwarded All DNS Request to PFsense. Ryan Rodrigue P.O. Box 4336 Chief Technical Manager Houma, LA 70361 A A R Electronics, Inc Phone (985) 876-4096 510 West Tunnel Blvd Phone (800) 649-7346 Houma, LA 70360 Fax (985) 853-0134 radiote...@aaremail.com www.aarelectronics.com -Original Message- From: Arquivos [mailto:arqui...@otv.com.br] Sent: Tuesday, September 06, 2011 2:34 PM To: support@pfsense.com Subject: Re: [pfSense Support] Outbound port forward What you want is a NAT Port Forward entry on your LAN interface to destination port 53 and a redirect target IP of the server you want to force. I haven't tried this but I believe it will do what you are asking. I´ve tried this config and it didn´t work :( In NAT por forward only internal IP´s can be specified and i need an external DNS server, so i´m still in the dark. Tks.. Danilo - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org __ Information from ESET NOD32 Antivirus, version of virus signature database 6441 (20110906) __ The message was checked by ESET NOD32 Antivirus. http://www.eset.com - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
RE: [pfSense Support] Linking 2 Building without VPN
Hi Klaus, Thanks for the initial assistance. I have now added an interface into each pfSense box to use for this link. Just because the rest of my subnets are /24 I have added the same to these two cards. So in 10.0.0.0/24 (Site A) I have added a new interface with 10.0.9.1 and from my pfSense box and all my workstation boxes I can ping 10.0.9.1 10.0.2.0/24 (Site B) I have added a new interface with 10.0.9.2 and from my pfSense box and all my workstation boxes I can ping 10.0.9.2 From 10.0.0.254 I can ping 10.0.9.1 but not 10.0.9.2 10.0.2.254 I can ping 10.0.9.2 but not 10.0.9.1 Even without any routes being created I figure from 10.0.9.1 I should be able to see 10.0.9.2 We did have a lightning strike so now I am questioning if I have my setup correct or some more dead hardware here in the building. Thanks. From: Klaus Wunder [mailto:kl...@net-wunder.de] Sent: Tuesday, August 02, 2011 4:03 AM To: support@pfsense.com Subject: AW: [pfSense Support] Linking 2 Building without VPN Hello, do you have a Layer 2 connections between the buildings? If, I think there are two possible options 1. Creating a Transport LAN to connect the buildings In this case you have to create a new Interface on both sites. You can create a small subnet 10.0.254.252/30 to interconnect the LAN. In this way you can use static routing 2. Creating a Transport LAN with failover I think a other option is to create the transport LAN and use a dynamic routing protocol to interconnect the LANs on booth site. In this case you can use the IPsec connection as a backup link. I think this solution will work with OSPF, you can install on pfSense. If you have questions just let me know. Regards Von: Ron Lemon [mailto:r...@maplewood.com] Gesendet: Dienstag, 2. August 2011 06:24 An: 'support@pfsense.com' Betreff: [pfSense Support] Linking 2 Building without VPN Hello, I have 2 building each with multiple networks. They are currently joined via an IPSec VPN. Building A is 10.0.0.0/24 and 10.0.1.0/24 And Building B is 10.0.2.0/24 and 10.0.3.0/24 Right now I have a 10 Mb/s link to the internet in building A and a 100 Mb/s link in building B so I have an IPSec vpn tying 10.0.0.0 to 10.0.2.0 and 10.0.3.0 and the same for 10.0.1.0 Now I have just been provided a 20 Mb/s dedicated patch cable between the two buildings (this wire has no services on it but is essential a 30 KM patch cable). What is the best way to utilize this new Patch Cable to take the place of my current IPSec VPN links? If need be I can add interfaces to the 2 pfSense boxes or just make configuration changes. Thanks.
