Re: [pfSense-discussion] weird openVPN behaviour

[Mark Dueck]

Curtis LaMasters wrote: To change the MTU modify /conf/config.xml.  Change the line <mtu/> to <mtu>1480</mtu> and then be sure to save.  I'm not sure if a reboot will be needed for this.  At a minimum an interface reset would be needed. Curtis LaMasters http://www.curtis-lamasters.com http://www.builtnetworks.com How do I remount in read/write mode?  I've tried 'mount -o rw /cf'  but that does not work. I've look into this more and I see I get some error messages on one pfSense server: Aug 16 08:41:11 php: : Resyncing configuration for all packages. Aug 16 08:41:12 check_reload_status: check_reload_status is starting Aug 16 08:41:12 login: login on ttyv0 as root Aug 16 08:42:56 kernel: arp: 192.168.0.2 is on re0 but got reply from 00:19:5b:89:c0:37 on dc0 Aug 16 08:43:56 kernel: arp: 192.168.0.2 is on re0 but got reply from 00:19:5b:89:c0:37 on dc0 Aug 16 08:44:53 last message repeated 3 times Aug 16 08:47:18 kernel: arp: 172.27.200.1 moved from 00:13:4f:00:aa:32 to 00:60:b3:e9:14:04 on dc0 Aug 16 08:53:55 kernel: arp: 192.168.0.2 is on re0 but got reply from 00:19:5b:89:c0:37 on dc0 Aug 16 09:00:02 kernel: arp: 172.27.200.1 moved from 00:60:b3:e9:14:04 to 00:13:4f:00:aa:32 on dc0 Aug 16 09:02:03 kernel: arp: 192.168.0.2 is on re0 but got reply from 00:19:5b:89:c0:37 on dc0 Aug 16 09:03:06 kernel: arp: 192.168.0.2 is on re0 but got reply from 00:19:5b:89:c0:37 on dc0 Aug 16 09:07:31 kernel: arp: 172.27.200.1 moved from 00:13:4f:00:aa:32 to 00:60:b3:e9:14:04 on dc0 I am guessing my problem is that a 192.168.0.0/24 exists also on the wan side of my wireless network, but I did not think it would affect anything because the whole network is bridged between locations, and I have a 172.27.200.x on the wan side on both pfSense boxes.  Here's the config: Lan A 192.168.0.x ->pfSense - 172.27.200.2 -> wireless network all bridged with also a 192.168.0.x  -> 172.27.200.1 -pfSense -> 10.20.30.x Lan B pinging the 172.27.200.x from either side comes through perfectly.  Once I ping from lan B to lan A or vice versa, ping times increase by 500ms each time.