OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Profile of sff »
  • Show Posts »
  • Messages
  • Profile Info
    • Summary
    • Show Stats
    • Show Posts...
      • Messages
      • Topics
      • Attachments

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

  • Messages
  • Topics
  • Attachments

Messages - sff

Pages: [1]
1
20.7 Legacy Series / Re: IPv6 gateway marked as "down" after every reboot
« on: August 15, 2020, 10:35:20 am »
Unfortunately it is not working although the gateway was marked as "up" during the time of this test (it also showed successful RTT).
The first output was made with "Source Address: WAN":

# /sbin/ping6 -S '2a03:4000:33:732::1' -c '3' 'fe80::1%vtnet0'
PING6(56=40+8+8 bytes) 2a03:4000:33:732::1 --> fe80::1%vtnet0
ping6: wrote fe80::1%vtnet0 16 chars, ret=-1
ping6: wrote fe80::1%vtnet0 16 chars, ret=-1
ping6: wrote fe80::1%vtnet0 16 chars, ret=-1

--- fe80::1%vtnet0 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host


This second test was done with "Source Address: Default":
# /sbin/ping6 -c '3' 'fe80::1%vtnet0'
PING6(56=40+8+8 bytes) fe80::487e:ceff:feec:3085%vtnet0 --> fe80::1%vtnet0
ping6: wrote fe80::1%vtnet0 16 chars, ret=-1
ping6: wrote fe80::1%vtnet0 16 chars, ret=-1
ping6: wrote fe80::1%vtnet0 16 chars, ret=-1

--- fe80::1%vtnet0 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host
ping6: sendmsg: No route to host

2
20.7 Legacy Series / Re: IPv6 gateway marked as "down" after every reboot
« on: August 14, 2020, 07:54:24 pm »
Hi,
I attached the screenshot from what the provider told me (prefix, subnet size, gateway), what I configured in the interface and what the gateway looks like.

What I don't understand is why it works after disabling/enabling. So there can't be a general problem with the configuration, because it only does not work after doing changes to the interface or after rebooting.

I also attached the output from the ping.

About the fe80::1 gateway: I have a second machine running with the same provider (netcup.de), same infrastructure (just different IPs), which is running a Sophos UTM 9 - no problems at all... it just works. :/

Thank you for your help!

Regards,
 Harald

3
20.7 Legacy Series / Re: IPv6 gateway marked as "down" after every reboot
« on: August 14, 2020, 01:44:51 pm »
Hi,

I'm on 20.7.1-amd64.

When I go to Interfaces, Diagnostics, Ping and enter the gateway address (fe80::1) I get "no route to host". But I get that too, when the gateway is "up" (although dpinger shows it as reachable with a RTT of 5ms). Which is weird - how is dpinger able to ping it?

4
20.7 Legacy Series / IPv6 gateway marked as "down" after every reboot
« on: August 14, 2020, 01:06:41 pm »
Hi all,

on my WAN I have public IPv4 and IPv6 addresses. Both are configured statically.
IPv4 works, but IPv6 never works after a reboot or after making any changes to the WAN interface (and applying those changes). Reason is that the IPv6 gateway is marked as "down".
After disabling and enabling the IPv6 gateway everything works fine until the next reboot or until applying any change to the WAN interface. After that: gateway gets marked as "down", disable, enable, and it's "up" again.

Any ideas for the reason or how to solve this? Because whenever the gateway should reboot I won't have IPv6 connectivity until I manually repair the IPv6 gateway...


Thank you,
 regards,
  Harry

Pages: [1]
OPNsense is an OSS project © Deciso B.V. 2015 - 2024 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2