cannot reach client from server

speedfight

i am trying to reach the clients from the server. but that's not working. i can reach the server from the client.

this is my config:

port 1194
proto udp
dev tun
ca ca.crt
cert server.crt
key server.key
dh dh1024.pem
server 10.9.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
keepalive 10 120
cipher AES-128-CBC
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 3

client.conf

client
dev tun
proto udp
remote serverip 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert client.crt
key client.key
cipher AES-128-CBC
comp-lzo
verb 3

netstat -rn

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.9.0.2        0.0.0.0         255.255.255.255 UH        0 0          0 tun0
xx.211.xx.0     0.0.0.0         255.255.255.0   U         0 0          0 eth0
10.9.0.0        10.9.0.2        255.255.255.0   UG        0 0          0 tun0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
0.0.0.0         xx.211.xx.254   0.0.0.0         UG        0 0          0 eth0

ifconfig -a

tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:10.9.0.1  P-t-P:10.9.0.2  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:423 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:0 (0.0 b)  TX bytes:35532 (34.6 KiB)

brctl show

bridge name     bridge id               STP enabled     interfaces

could someone tell me what I am missing or doing wrong

thanks in advance

janjust

if the client can reach the server but the server cannot reach/ping the client then there's a firewall on the client blocking access.

Also, just for the record: you're using a 'tun' setup, so bridging has no effect here.

speedfight

janjust wroteif the client can reach the server but the server cannot reach/ping the client then there's a firewall on the client blocking access.

your totally right! disabled the firewall and now pinging is possible.

janjust wrote Also, just for the record: you're using a 'tun' setup, so bridging has no effect here.

is it better to use tap then?

pfsense has a bug that doesn't support tap

thnx

janjust

'tap' isn't necessarily better than 'tun' ; if your setup is now working I wouldn't bother with 'tap' - I just made the comment about the bridge because it does not have anything to do with a 'tun' based setup.