pfsense, two subnets, jumboframes etc. | Thread profile

Hi, I have a setup that differes quite a bit form the norm (apparently): We have 3 subnets: 192.168.140.0/24, 192.168.210.0/24 and 192.168.190.0/24. The .140 subnet is our normal office network, with it's own firewall and normal access to the internet. The .210 subnet is our production network and uses jumboframes (mtu 9000) thruout. One layer3 switch and several smaller layer2 ...

Have you checked the firewall logs (Status -> System Logs Firewall tab)? tcpdump can be very helpful to verify packets arriving at a particular interface or going out a particular interface. On pfSense and other unix like systems, # pfsense -i <interface> will display traffic on the specified interface. You can use this to verify that the packets are being seen at each of the hops ...

Quote from: wallabybob on October 03, 2008, 06:44:12 pm Have you checked the firewall logs (Status -> System Logs Firewall tab)? Yes, I have also monitored what's happening via ssh from the pfsense box. The problem here is that there is an obscene amount of things in the log, due to several windows machines and servers sending broadcast and udp traffic everywhere on the network. ...

This is what I see in the filter logs: pass in on fxp0: 192.168.140.77.1549 > 192.168.210.113.22: tcp 28 [bad hdr length 0 - too short, < 20] And nothing after that, form either of those IP's. /jussi

Quote from: juosukai on Yesterday at 04:04:15 am This is what I see in the filter logs: pass in on fxp0: 192.168.140.77.1549 > 192.168.210.113.22: tcp 28 [bad hdr length 0 - too short, < 20] And nothing after that, form either of those IP's. /jussi This might be the reason the box was "lying around". I presume fxp0 is the motherboard NIC. That trace would lead me to ...

Hi One quick. Put ifconfig in the very last of /etc/rc. Quote instead after each reboot I need to set it up by hand using ifconfig. Any solutions to this? cheers,

Quote pass in on fxp0: 192.168.140.77.1549 > 192.168.210.113.22: tcp 28 [bad hdr length 0 - too short, < 20] first, disable hardware checksum offloading (in advanced) second - try different NIC

Hi Guys, thanks for the tips. Quote from: pan_2 on Yesterday at 05:49:04 am Quote pass in on fxp0: 192.168.140.77.1549 > 192.168.210.113.22: tcp 28 [bad hdr length 0 - too short, < 20] first, disable hardware checksum offloading (in advanced) second - try different NIC Tried this. Still not succeeding with the NAT. I also changed a new 3COM NIC in instead of the built in ...

Hi, Just MTU thingy put a side for now and focusing on port forwarding issue, I've experienced most likely the same issue with the latest 1.3-AA build yesterday. Everything on the WAN gets port forwarded by the rule are dropped with the [too short] messages. Although yours isn't 1.3 nor the latest 1.2.1 so it might not your case but I strongly recommend that you try some OLDER builds....

Are you allowing icmp otherwise you break path mtu discovery?! Can you monitor if RST packets are being sent by pfsense to the .140 network? Are you sure that ssh on pfSense is not running on that port(ssh:22)?