tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Fwd: 10-BETA : some network issues
Happy new year.
I'm trying to install a virtual NetBSD on qemu (without success, my
dedicated workstation usually runs Xen and doesn't have screen. I have
installed wdm to obtain a remote session, but just after
authentification, X session is closed...).
That being said, I have done another constatation.
NetBSD server runs ntpd:
legendre:[~] > ps auwx | grep ntp
root 1495 0,0 0,1 31280 16560 ? Ss mar.10AM
0:12.14 /usr/sbin/ntpd -p /var/run/ntpd.pid
bertrand 15903 0,0 0,0 20288 1868 pts/2 O+ 10:57AM
0:00.01 grep ntp
But clients cannot connect to this server when server runs NetBSD-10.
With a -9 kernel, time synchronization runs fine. Clients can use a ntp
server through VPN.
From a client, nmap shows:
Root hilbert:[~] > nmap -sU legendre
Starting Nmap 7.92 ( https://nmap.org ) at 2023-01-01 10:54 CET
Nmap scan report for legendre (192.168.10.128)
Host is up (0.00012s latency).
rDNS record for 192.168.10.128: legendre.systella.fr
Not shown: 988 closed udp ports (port-unreach)
PORT STATE SERVICE
53/udp open domain
67/udp open|filtered dhcps
69/udp open|filtered tftp
111/udp open rpcbind
123/udp open ntp
177/udp open xdmcp
1019/udp open|filtered unknown
1020/udp open|filtered unknown
1021/udp open|filtered exp1
1022/udp open|filtered exp2
1023/udp open|filtered unknown
2049/udp open nfs
MAC Address: 68:05:CA:02:B2:59 (Intel Corporate)
Nmap done: 1 IP address (1 host up) scanned in 172.47 seconds
On server, a tcpdump shows:
legendre# tcpdump -p -i lagg0 udp and port 123
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lagg0, link-type EN10MB (Ethernet), capture size 262144 bytes
11:00:49.661351 IP hilbert.systella.fr.ntp > legendre.systella.fr.ntp:
NTPv4, Client, length 48
11:01:27.033602 IP schwarz.systella.fr.ntp > legendre.systella.fr.ntp:
NTPv4, Client, length 48
11:01:27.776483 IP hilbert.systella.fr.ntp > legendre.systella.fr.ntp:
NTPv4, Client, length 48
and no answer from server...
It's not related to UDP packet as other daemons (tftp, nfs, rpcbind...)
run fine.
Regards,
JB
Home |
Main Index |
Thread Index |
Old Index