Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
I see that I'm missing the modules necessary to run iptables on my DNS 323 (chroot debian). I have a few openvpn tunnels to family and friends that all terminate to openvpn processes that run on my DNS-323. My end goal is to route traffic between multiple lan segments, and SNAT the traffic on the NAS.
When I run the follow it reports the modules are not loaded.
wheezy1:~# iptables -t filter -L
iptables v1.3.6: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
Does anyone have compiled modules for a 2.6.12.6-arm1 vanilla kernel?
Reason for modules:
It's slightly off topic, but the reason for needing iptables is to source nat packets destined for networks connected by vpn tunnels. From what I see in tcpdumps when I attempt to access an adjacent network my source IP is mangled as it passes through the vpn tunnel. When the other side attempts to reply it's sending the packet to the adjacent vpn endpoint, not my local subnet device. All documentation I've found on for openvpn on openwrt shows others utilizing iptables to mangle the packets before the enter the vpn tunnel.
Thanks in advance for any help, or other suggestions for implementing a routed openvpn solution.
Offline
kennedy101 wrote:
Reason for modules:
It's slightly off topic, but the reason for needing iptables is to source nat packets destined for networks connected by vpn tunnels. From what I see in tcpdumps when I attempt to access an adjacent network my source IP is mangled as it passes through the vpn tunnel. When the other side attempts to reply it's sending the packet to the adjacent vpn endpoint, not my local subnet device. All documentation I've found on for openvpn on openwrt shows others utilizing iptables to mangle the packets before the enter the vpn tunnel.
Have you any success with kernel module compilation? I have the same problem with a Open VPN and I also think that the problem happens because no ip forwarding between two network interfaces because lack of kernel modules
Offline
alny wrote:
I also think that the problem happens because no ip forwarding between two network interfaces because lack of kernel modules
To enable IP forwarding (routing), just type:
echo 1 > /proc/sys/net/ipv4/ip_forward
Offline
Electrocut wrote:
alny wrote:
I also think that the problem happens because no ip forwarding between two network interfaces because lack of kernel modules
To enable IP forwarding (routing), just type:
echo 1 > /proc/sys/net/ipv4/ip_forward
I have already do that but nothing happens. I still think that the problem with no "forwarding" module in the kernel
Offline
I don't think any special module is needed, to be able to forward IP packets. I think Iptables kernel modules are just if you want to filter traffic ... (choose what you want to forward), but I can be wrong.
Offline
Electrocut wrote:
I don't think any special module is needed, to be able to forward IP packets. I think Iptables kernel modules are just if you want to filter traffic ... (choose what you want to forward), but I can be wrong.
Yes, you were right. No additional kernel modules was needed to forward IP from tun0 to egiga0 interface, just 1 flag in /proc/sys/net/ipv4/ip_forward file. My problem was in routing tables but not at DNS-323 device but at the other computers in my network. When they receive IP packet from other VPN network (10.10.0.x in my case) they don't know how to respond, to which gateway send the answer. When I put routing record
route add 10.10.0.0 MASK 255.255.255.0 <my NAS IP here>
to them, everything goes to work perfect.
My final step was adding the same record to my home router, so now I don't need to configure each computer in network.
Offline
The modules I need are to route from one client PC on say site1, to another client PC on site2. For the sake of arguement here was my setup
Site1 PC -> Site1 VPN GW -> Site1 VPN Tun -> Internet
192.168.200.146/24 192.168.200.5 10.0.0.1
Internet -> Site2 VPN Tun -> Site2 VPN GW -> Site2 PC
10.0.0.2 192.168.150.1 192.168.150.101/24
All route statements were in place and I could ping each VPN endpoint (10.0.0.1 or 10.0.0.2)
A tcpdump on both sides (internal interface) showed that the VPN Gw at site 1 was mangling the packet from the PC. I could see that the source IP address seen at the Site2 interface (192.168.150.1) was 10.0.0.1 NOT 192.168.200.146. I noted that the Site1 GW interface (192.168.200.5) showed the correct source IP.
Looking at the OpenWRT forums this is "normal" and a source NAT rule is needed to force the packets to not mangle.
Anyway, the modules have been tested and working in my OpenWRT boxes. It would be nice to have the same modules available for the NAS.
Offline
Ended up loading DD-WRT on a WRT54G-TM (8 meg flash) router with jffs enabled. With openvpn moved to the router got the all needed module for iptables.
Offline
From WebAdmin LAN settings is:
IP 192.168.1.10
MASK 255.255.255.0
GW 192.168.1.1
comand through shell (on funplug 0.5)
route delete -net 0.0.0.0 (default route have metric 0)
route add -net 172.20.0.0 netmask 255.255.0.0 gw 192.168.1.2 metric 0
route add -net 0.0.0.0 netmask 0.0.0.0 gw 192.168.1.1 metric 2
Before reboot routs work correctly,
but after rebooting routing table DNS-323 return to "default" - with set in webadmin (default route 192.168.1.1)
How to save config through shell?
(DNS-323, FW 1.07,2xSAMSUNG 1TB [HD103UJ], funplug 0.5)
Last edited by driverom (2009-12-14 11:52:16)
Offline
Pages: 1