On 11/1/18 12:09 PM, Samuel Sieb wrote:
On 11/1/18 9:21 AM, rpjday(a)crashcourse.ca wrote:
> yesterday, did system-upgrade to fedora 29, went very smoothly, almost
> everything continued working out of the box except that i could no
> longer "vpnc" into my current client. i checked with their IT guy, who
> could see the incoming request and confirmed that everything seemed fine.
>
> then i looked at the interface created for the VPN tunnel:
>
> tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1412
> inet REDACTED netmask 255.255.255.255 destination REDACTED
> inet6 fe80::1f2f:331c:9941:aff2 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 0 bytes 0 (0.0 B)
> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
You need to provide more details about what isn't working. The tunnel
interface has an IP address. I see that there are no packets
transferred though. Does "ip route" show the right routing? How are
you running vpnc? Can you provide the relevant log messages or vpnc
output?
> i don't recall all that "unspec
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00"
> being there before (if it was, maybe i just never noticed it).
>
> is this normal? or do i now have to add something to
> /etc/vpnc/default.conf
> to deal with that?
I see this on F28 as well and I'm pretty sure it's been there for a long
time.
> i have no idea whether iscsi is relevant to this, just thought i'd
> throw it
> out there in case it was.
It's not relevant. I think there's some trigger related to network
interfaces changing.
Just for reference, from an F28 system that works:
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1412
inet xxx.xxx.xxx.xxx netmask 255.255.255.255 destination
xxx.xxx.xxx.xxx
inet6 xxxx::xxxx:xxxx:xxxx:xxxx 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 1162 bytes 180876 (176.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1595 bytes 122221 (119.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
So the most likely thing is the routing isn't getting set. "ip route
show" would reveal that.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Diplomacy: The art of saying "Nice doggy!" until you can find a -
- big enough rock. -
----------------------------------------------------------------------