Re: FW: FW: [Openvpn-users] Map network drives

[Emmanuel Polet <e.polet@xxxxxxxxxx>]

The problem is, I am almost there with tun devices settings.... I don't 
really fell like going through all the process again with tap devices ! 
I can ping accross the tunnel (with tun) and access all my network 
computers ! Why wouldn't it allow me to map network drives if I use IPs 
? For instance : "net use : \\192.168.0.3\d"  does not require windows 
netbios naming features .... (or there's something I have missed 
somewhere...).

My iptables conf file is (I am sure there must be some pretty stupid 
things in there so I ask all your liniency ;)) :

# Generated by iptables-save v1.2.9 on Wed Nov  3 14:14:06 2004
*nat
:PREROUTING ACCEPT [73:7092]
:POSTROUTING ACCEPT [8:729]
:OUTPUT ACCEPT [2:151]
-A POSTROUTING -s 10.3.0.2 -o eth1 -j MASQUERADE  #"10.3.0.2" is the 
tunnel endpoint of my fedora openvpn server
COMMIT
# Completed on Wed Nov  3 14:14:06 2004
# Generated by iptables-save v1.2.9 on Wed Nov  3 14:14:06 2004
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [61:5839]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A INPUT -i tun+ -j ACCEPT
-A FORWARD -j RH-Firewall-1-INPUT
-A FORWARD -i tun+ -j ACCEPT
-A FORWARD -i tun+ -o eth1 -m state --state NEW,RELATED,ESTABLISHED -j 
ACCEPT
-A OUTPUT -o tun+ -j ACCEPT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -i eth1 -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp -m icmp --icmp-type 255 -j ACCEPT
-A RH-Firewall-1-INPUT -p esp -j ACCEPT
-A RH-Firewall-1-INPUT -p ah -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5000 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j 
ACCEPT
#-A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 5000 
-j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Wed Nov  3 14:14:06 2004

client side :

remote server_static_IP
local dyndns_IP
dev tun
ifconfig 10.3.0.2 10.3.0.1
comp-lzo
ping 10
proto udp
port 5000
secret shared_key
route 192.168.0.0 255.255.255.0 10.3.0.1
verb 5

serveur side :

local server_static_IP
remote dyndns_IP
dev tun
ifconfig 10.3.0.1 10.3.0.2
comp-lzo
ping 10
proto udp
port 5000
secret shared_key
verb 5

Pretty simple conf, isn't it :)
I think this a problem of nat or routing, but I don't know where to look 
for...

Thanks again for your help :)

> [snip]
>
> Using TAP and bridging is an easy way to access windows nnetbios
> naming features.  Is *is not* necessary to get things working.  Proper
> WINS/DNCP/DNS (exact requirements vary) setup will work quite well
> with the tunnel setup.
>
>  



____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users