I would check any used computer store re-pc here in Seattle has lots of
cheap older 100MB SW's for under 30USD. Option B is something like the WRT54G
from Linksys, you can used a hacked firmware for them that is VLAN aware
(openwrt, seavsoft, etc.. (please don't anyone go off on any tangent
Jared B. Griffith schrieb:
When is 1.3 due to be out?
I'm not a spokesperson for pfSense but from what I remember, it will be
about a year from now on before it's in a semi-ready state.
So, don't hold your breath ;-)
Rainer
Hi Chris,
When I set my firewall as you said below it still wouldn't allow me to log
on to MSN. The only way I get it to work is by setting the any rule on all
the criteria:
Proto Source PortDestination PortGateway
ScheduleDescription
* *
because you can't specify filters on openvpn clients, we simply built a
separate box which is a dedicated openvpn server; this also means we can
keep our main firewalls locked down better and the openvpn clients come
in via a DMZ which gives better tracking.
I've never actually herd of having to open any ports for MSN to function
properly. Now, I only use the messenger portion of this so I may not have
ever had the need. Without adding any special rules to the firewall or
changing the outbound NAT, do you get any error messages in the log? Have
you
Searching the archives show's people have had luck running this under Xen but I
would like to export a Realtek 8169 Nic into the VM for use as pfsence's wan
nic. Reading http://doc.pfsense.org/index.php/ALTQ_drivers I don't see explicit
support for the 8111/8169 but I do see the 8110/8168 which
lartc wrote:
hi all,
i have inherited two sites that need to be connected with an ipsec
tunnel -- issue is that each lan on each side of the tunnel is identical
rfc1918 address space (172.16.16.0/16).
is there a way to overcome this with nat
There will be in 1.3, but isn't now. Still I
Hi Curtis,
Thanks for the advise, I will give wireshark a bash, just not sue how to
find where things are going wrong with MSN ? I dont see any errors in the
log either I just see sessions going through their normal process.
I seemed to make some changes today and it works.
Regards,
Mike
Ok. I guess you could leave it where it is and let it run or if you do
want, with Wireshark the big thing is inspecting what you expect. You logon
to MSN (or attempt), you then should see traffic from MSN acknowledging
that. Typical TCP stuff. Let me know if you want more information.
--
Hello, I am new in this list so from already my greetings to all. I have the
following doubt: how can I leak LogMeIn in pfsense?
Should I leak only everything what it avenges from *.logmein.com?
I wait for some suggestion, from already thank you very much
Sebastián Veloso Varas
Fuerza Aérea de
You've already asked this question once. Please be patient, the answer
may take a bit.
Sebastián Veloso Varas wrote:
Hello, I am new in this list so from already my greetings to all. I have the
following doubt: how can I leak LogMeIn in pfsense?
Should I leak only everything what it
Which log me in product are you trying to use?
Curtis
The problem turned out to be packet state maintenance. I set it to Keep State
for all of my rules having to do with NAT and tunnels and it solved all of the
problems. It was one of those duh. moments. :-)
Its kind of interesting that Windows 2000, 2000 Server, XP and 2003 Server
didn't seem
Linksys has a couple of very nice models as does Adtran.
Curtis Maurand
Head Honcho
Xyonet Webhosting Services
6 Evergreen Lane
Biddeford, ME 04005
http://www.xyonet.com
mailto:[EMAIL PROTECTED]
207.252.7748
- Original Message -
From: Paul M [EMAIL PROTECTED]
To:
the idea is to leak any version of LogMeIn, but in these moments it is a
LogMeIn Free Version
Best Regards
Sebastián Veloso Varas
Fuerza Aérea de Chile
Servicio Aerofotogramétrico
Departamento de Informática y Computación
Teléfono: (56-2) 3272025 - (56-2)3272045
Web :
15 matches
Mail list logo
