Score:0

How to Configure IPTABLES to allow PTP sync behind a bridge firewall

ps flag

We have a Fedora machine with eth0(ip:10.321.xx)connected to intranet. The same machine has a eth1 with a few more linux boxes connected in a 192.xx network. on the 10.321.xx n/w there is a PTP server. But I cant seem to get PTP time sync to work on any machines on the 192.xx n/w. I AM able to ping the PTP server from the 192.xx network machines. These are some configurations. I've disabled my normal rules just to get this to work. Thanks for all the help !

>> iptables -t filter -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination   
iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ACCEPT     all  --  anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
MASQUERADE  all  --  anywhere             anywhere  
>>iptables -t filter -L -n -v                              

Chain INPUT (policy ACCEPT 9202 packets, 6661K bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 2123 packets, 1601K bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 1874 packets, 341K bytes)
 pkts bytes target     prot opt in     out     source               destination

iptables -t nat -L -n -v                                

Chain PREROUTING (policy ACCEPT 378 packets, 28122 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain INPUT (policy ACCEPT 6 packets, 1136 bytes)
 pkts bytes target     prot opt in     out     source               destination
   29  5602 ACCEPT     all  --  eth0   *       0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT 180 packets, 12961 bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain POSTROUTING (policy ACCEPT 2 packets, 120 bytes)
 pkts bytes target     prot opt in     out     source               destination
  281 19314 MASQUERADE  all  --  *  eth0    0.0.0.0/0            0.0.0.0/0

on the 192.xxx network , this is this status of ptp

# Timestamp, State, Clock ID, One Way Delay, Offset From Master, Slave to Master, Master to Slave, Observed Drift, Last packet Received, One Way Delay Mean, One Way Delay Std Dev, Offset From Master Mean, Offset From Master Std Dev, Observed Drift Mean, Observed Drift Std Dev, raw delayMS, raw delaySM
023-03-30 17:31:09.354917, init, 
2023-03-30 17:31:09.456202, lstn_init,  1 
2023-03-30 17:31:21.526305, lstn_init,  1 
2023-03-30 17:31:33.529512, lstn_init,  1 
2023-03-30 17:31:45.532634, lstn_init,  1 
2023-03-30 17:31:57.535746, lstn_init,  1 
2023-03-30 17:32:09.535962, flt, 
2023-03-30 17:32:09.536005, flt, 
2023-03-30 17:32:09.536027, init, 
2023-03-30 17:32:09.539095, lstn_reset,  2 
2023-03-30 17:32:21.639373, lstn_reset,  2 
2023-03-30 17:32:33.739668, lstn_reset,  2 
2023-03-30 17:32:45.840030, lstn_reset,  2 
2023-03-30 17:32:57.940402, lstn_reset,  2 
2023-03-30 17:33:09.940618, flt, 
2023-03-30 17:33:09.940660, flt, 
2023-03-30 17:33:09.940683, init, 
2023-03-30 17:33:10.041885, lstn_reset,  3 
2023-03-30 17:33:22.142157, lstn_reset,  3 
2023-03-30 17:33:34.242529, lstn_reset,  3 
2023-03-30 17:33:46.342890, lstn_reset,  3 
2023-03-30 17:33:58.355073, lstn_reset,  3 
2023-03-30 17:34:10.355191, flt, 
2023-03-30 17:34:10.355232, flt, 
2023-03-30 17:34:10.355253, init, 
2023-03-30 17:34:10.385278, lstn_reset,  4 
2023-03-30 17:34:22.485573, lstn_reset,  4 
2023-03-30 17:34:34.585933, lstn_reset,  4 
2023-03-30 17:34:46.686293, lstn_reset,  4 
2023-03-30 17:34:58.786686, lstn_reset,  4 
2023-03-30 17:35:10.786903, flt, 
2023-03-30 17:35:10.786944, flt, 
2023-03-30 17:35:10.786967, init, 
2023-03-30 17:35:10.888089, lstn_reset,  5 
2023-03-30 17:35:22.988383, lstn_reset,  5 
2023-03-30 17:35:35.088737, lstn_reset,  5 
2023-03-30 17:35:47.189101, lstn_reset,  5 
2023-03-30 17:35:59.289488, lstn_reset,  5 
2023-03-30 17:36:11.289705, flt, 
2023-03-30 17:36:11.289746, flt, 
 

I tried adding port 319/320 explicitly, to no avail. I tried adding mcast explicitly , to no luck. i

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.