Jump to content

Welcome, Guest!


  • Content Count

  • Joined

  • Last visited

  • Days Won


thompson last won the day on September 28 2014

thompson had the most liked content!

Community Reputation

1 Neutral

About thompson

  • Rank

Profile Information

  • Location
    United States
  1. I set it up for static ip awhile back, and it's hardwired (wasn't quite convinced wifi had the same speed as wired).
  2. So after months of flawless operation I noticed I couldn't ssh to my Pi about 2 weeks ago. Activity & networking lights were running, everything appeared okay. So I just hard restarted it and she came back, but a few days later it happened again. I run it headless with a few daemons running (transmission, openvpn, samba, ftp, etc). Here's the message I get when I try to ssh to the Pi using connectbot on my androids: But now even powering it off doesn't bring back connectivity, it just immediately goes to that. I tried reformatting the SD card on a whim, as well as trying a more robust power supply (neither of which seemed to have any positive effect). I've also ran apt-get update, upgrade & dist-upgrade just to see and it also had no effect. I have a suspicion that openvpn or part of transmission is to blame, but last time I was able to gain access I killed both & it still ended up error'ing minutes later. I did make some changes to IPTables to allow external access while still channeling other traffic through the vpn and also suspect this is part of it (the "failed to connect to (port 1773)" doesn't seem like my internal ip should be there twice). Any help is greatly appreciated as I'm a bit lost atm, I do know it's driving me crazy.
  3. So I was having a problem with port forwarding while my vpn client was running. Found a fix adding some rules & making a new table. But problem is it doesn't all seem to stick after reboot. I tried with /etc/network/if-up.d but it would apply the rules 3 times & seemed to confuse the Pi (breaking connectivity). I have managed to get a script setup to automatically save & restore iptables however. But otherwise the ip rule & table 10 don't seem to be persistent. Here's how I've setup the table (10 / openvpn) echo 10 openvpn >> /etc/iproute2/rt_tables ip route show table main | while read entry; do sudo ip route add table 10 $entry; done Which outputs: default via dev eth0 dev eth0 proto kernel scope link src Then adding a lookup rule or what have you (still pretty new to this) : ip rule add fwmark 10 lookup openvpn Then finally adding the port I'm interested in: iptables -A OUTPUT -t mangle -p tcp --sport PORT -j MARK --set-mark=10 Any help is greatly appreciated, I'm away from the Pi most of the time so having ssh access is clutch, but I'd also like that vpn connection to stay up. Sent from my Nexus 7 using Tapatalk

About Us

Bringing you the latest Raspberry Pi news, tutorials and user forum.

The Fruity Computer

  • Create New...