| Hello Brian, Your tcpdump Output is just ARP traffic for getting the ethernet address to the IP address. And according to the length in tcpdump output I would say it is requesting the ethernet address to an IPv4 IP address. So nothing wrong there. Regards, Ingo Gesendet von meinem BlackBerry 10-Smartphone.
Hello Amanda users, For some reason I’m not seeing much/any Amanda traffic, I did re-register with a new email address last month… Installing Amanda-client on an ununtu system, when I run # amcheck from the server I’m seeing the following in tcpdump output. flower.wadsworth.org.516 > biowork2.health1.hcom.health.state.ny.us.amanda: Flags [R], cksum 0x3d33 (correct), seq 2828866964, win 49640, length 0 11:29:44.054702 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has flower.wadsworth.org tell biowork2.health1.hcom.health.state.ny.us, length 28 11:29:44.054796 ARP, Ethernet (len 6), IPv4 (len 4), Reply flower.wadsworth.org is-at 00:14:4f:21:10:c2 (oui Unknown), length 46 That is, Amanda-client is being activated by IPv4 but responding using IPv6. I know that is mentioned in the mail archives and I have checked, re-installed xinetd on the client and verified flags are IPv4. root@biowork2:/etc/ufw/applications.d# more /etc/xinetd.d/amanda # default: on # # description: Amanda services for Amanda server and client. # service amanda { disable
= no flags
= IPv4 socket_type
= dgram protocol
= udp wait
= no user
= amandabackup group
= disk groups
= yes #
server
= /usr/lib/amanda/amandad server
= /usr/lib/x86_64-linux-gnu/amanda/amandad server_args
= -auth=bsdtcp amdump amindexd amidxtaped } Either I’m missing a step or I’m not chasing the correct problem. Any help would be appreciated. Brian Brian Cuttler, Wadsworth Center/NYS Dept of Health Albany, NY 12201 | ||
- ipv4 vs ipv6 Cuttler, Brian R (HEALTH)
- AW: ipv4 vs ipv6 Ingo Schaefer
- Re: ipv4 vs ipv6 Cuttler, Brian R (HEALTH)
- Re: ipv4 vs ipv6 Ingo Schaefer
