Use WAN interface for package downloads?
-
Sorry I should have explained more.
The WAN connection is going out our local ISP which is open (Guest network), the LAN interface is connected to our corporate network which requires authentication to the internet which also takes a different path to another ISP.
when I try to install packages the package manager is using the LAN interface and want it to use the WAN interface (which doesn't require authentication).
-
-
when I try to install packages the package manager is using the LAN interface
ORLY?
Sorry, I'm new to this. What is ORLY?
-
http://www.internetslang.com/ORLY-meaning-definition.asp
Please, in the beginning, keep away from snort. Start with a 'bare' pfSense box. Learn it. As soon as you reached pfSense-expert level, think briefly about snort. That will do.
-
Sorry, I'm new to this. What is ORLY?
It means something you said or did shocked him/her.
is there something that does, whatever snort does, better?
-
snort is a powerful tool.
But, before using the tool, one has to know how to set it up, how to use it.
My advise: learn to work with pfSense first, then, and only then, add things you need - if you still need them ;) -
I still don't get why would package manager use your LAN to download anything. Except for complete firewall misconfiguration.
-
To each his own. Doesn't appear this is the place to come for help.
Thanks anyways.
-
Doesn't appear this is the place to come for help.
Actually, it's a great place to get help but your skin needs to be thicker when dealing with some of the characters here.
I'm still scratching my head about your issue. pfSense should use the WAN to grab the packages you want since WAN, by default, is the connection to the Internet. I can't imagine how you would have it going through LAN to the Internet in the first place. Are you sure there isn't some upstream router that is routing your pfSense WAN traffic somewhere else?
-
maybe checking that there is a default route out WAN for the pfSense box? If you can ssh to the pfSense box output of "netstat -rn" should show the routing table
