Hi,
when doing slaacctl send solicitation vio0, tcpdump says:
mx-00# tcpdump -ni vio0 icmp6 tcpdump: listening on vio0, link-type EN10MB
16:06:54.725229 fe80::2de:361a:24aa:d7a6 > ff02::2: icmp6: router
solicitation
16:06:55.803125 fe80::22d8:b00:86fa:424c > ff02::1:ff96:189a: icmp6:
neighbor
Hello,
@Fernando Gont:
I have tried that as well. No difference.
@ Bastien Durel
When pinging ff02::2%vio0 I don't receive any replies.
The tcpdump for those requests is the following:
# tcpdump -ni vio0 icmp6
tcpdump: listening on vio0, link-type EN10MB
15:47:40.580787
On 22/8/19 21:11, list wrote:
> Hi,
>
> I might be missing something right here
>
> I have the output of "route show" attached, because I cannot paste it in
> here in a formatted form.
>
>
> This is super annoying.
>
> Just wanna get the damn thing running.
Your default route is wrong.
Le jeudi 22 août 2019 à 20:11 +0200, list a écrit :
> Hi,
>
> I might be missing something right here
>
> I have the output of "route show" attached, because I cannot paste it
> in
> here in a formatted form.
>
>
> This is super annoying.
>
> Just wanna get the damn thing running.
>
Hi,
I might be missing something right here
I have the output of "route show" attached, because I cannot paste it in
here in a formatted form.
This is super annoying.
Just wanna get the damn thing running.
Regards,
Stephan
On 8/19/19 10:33 AM, Bastien Durel wrote:
> Le dimanche 18
On Sun, Aug 18, 2019 at 07:36:55PM +0200, list wrote:
> Hi,
>
> The output of slaacctl show interface vio0 ist the following:
>
> # slaacctl show interface vio0
>
> slaacctl: connect: /dev/slaacd.sock: Connection refused
>
> This is not how it is supposed to be i guess.
it would be
Le dimanche 18 août 2019 à 11:50 +0200, list a écrit :
> When I take a closer look and run tcpdump while pinging I see the
> following output:
> (With route to fe80::1%vio added and the normal hostname.vio0)
>
> 11:40:36.446539 fe80:: > ff02::1:ff00:1: icmp6: neighbor sol:
> who has fe80::1
>
>
Hi,
so i removed everything from /etc/mygate and rebooted the machine.
I still cannot ping anybody.
The output of slaacctl show interface vio0 ist the following:
# slaacctl show interface vio0
slaacctl: connect: /dev/slaacd.sock: Connection refused
This is not how it is supposed to be i
> From: list
> my /etc/hostname looks exactly like you proposed:
> inet6 autoconf autoconfprivacy soii
> inet6
> when i enter the default IPv6 gateway manually. I can ping stuff
> but don't get a reply. When I don't: "No route to host"
> (With route to fe80::1%vio added and the
Hi,
my /etc/hostname looks exactly like you proposed:
inet6 autoconf autoconfprivacy soii
inet6
when i enter the default IPv6 gateway manually. I can ping stuff but don't get
a reply.
When I don't: "No route to host"
PF is not the problem. Same results when loading pf rules that look like
> From: list
> I've restarted my VM over the official
> Webinterface but still...
> When trying to ping the gateway on fe80::1 I don't get any icmp
> echoreplies.
> What is the behavior of pf when disabled ? Is there some kind of
> default blocking rule that is still active ?
Have you
Hi,
i did specify it correctly now and the entry in my routing table is made.
However that doesn't change my situation. I've restarted my VM over the
official Webinterface but still...
When trying to ping the gateway on fe80::1 I don't get any icmp
echoreplies.
When asking the provider I am
I have taken a look at the website of my hosting provider.
My IPv6 gateway would be fe80::1.
When trying to add the route manually i get "network unreachable".
https://marc.info/?l=openbsd-misc=156572276103920=2
SCNR
On Thu, Aug 15, 2019 at 06:50:09PM +0200, list wrote:
> Hi,
>
> EDIT:
>
> I have taken a look at the website of my hosting provider.
>
> My IPv6 gateway would be fe80::1.
>
> When trying to add the route manually i get "network unreachable".
>
Did you specify the output interface ? With LL
Hi,
EDIT:
I have taken a look at the website of my hosting provider.
My IPv6 gateway would be fe80::1.
When trying to add the route manually i get "network unreachable".
Which leaves me puzzeled.
Stephan
On 8/14/19 11:08 PM, gwes wrote:
> On 8/14/19 4:45 PM, freda_bundc...@nym.hush.com
Hey,
thanks for the answers,
so ..
I firstly got rid of the alias and the manual routes.
1.) "Can you ping your own IPv6 address ?"
Yes i can. Works as expected.
2.) "tcpdump -ni vio0 -s 1500 icmp6"
results in alot of "neigbor sol".
3.) "Who are you trying to ping?"
I have a /64 for
On 8/14/19 4:45 PM, freda_bundc...@nym.hush.com wrote:
Hi, I just thought since the interface was vio that you're running in a virtual
environment. Providers like Vultr say "Important Note: If you add an IPv6
subnet to an existing machine, you must restart the server via the Vultr
control panel
On 8/14/19 2:36 PM, list wrote:
My hostname.vio0 now looks like this:
inet6 alias /64
!route add -inet6 default fe80::2de:361a:24aa:d7a6%vio
When doing a "ifconfig vio0" I get:
vio0: flags=8843 mtu 1500
[...]
inet6 fe80::2de:361a:24aa:d7a6%vio0 prefixlen 64
Hi, I just thought since the interface was vio that you're running in a virtual
environment. Providers like Vultr say "Important Note: If you add an IPv6
subnet to an existing machine, you must restart the server via the Vultr
control panel before IPv6 will work. Restarting via SSH or similar is
On Wed, Aug 14, 2019 at 08:36:45PM +0200, list wrote:
> Hello,
>
> thanks alot for your suggestions! I really appreciate it.
>
> Unluckily that didn't work out.
>
> My hostname.vio0 now looks like this:
>
> inet6 alias /64
>
> !route add -inet6 default
Hi,
what do you mean by "a hard restart" ?
There is nothing else i can do apart from restarting my OpenBSD Box..
I think I am misunderstanding you right there.
Stephan
On 8/14/19 9:17 PM, freda_bundc...@nym.hush.com wrote:
> Hi, since your interface is vio0 your virtual service provider
Hi, since your interface is vio0 your virtual service provider might
require a hard restart of your server -- separate from rebooting
from your installed OpenBSD.
I know you disabled pf, but once it's working, I think the rules
you need to add would be something like:
# ip6
# man icmp6 has
Hello,
thanks alot for your suggestions! I really appreciate it.
Unluckily that didn't work out.
My hostname.vio0 now looks like this:
inet6 alias /64
!route add -inet6 default fe80::2de:361a:24aa:d7a6%vio0
So with this gateway added I now don't get the "no route to host"
On 8/13/19 10:11 AM, Thomas Bohl wrote:
Hello,
My hostname.vio0 looks like this:
dhcp
inet6 alias 64
You most likely need to add a route. Add something like this to your
hostname file:
!route add -inet6 default fe80::1%vio0
Just in case you have the same problem. For whatever
You can also add a second line to /etc/mygate if you’re using that.
> On Aug 13, 2019, at 1:11 PM, Thomas Bohl wrote:
>
> Hello,
>
>> My hostname.vio0 looks like this:
>> dhcp
>> inet6 alias > provider> 64
>>
>
> You most likely need to add a route. Add something like this to your hostname
Hello,
My hostname.vio0 looks like this:
dhcp
inet6 alias 64
You most likely need to add a route. Add something like this to your
hostname file:
!route add -inet6 default fe80::1%vio0
Just in case you have the same problem. For whatever reason, after a
reboot, I have to do this in
On Tue, Aug 13, 2019 at 05:25:43PM +0200, list wrote:
> Hi,
>
> I have been trying to set up IPv6 on my OpenBSD machine.
>
> It is running on stable branch.
>
> The interface I am trying to configure IPv6 on is "vio".
>
> My hostname.vio0 looks like this:
>
>
> dhcp
>
> inet6 alias
Hi,
I have been trying to set up IPv6 on my OpenBSD machine.
It is running on stable branch.
The interface I am trying to configure IPv6 on is "vio".
My hostname.vio0 looks like this:
dhcp
inet6 alias 64
But I just can't get it to work. It is not reachable at all. I may not
be reached
I'm running OpenBSD 4.2 on SPARC64. I have managed to get a simple BGP setup
working on IPv4, however the IPv6 version of the same setup fails. A BGP
session is established in both cases and peer B claims to be announcing what it
should be announcing, yet in the IPv6 version peer A does not add
29 matches
Mail list logo
