Re: [Dnsmasq-discuss] dnsmasq 2.78 is failing to respond to dhcpv6 requests forwarded via relay agent
On Fri, Jan 04, 2019 at 11:55:49AM +0530, Sandeep K M wrote: > Attached are the packet captures: > > 1. Packets exchanged between client and relay (client-relay.pcap) > 2. Packets exchanged between relay and server (relay-server.pcap) > 3. strace of dnsmasq (dnsmasq.trace) > > Please let me know if any other information is required. At the server ip link # what interfaces are there ip -6 address ip -6 route Cheers Geert Stappers DevOps Engineer ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq 2.78 is failing to respond to dhcpv6 requests forwarded via relay agent
Hi, Here are the output of the commands: root@8320:~# *ip -6 addr* 49: m1s1p7: mtu 1500 state UNKNOWN qlen 1000 inet6 1040::2/120 scope global valid_lft forever preferred_lft forever inet6 fe80::480f:cf00:7af:8444/64 scope link valid_lft forever preferred_lft forever root@8320:~# *ip -6 route* 1040::/120 dev m1s1p7 proto kernel metric 256 pref medium 2020::/120 via 1040::1 dev m1s1p7 proto static metric 512 pref medium Sorry forgot to capture "ip link" output. The setup is disassembled as of now but if it is required then I will recreate the setup and send you the output. Thanks -Sandeep On Fri, Jan 4, 2019 at 2:30 PM Geert Stappers wrote: > On Fri, Jan 04, 2019 at 11:55:49AM +0530, Sandeep K M wrote: > > Attached are the packet captures: > > > > 1. Packets exchanged between client and relay (client-relay.pcap) > > 2. Packets exchanged between relay and server (relay-server.pcap) > > 3. strace of dnsmasq (dnsmasq.trace) > > > > Please let me know if any other information is required. > > > At the server > > ip link # what interfaces are there > ip -6 address > ip -6 route > > > > Cheers > Geert Stappers > DevOps Engineer > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq 2.78 is failing to respond to dhcpv6 requests forwarded via relay agent
On Fri, Jan 04, 2019 at 02:47:11PM +0530, Sandeep K M wrote: > On Fri, Jan 4, 2019 at 2:30 PM Geert Stappers wrote: > > On Fri, Jan 04, 2019 at 11:55:49AM +0530, Sandeep K M wrote: > > > [ ] > > > > > > Please let me know if any other information is required. > > > > > > At the server > > > > ip link # what interfaces are there > > ip -6 address > > ip -6 route > > > Hi, > > Here are the output of the commands: > > root@8320:~# *ip -6 addr* > 49: m1s1p7: mtu 1500 state UNKNOWN qlen 1000 > inet6 1040::2/120 scope global >valid_lft forever preferred_lft forever > inet6 fe80::480f:cf00:7af:8444/64 scope link >valid_lft forever preferred_lft forever Based upon that: there is only 1 interface > root@8320:~# *ip -6 route* > 1040::/120 dev m1s1p7 proto kernel metric 256 pref medium > 2020::/120 via 1040::1 dev m1s1p7 proto static metric 512 pref medium So there is some kind of routing information where the 2020::/120 network is ... > Sorry forgot to capture "ip link" output. The setup is disassembled as of > now but if it is required then I will recreate the setup and send you the > output. Come again? As in: "How was the output of `ip -6 addr` and `ip -6 route` generated? Cheers Geert Stappers DevOps Engineer ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Re: [Dnsmasq-discuss] dnsmasq 2.78 is failing to respond to dhcpv6 requests forwarded via relay agent
Hi, These command output is what I have captured previously for my reference before dissembling the setup. I tried to capture only the relevant interface output but not all. *I have recreated the setup and attached (ip-command-output.txt) is the output of the commands that you have requested in full*. Please let me know if any other information is needed. PS: As the command outputs are pretty big I have captured in a file. Thanks -Sandeep On Fri, Jan 4, 2019 at 3:59 PM Geert Stappers wrote: > On Fri, Jan 04, 2019 at 02:47:11PM +0530, Sandeep K M wrote: > > On Fri, Jan 4, 2019 at 2:30 PM Geert Stappers wrote: > > > On Fri, Jan 04, 2019 at 11:55:49AM +0530, Sandeep K M wrote: > > > > [ ] > > > > > > > > Please let me know if any other information is required. > > > > > > > > > At the server > > > > > > ip link # what interfaces are there > > > ip -6 address > > > ip -6 route > > > > > Hi, > > > > Here are the output of the commands: > > > > root@8320:~# *ip -6 addr* > > 49: m1s1p7: mtu 1500 state UNKNOWN > qlen 1000 > > inet6 1040::2/120 scope global > >valid_lft forever preferred_lft forever > > inet6 fe80::480f:cf00:7af:8444/64 scope link > >valid_lft forever preferred_lft forever > > Based upon that: there is only 1 interface > > > root@8320:~# *ip -6 route* > > 1040::/120 dev m1s1p7 proto kernel metric 256 pref medium > > 2020::/120 via 1040::1 dev m1s1p7 proto static metric 512 pref medium > > So there is some kind of routing information where the 2020::/120 network > is ... > > > > Sorry forgot to capture "ip link" output. The setup is disassembled as of > > now but if it is required then I will recreate the setup and send you the > > output. > > Come again? > As in: "How was the output of `ip -6 addr` and `ip -6 route` generated? > > > > Cheers > Geert Stappers > DevOps Engineer > > ___ > Dnsmasq-discuss mailing list > Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > root@8320:~# ip link 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: bridge-vrf: mtu 9198 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 52:3f:d2:26:79:d4 brd ff:ff:ff:ff:ff:ff 3: tap-br0@tap0: mtu 9198 qdisc noqueue master bridge-vrf state UP mode DEFAULT group default qlen 1000 link/ether 52:3f:d2:26:79:d4 brd ff:ff:ff:ff:ff:ff 4: tap0@tap-br0: mtu 9198 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 2e:e8:a4:b0:fe:1e brd ff:ff:ff:ff:ff:ff 6: m1s1p52: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 7: m1s1p8: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 8: m1s1p38: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 9: m1s1p13: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 10: m1s1p26: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 11: m1s1p35: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 12: m1s1p41: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 13: m1s1p42: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 14: m1s1p27: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 15: m1s1p48: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 16: m1s1p32: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 17: m1s1p3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 18: m1s1p18: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 19: m1s1p20: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 20: m1s1p40: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 21: m1s1p54: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:ff:ff:ff 22: m1s1p5: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 70:72:cf:fd:e1:0d brd ff:ff:ff:f
Re: [Dnsmasq-discuss] dnsmasq 2.78 is failing to respond to dhcpv6 requests forwarded via relay agent
On Fri, Jan 04, 2019 at 05:34:03PM +0530, Sandeep K M wrote: > Hi, > > On Fri, Jan 4, 2019 at 3:59 PM Geert Stappers wrote: > > On Fri, Jan 04, 2019 at 02:47:11PM +0530, Sandeep K M wrote: > > > On Fri, Jan 4, 2019 at 2:30 PM Geert Stappers wrote: > > > > On Fri, Jan 04, 2019 at 11:55:49AM +0530, Sandeep K M wrote: > > > > > [ ] > > > > > Please let me know if any other information is required. > > > > > > > > At the server > > > > ip link # what interfaces are there > > > > ip -6 address > > > > ip -6 route > > > > > > Here are the output of the commands: > > > > > > root@8320:~# *ip -6 addr* > > > 49: m1s1p7: mtu 1500 state UNKNOWN qlen > > > 1000 > > > inet6 1040::2/120 scope global > > >valid_lft forever preferred_lft forever > > > inet6 fe80::480f:cf00:7af:8444/64 scope link > > >valid_lft forever preferred_lft forever > > > > Based upon that: there is only 1 interface But it are about sixty > > > root@8320:~# *ip -6 route* > > > 1040::/120 dev m1s1p7 proto kernel metric 256 pref medium > > > 2020::/120 via 1040::1 dev m1s1p7 proto static metric 512 pref medium > > > > So there is some kind of routing information where the 2020::/120 network > > is ... > > In the non-stripped version > fe80::/64 dev bridge-vrf proto kernel metric 256 pref medium > fe80::/64 dev tap0 proto kernel metric 256 pref medium > fe80::/64 dev tap-br0 proto kernel metric 256 pref medium > fe80::/64 dev m1s1p7 proto kernel metric 256 pref medium (do notice there is no default route) > > > Sorry forgot to capture "ip link" output. The setup is disassembled as of > > > now but if it is required then I will recreate the setup and send you the > > > output. > > > > Come again? > > As in: "How was the output of `ip -6 addr` and `ip -6 route` generated?" > > > These command output is what I have captured previously for my reference > before dissembling the setup. OK. Thanks for explaining. > *I have recreated the setup and attached (ip-command-output.txt) is the > output of the commands that you have requested in full*. > Please let me know if any other information is needed. Not yet mentioned in this thread is working connectity between "server" and "client". This will require temporary manual configuration of an IPv6 address at client. Let say it is 2020::2/120. Then verify with more than "ping". Example given: `ssh 1040::2` It shall reveal how well router ( with the odd name 'Switch' ) is configured for routing between 1040::/120 and 2020::/120. Also if the ssh deamon is able to send packets out on the right interface. I do know that it might seem a detour. And we also known that original poster is already stuck with current setup. So the "detour" could be a step forward. Good luck. Groeten Geert Stappers ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
