So I inadvertently killed my D1 by drowning it in a river and work sent me a new D3.
With a rooted D1, I was able to get VPNC to a Cisco working and <whisper>WiFi tether; I wanted the same usability in the D3. A little trickier getting things set up, but I'm just about there.
With wonderful resources like you people, found a radio tweak, and also that the D3 has tun built in (can see dev/net/tun), so with VPNC widget, got connected, see our Cisco banner text and issued IP in the VPNC log.
However, once connected to VPN, I can't access internet and can't ping any of our internal IPs either...I think my routes are wrong.
But, I don't know enough about setting up the routing table and was hoping someone could steer me in the right direction? I would like to manually adjust them, see if it works, then hopefully script it for after connection.
Not sure what anyone might need, but I'll start with this:
Before...
ip route list
66.174.201.64 dev ppp0 scope link
66.174.201.64 dev ppp0 proto kernel scope link src 10.251.3.122
default via 66.174.201.64 dev ppp0
netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
gether0 DOWN 0.0.0.0 0.0.0.0 0x00001002
sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080
ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
tun DOWN 0.0.0.0 0.0.0.0 0x00001002
ppp0 UP 10.251.3.122 255.255.255.255 0x000010d1
After VPN connected...
66.174.201.64 dev ppp0 scope link
66.174.201.64 dev ppp0 proto kernel scope link src 10.251.3.122
default via 66.174.201.64 dev ppp0
netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
gether0 DOWN 0.0.0.0 0.0.0.0 0x00001002
sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080
ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
tun DOWN 0.0.0.0 0.0.0.0 0x00001002
tun0 UP 192.168.144.8 255.255.255.255 0x000010d1
ppp0 UP 10.251.3.122 255.255.255.255 0x000010d1
I appreciate anyone taking the time to help me out.
(Edited to correct format and improve readability...no idea how that happened)
With a rooted D1, I was able to get VPNC to a Cisco working and <whisper>WiFi tether; I wanted the same usability in the D3. A little trickier getting things set up, but I'm just about there.
With wonderful resources like you people, found a radio tweak, and also that the D3 has tun built in (can see dev/net/tun), so with VPNC widget, got connected, see our Cisco banner text and issued IP in the VPNC log.
However, once connected to VPN, I can't access internet and can't ping any of our internal IPs either...I think my routes are wrong.
But, I don't know enough about setting up the routing table and was hoping someone could steer me in the right direction? I would like to manually adjust them, see if it works, then hopefully script it for after connection.
Not sure what anyone might need, but I'll start with this:
Before...
ip route list
66.174.201.64 dev ppp0 scope link
66.174.201.64 dev ppp0 proto kernel scope link src 10.251.3.122
default via 66.174.201.64 dev ppp0
netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
gether0 DOWN 0.0.0.0 0.0.0.0 0x00001002
sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080
ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
tun DOWN 0.0.0.0 0.0.0.0 0x00001002
ppp0 UP 10.251.3.122 255.255.255.255 0x000010d1
After VPN connected...
66.174.201.64 dev ppp0 scope link
66.174.201.64 dev ppp0 proto kernel scope link src 10.251.3.122
default via 66.174.201.64 dev ppp0
netcfg
lo UP 127.0.0.1 255.0.0.0 0x00000049
usb0 DOWN 0.0.0.0 0.0.0.0 0x00001002
gether0 DOWN 0.0.0.0 0.0.0.0 0x00001002
sit0 DOWN 0.0.0.0 0.0.0.0 0x00000080
ip6tnl0 DOWN 0.0.0.0 0.0.0.0 0x00000080
tun DOWN 0.0.0.0 0.0.0.0 0x00001002
tun0 UP 192.168.144.8 255.255.255.255 0x000010d1
ppp0 UP 10.251.3.122 255.255.255.255 0x000010d1
I appreciate anyone taking the time to help me out.
(Edited to correct format and improve readability...no idea how that happened)
Last edited: