Re: [pfSense Support] Problem with RDP and VNC Streams
May be checking your MTU. -Raylund Ronny Forberger wrote: Hi List, first of all let me say pfsense is an awesome idea to provide a router platform. But I'm getting a strange problem and can't resolve it: All my VNC and RDP connections via being tunneled both throght an SSL VPN (openvpn) and OpenSSH tunnels after a while will hang. Then sometimes it turns back working but most of the time I have to reconnect vnc / rdp. I seems pakets are being dropped but I cant figure out where. This is very strange, since I was using this szenario before with the same tunnels but another router. (Same external PPPoE connection even). I do not have any traffic shaping rules enabled - I am stuck on finding glues what the problem could be. Can you maybe give me hints? Cheers, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Problem with RDP and VNC Streams
Hi List, first of all let me say pfsense is an awesome idea to provide a router platform. But I'm getting a strange problem and can't resolve it: All my VNC and RDP connections via being tunneled both throght an SSL VPN (openvpn) and OpenSSH tunnels after a while will hang. Then sometimes it turns back working but most of the time I have to reconnect vnc / rdp. I seems pakets are being dropped but I cant figure out where. This is very strange, since I was using this szenario before with the same tunnels but another router. (Same external PPPoE connection even). I do not have any traffic shaping rules enabled - I am stuck on finding glues what the problem could be. Can you maybe give me hints? Cheers, -- Ronny Forberger Systemadministration & IT-Support elego Software Solutions GmbH Gustav-Meyer-Allee 25 Gebäude 12, Raum 227 D-13355 Berlin Tel. +49 30 23 45 86 96 ronny.forberger at elegosoft.com Fax +49 30 23 45 86 95 http://www.elegosoft.com Geschäftsführer: Olaf Wagner, Sitz Berlin Amtsgericht Berlin-Charlottenburg, HRB 77719, USt-IdNr: DE163214194 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DNS Issues with 1.2 RC2
Thanks Scott! I was using the policybased_multiwan.pdf howto by Daniel Solsona. It does not mention DNS servers or static routes. It is working great now. Thanks for all of your hard work. The 1.2 release looks good. Robert On Thursday 25 October 2007 16:17, Scott Ullrich wrote: > On 10/25/07, Robert Goley <[EMAIL PROTECTED]> wrote: > [snip] > > > What am I missing? > > Static routes. See the multi-wan tutorials. > > Scott > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] DNS Issues with 1.2 RC2
On 10/25/07, Robert Goley <[EMAIL PROTECTED]> wrote: [snip] > What am I missing? Static routes. See the multi-wan tutorials. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] DNS Issues with 1.2 RC2
I have a multi wan setup with 3 WAN interfaces and 1 LAN. It is using policy based routing. DNS refuses to work. This is because the pfsense machine can not resolve anything. The DNS servers are correct. They are pingable from the pfsense machine. They are accessible from machines on the LAN. A traceroute shows that the pfsense machine is trying to access DNS servers for OPT1 and OPT2 using the WAN interface instead. I setup rules for the LAN interface so that all connections to the specific DNS server must go out over specific interfaces. This works for the LAN but does not work for the pfsense machine itself. Can some one provide some insight to this? Do I need to add static routes for these instead of LAN firewall entries? The warnings on the static routes page seems to indicate that I should not. I am sure that others are using multiple DNS servers from multiple ISPs in a multi-wan setup. What am I missing? Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] Re: pfsense, procurve 2626 3 vlans
Dimitri Rodis wrote: Glad to hear it's resolved. Just FYI, the Dell switches are a little weird with the VLAN configs-- they aren't as easy to configure for tagged/untagged VLANs as the Procurves are IMO. There is a setting on each port on the Dells called PVID (which stands for Primary VLAN ID), and basically that is how you change a port's "untagged" membership to a VLAN. Then on an entirely separate page, you can set up the tagged ports. Very unfriendly and confusing compared to the HPs. Thanks. The HPs seems to be a lot better. I guess we should at least have bought a manageable switch from dell, not just a web-managed. Anyway, I'll return the switch to Dell and ask for a full refund. We got 2 switches and the first one failed within 24h. The one lasted OK and never failed (a few days), but the web interface became unreacheable within about 2 days. Ugo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Re: pfsense, procurve 2626 3 vlans
Glad to hear it's resolved. Just FYI, the Dell switches are a little weird with the VLAN configs-- they aren't as easy to configure for tagged/untagged VLANs as the Procurves are IMO. There is a setting on each port on the Dells called PVID (which stands for Primary VLAN ID), and basically that is how you change a port's "untagged" membership to a VLAN. Then on an entirely separate page, you can set up the tagged ports. Very unfriendly and confusing compared to the HPs. Dimitri Rodis Integrita Systems LLC -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Ugo Bellavance Sent: Wednesday, October 24, 2007 10:35 PM To: support@pfsense.com Subject: [pfSense Support] Re: pfsense, procurve 2626 3 vlans Ugo Bellavance wrote: > Dimitri Rodis wrote: >> What device did you connect? If a machine (.120) is able to communicate >> with pfSense (.1), then I would say there is a problem with this mystery >> device, and not your setup. What IP address did you assign to your LAN >> interface on vlan#3? (You only mentioned LAN2). > > 192.168.2.1 is the LAN interface address. It's my usual setup at home, > WAN -> DHCP, LAN -> 192.168.2.1. 192.168.2.120 was a laptop that I > connected to port in vlan3. > > Thanks a lot Dimitri. Ok, nevermind, I got it working. I don't know exactly what was the problem, but it is all working now on the procurve switch and the crappy Dell is going back to Dell. I'll try to write an article in my blog about that to help other people. Thanks all for all your help! Regards, Ugo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
