Jump to content

yabasoya

Active Members
  • Content Count

    184
  • Joined

  • Last visited

  • Days Won

    2

About yabasoya

  • Rank
    Hak5 Zombie

Profile Information

  • Gender
    Male
  • Location
    Bolivia

Recent Profile Visitors

1,215 profile views
  1. Thanks for the heads up.. I'll need to check into this again.
  2. You're not the only one. In fact, I cant find anyone that has gotten this to work. I keep checking back here weekly in hopes that someone made a breakthrough.
  3. I guess that is a no?
  4. I am also curious to know if anyone has gotten this to work fully.
  5. Can someone take a look at these routing tables to see if anything looks funny? 104.XXX.XXX.25 = CloudServer 192.168.222.2 = VPN address of LAN Turtle 192.168.222.3 = VPN address of my laptop 192.168.1.1 = Router that the Lan Turtle is connected to 172.27.208.1 = LAN address of OpenVPN Server CloudServer turtle@Cloud Server:~$ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 104.XXX.XXX.1 0.0.0.0 UG 0 0 0 eth0 10.8.0.0 10.8.0.2 255.255.255.0 UG 0 0 0 tun0 10.8.0.2 * 255.255.255.255 UH 0 0 0 tun0 104.XXX.XXX.0 * 255.255.192.0 U 0 0 0 eth0 172.27.208.0 * 255.255.255.128 U 0 0 0 as0t0 192.168.1.0 * 255.255.255.0 U 0 0 0 as0t0 192.168.222.2 * 255.255.255.255 UH 0 0 0 as0t0 turtle@ClodServer:~$ ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. From 192.168.222.2 icmp_seq=1 Destination Port Unreachable From 192.168.222.2 icmp_seq=2 Destination Port Unreachable LAN Turtle root@turtle:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.222.1 128.0.0.0 UG 0 0 0 tun0 default 192.168.1.1 0.0.0.0 UG 0 0 0 eth1 104.XXX.XXX.25 192.168.1.1 255.255.255.255 UGH 0 0 0 eth1 128.0.0.0 192.168.222.1 128.0.0.0 UG 0 0 0 tun0 172.16.84.0 * 255.255.255.0 U 0 0 0 br-lan 192.168.1.0 * 255.255.255.0 U 0 0 0 eth1 192.168.222.0 * 255.255.255.0 U 0 0 0 tun0 root@turtle:~# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1): 56 data bytes 64 bytes from 192.168.1.1: seq=0 ttl=64 time=1.562 ms 64 bytes from 192.168.1.1: seq=1 ttl=64 time=0.623 ms My Laptop IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 10.10.50.1 10.10.50.102 20 0.0.0.0 128.0.0.0 192.168.222.1 192.168.222.3 20 10.10.50.0 255.255.255.0 On-link 10.10.50.102 276 10.10.50.102 255.255.255.255 On-link 10.10.50.102 276 10.10.50.255 255.255.255.255 On-link 10.10.50.102 276 104.XXX.XXX.25 255.255.255.255 10.10.50.1 10.10.50.102 20 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 128.0.0.0 128.0.0.0 192.168.222.1 192.168.222.3 20 192.168.222.0 255.255.255.0 On-link 192.168.222.3 276 192.168.222.3 255.255.255.255 On-link 192.168.222.3 276 192.168.222.255 255.255.255.255 On-link 192.168.222.3 276 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 192.168.222.3 276 224.0.0.0 240.0.0.0 On-link 10.10.50.102 276 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link 192.168.222.3 276 255.255.255.255 255.255.255.255 On-link 10.10.50.102 276 Traceroute from my laptop to turtle LAN Tracing route to 192.168.1.1 over a maximum of 30 hops 1 22 ms * 23 ms 172.27.208.1 2 43 ms 45 ms 46 ms 192.168.222.2 3 192.168.222.2 reports: Destination protocol unreachable. Trace complete.
  6. My cable modem puts out 2 public ip addresses. Basically I have a switch and 2 routers along with a vps.
  7. Still stuck.. I cant get past this. I found a couple of solutions online that say to reconfigure routes. I didn't want to start messing with that because I feel the turtle should phone home after being dropped and give me a vpn connection from whatever subnet it falls on. It must be something silly that I'm missing.
  8. I am stuck exactly in the same spot. I have my lan turtle sitting behind a Linksys router. I am on a 10.x.x.x subnet, Openvpn server is on a 172.27.224.x subnet, and my lan turtle is on a 192.168.1.x subnet. Both my laptop and lan turtle have successful connections to the open vpn server. Tracing route to 192.168.1.1 over a maximum of 30 hops 1 25 ms * 21 ms 172.27.224.1 2 48 ms 43 ms 43 ms 172.27.224.8 3 172.27.224.8 reports: Destination protocol unreachable. Trace complete. 172.27.224.8 is my lan turtle, so it looks as if it knows to go to the lan turtle to find the 192.168.1.x subnet. It just isn't making that last step. If I SSH into the lan turtle, I can ping 192.168.1.1 successfully.
  9. I suspected that is what this is trying to accomplish. Although I've read several times that you cannot SSH into the Ethernet side without reverse SSH first. Can you SSH directly this way? I'm just trying to connect the dots. Thanks.
  10. I figured it out. When I initially setup the user turtle as a vpn clent, I never selected autologin. I then downlowded the ovpn file. Shortly after I checked the autoligin box and didn't realize the format of the ovpn file changed. I downloaded a fresh copy of the ovpn file and uploaded it. All works now. I suppose that the turtle was connecting to a login prompt rather than auto login. It never made the full connection but reported back that it connected. Just thought I'd share so that it may help someone else.
  11. So this is setup as one or the other, not both at the same time? I still need to work on this more but the admin panel shows 0 connections even though the lan turtle seems to connect.
  12. Sorry for being a pain. I can't seem to find the answer. After starting the openvpn module I seem to lose SSH through the VPS to the Lan Turtle. I get the connection refused error. As soon as I turn off open vpn (SSH through USB), I can SSH again through the VPS to the Lan Turtle. I'm trying to get openvpn working correctly and that may be causing my issue since I cant seem to get openvpn right either :( Also, can someone point me to instructions on converting .ovpn to .conf?
  13. I suppose it was me not connecting the dots.. Sorry about that. I would have bet my life that I could SSH over LAN. Thanks for putting up with my ignorance.
×
×
  • Create New...