Re: VPN now fails to come up, "unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Quoting Samuel Sieb <samuel@xxxxxxxx>:

On 11/1/18 9:21 AM, rpjday@xxxxxxxxxxxxxx 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.

  never mind ... it's related to some earlier complaining i saw on this list.
as we were debugging, the IT guy casually mentioned that he normally brings
up the VPN via NetworkManager, while I was used to doing it via "sudo vpnc".
"fine," i thought, and humoured him by bringing it up that way ... and it
worked.

  argh. so no more command line, only NetworkManager.

rday


_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux