RE: route problem

2013-05-21 Thread Ivailo Tanusheff
Hi, Hope you have rebooted after enabling the gateway, but you can check this with sysctl net.inet.ip.forwarding :) So far from the server side it looks OK for me, but what are you pinging actually? How is done the configuration of the target device? This sounds like a pure routing problem,

Re: route problem

2013-05-20 Thread Andre Goree
On 2013-05-20 3:58 pm, Pol Hallen wrote: Hi folks! On my lan I've: server1 re0 - 192.168.1.250 xl0 - 192.168.2.250 default192.168.1.212 UGS 0 189re0 127.0.0.1 link#8 UH 0 18lo0 192.168.1.0/24 link#1 U

Re: route problem

2013-05-20 Thread Pol Hallen
Try: route add 192.168.1.0/24 192.168.2.250 does not run :-( Pol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

Re: route problem

2013-05-20 Thread Andre Goree
On 2013-05-20 4:19 pm, Pol Hallen wrote: Try: route add 192.168.1.0/24 192.168.2.250 does not run :-( Pol Interesting. I had a similar issue I got around with a similar route addition, though I was going from a LAN PC through my server that was running openvpn out to a remotely connected

Re: route problem

2013-05-20 Thread Pol Hallen
If you don't mind could you post the output of ifconfig from both boxes? server1: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 70:71:bc:94:c3:6d inet

Re: route problem

2013-05-20 Thread Andre Goree
On 2013-05-20 5:01 pm, Pol Hallen wrote: If you don't mind could you post the output of ifconfig from both boxes? server1: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE