tailscale .deb packages for armel? November 28, 2021 11:35AM |
Registered: 12 years ago Posts: 501 |
Re: tailscale dpk packages? November 28, 2021 05:03PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: tailscale dpk packages? November 29, 2021 10:15PM |
Registered: 12 years ago Posts: 501 |
apt install iptablesand then execute tailscaled
./tailscaled logtail started Program starting: v1.18.1-date.20211101, Go 1.17.3: []string{"./tailscaled"} LogID: 7f4577b5d4d3ad66e876c82807a57c8c613f6bab9dd9a2575c72dff8a04a6183 logpolicy: using system state directory "/var/lib/tailscale" wgengine.NewUserspaceEngine(tun "tailscale0") ... logtail: dialed "log.tailscale.io:443" in 282ms router: v6nat = true dns: [rc=unknown ret=direct] dns: using *dns.directManager link state: interfaces.State{defaultRoute=eth0 ifs={eth0:[192.168.11.5/24]} v4=true v6=false} magicsock: disco key = d:3a6e7b3dcea76f9d Creating wireguard device... Bringing wireguard device up... Bringing router up... external route: up Clearing router settings... Starting link monitor... Engine created. monitor: RTM_NEWROUTE: src=, dst=ff00::/8, gw=, outif=5, table=255 monitor: RTM_NEWROUTE: src=, dst=fe80::/64, gw=, outif=5, table=254 monitor: RTM_NEWROUTE: src=, dst=fe80::3617:b351:febb:bc05/128, gw=, outif=5, table=255 netmap packet filter: (not ready yet) Start using backend prefs created empty state for "_daemon": Prefs{ra=true dns=true want=false routes=[] nf=on Persist=nil} got initial portlist info in 0s control: HostInfo: {"IPNVersion":"1.18.1-date.20211101","BackendLogID":"7f4577b5d4d3ad66e876c82807a57c8c613f6bab9dd9a2575c72dff8a04a6183","OS":"linux","OSVersion":"Debian 11.0 (bullseye); kernel=5.2.9-kirkwood-tld-1","DeviceModel":"Pogoplug v4","Hostname":"PiHole7C6E","GoArch":"arm","Services":[{"Proto":"tcp","Port":22,"Description":"sshd [listener] 0 of 10-100 startups"},{"Proto":"tcp","Port":53,"Description":"pihole-FTL"},{"Proto":"tcp","Port":80,"Description":"lighttpd"},{"Proto":"tcp","Port":2812,"Description":"monit"}]} Backend: logs: be:7f4577b5d4d3ad66e876c82807a57c8c613f6bab9dd9a2575c72dff8a04a6183 fe: Switching ipn state NoState -> NeedsLogin (WantRunning=false, nm=false) blockEngineUpdates(true) wgengine: Reconfig: configuring userspace wireguard config (with 0/0 peers) wgengine: Reconfig: configuring router wgengine: Reconfig: configuring DNS dns: Set: {DefaultResolvers:[] Routes:{} SearchDomains:[] Hosts:0} control: authRoutine: state:new; goal=nil paused=false health("overall"): error: state=NeedsLogin, wantRunning=false dns: Resolvercfg: {Routes:{} Hosts:0 LocalDomains:[]} control: mapRoutine: state:new dns: OScfg: {Nameservers:[] SearchDomains:[] MatchDomains:[]}
root@PiHole7C6E:~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.11.5 netmask 255.255.255.0 broadcast 192.168.11.255 inet6 fe80::225:31ff:fe05:7c6e prefixlen 64 scopeid 0x20<link> ether 00:25:31:05:blahblah txqueuelen 1000 (Ethernet) RX packets 123102 bytes 86099982 (82.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16554 bytes 2046106 (1.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 36 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 61597 bytes 5337870 (5.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 61597 bytes 5337870 (5.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tailscale0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1280 inet6 fe80::3617:b351:febb:bc05 prefixlen 64 scopeid 0x20<link> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 500 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 8 bytes 384 (384.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@PiHole7C6E:/# ./tailscale up To authenticate, visit: https://login.tailscale.com/a/3e0b4caeblahblah
echo 1 > /proc/sys/net/ipv4/ip_forward echo 1 > /proc/sys/net/ipv6/conf/all/forwardingNote that you'd probably want to use some sort of the "tee" form shown in their docs to make it persist after reboots ...
./tailscale up --advertise-routes 192.168.11.0/24 --accept-routes
Re: tailscale .deb packages for armel? December 05, 2021 10:56PM |
Registered: 6 years ago Posts: 8 |
root@debian:~/tailscale_1.18.1_arm# ./tailscaled --state=tailscaled.state logtail started Program starting: v1.18.1- root@debian:~/tailscale_1.18.1_arm# ./tailscale up --advertise-exit-node To authenticate, visit: https://login.tailscale.com/a/8b54 Success.
Quote
Yes, the ARM version supports the same feature set as x86
# Tailscale packages for debian stretch deb https://pkgs.tailscale.com/stable/debian stretch main
root@debian:~# apt-get update && apt-get upgrade Hit:2 http://security.debian.org stretch/updates InRelease Ign:3 http://ftp.us.debian.org/debian stretch InRelease Hit:4 http://ftp.us.debian.org/debian stretch Release Hit:1 http://cdn-fastly.deb.debian.org/debian stretch-updates InRelease Fetched 5535 B in 42s (129 B/s) Reading package lists... Done N: Skipping acquire of configured file 'main/binary-armel/Packages' as repository 'https://pkgs.tailscale.com/stable/debian stretch InRelease' doesn't support architecture 'armel' Reading package lists... Done Building dependency tree Reading state information... Done
Re: tailscale .deb packages for armel? December 08, 2021 11:25AM |
Registered: 12 years ago Posts: 501 |
> root@debian:~/tailscale_1.18.1_arm# ./tailscaled > --state=tailscaled.state > logtail started > Program starting: v1.18.1- > > root@debian:~/tailscale_1.18.1_arm# ./tailscale up > --advertise-exit-node > > To authenticate, visit: > > https://login.tailscale.com/a/8b54 > > Success. >>
>Quote
Yes, the ARM version supports the same
> feature set as x86
>
Saying "ARM" is pretty generic. Their statement seems to be true, since it runs fine on other boxes, routers, etc. and functions there just as it does on 64bit intel boxes. They actually never say __which__ ARM architectures are supported by their builds. There are many. Our Kirkwood is "armel", which is ARMv5 Little Endian. They are only building for ARMv7 and newer ARM processors.
>
> # Tailscale packages for debian stretch > deb https://pkgs.tailscale.com/stable/debian > stretch main >>
> root@debian:~# apt-get update && apt-get upgrade > Hit:2 http://security.debian.org stretch/updates > InRelease > > Ign:3 http://ftp.us.debian.org/debian stretch > InRelease > > Hit:4 http://ftp.us.debian.org/debian stretch > Release > Hit:1 http://cdn-fastly.deb.debian.org/debian > stretch-updates InRelease > Fetched 5535 B in 42s (129 B/s) > Reading package lists... Done > N: Skipping acquire of configured file > 'main/binary-armel/Packages' as repository > 'https://pkgs.tailscale.com/stable/debian stretch > InRelease' doesn't support architecture 'armel' That says it right there ... doesn't support architecture 'armel' > Reading package lists... Done > Building dependency tree > Reading state information... Done >>
Re: tailscale .deb packages for armel? December 08, 2021 10:51PM |
Registered: 9 years ago Posts: 451 |
Quote
If you use these files, please also let us know your distro at info@tailscale.com, so that we can consider supporting it directly.
Re: tailscale .deb packages for armel? December 09, 2021 07:11AM |
Registered: 12 years ago Posts: 501 |
Details are here:Quote
It doesn't run systemd, so we'd have to write and support legacy sysvinit scripts, and reimplement missing functionality like automatic restarts. CentOS 6 is the only distro in our current list that would need this.
Re: tailscale .deb packages for armel? December 09, 2021 05:54PM |
Registered: 6 years ago Posts: 8 |
> > root@debian:~/tailscale_1.18.1_arm# > ./tailscaled > > --state=tailscaled.state > > logtail started > > Program starting: v1.18.1- > > > > root@debian:~/tailscale_1.18.1_arm# ./tailscale > up > > --advertise-exit-node > > > > To authenticate, visit: > > > > https://login.tailscale.com/a/8b54 > > > > Success. > >> >
> >Quote
Yes, the ARM version supports the same
> > feature set as x86
> >
>
> Saying "ARM" is pretty generic. Their statement
> seems to be true, since it runs fine on other
> boxes, routers, etc. and functions there just as
> it does on 64bit intel boxes. They actually never
> say __which__ ARM architectures are supported by
> their builds. There are many. Our Kirkwood is
> "armel", which is ARMv5 Little Endian. They are
> only building for ARMv7 and newer ARM processors.
>
> >
> > # Tailscale packages for debian stretch > > deb https://pkgs.tailscale.com/stable/debian > > stretch main > >> >
> > root@debian:~# apt-get update && apt-get > upgrade > > Hit:2 http://security.debian.org > stretch/updates > > InRelease > > > > > Ign:3 http://ftp.us.debian.org/debian stretch > > InRelease > > > > > Hit:4 http://ftp.us.debian.org/debian stretch > > Release > > Hit:1 http://cdn-fastly.deb.debian.org/debian > > stretch-updates InRelease > > Fetched 5535 B in 42s (129 B/s) > > Reading package lists... Done > > N: Skipping acquire of configured file > > 'main/binary-armel/Packages' as repository > > 'https://pkgs.tailscale.com/stable/debian > stretch > > InRelease' doesn't support architecture 'armel' > > That says it right there ... doesn't support > architecture 'armel' Yes, they didn't have repo for armel arch. So they advice the steps to install the binary manually > > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > >> >
Hello, It looks like you may need to do a manual installation. In your tailscale_1.18.1_arm folder, run these commands: sudo mkdir -p /etc/default /etc/systemd/system sudo mv systemd/tailscaled.defaults /etc/default/tailscaled sudo mv systemd/tailscaled.service /etc/systemd/system sudo mv tailscale /usr/bin/tailscale sudo mv tailscaled /usr/sbin/tailscaled sudo systemctl daemon-reload sudo systemctl enable --now tailscaled This will install Tailscale on your system (the same way that the debian package would) and enable it to automatically start on boot. After a moment or two run this command to see if Tailscale is running: sudo systemctl status tailscaled It should say something along the lines of Active: active (running). Then you can use sudo tailscale up to login as normal. I would also suggest rebooting the device at least once to ensure that Tailscale will come back up when you reboot. You can repeat those install directions in the future for when you need to upgrade Tailscale, just use sudo systemctl restart tailscaled instead of the systemctl enable command. Hope this helps. Be well,