Topic: IP Tables Help, Device not able to communicate to server

[ramasule]

Sorry for all the questions,

RequestedDeletion how do I remove rules or view them after I set them?

config set WaterTimer service status enabled access public UDPPort 67

I used iptables -L but do not see that service in it,

I'm removing OpenVPN right now.

[guest22]

RequestedDeletion how do I remove rules or view them after I set them?

config set WaterTimer service status enabled access public UDPPort 67

config delete WaterTimer
signal-event remoteaccess-update

I used iptables -L but do not see that service in it,

You should be able to see port 67 being 'open'

[ReetP]

As a note... you shouldn't set iptables rules manually.

Using Charlies suggestion anything configured as a 'service' with a port and the service set to public will have that port automagically opened by SME. The masq templare picks up any ports and creates the relevant iptables rules for you. Saves lots of manual fiddling !

[CharlieBrady]

Remove the openVPN contrib and revert back to plain SME server configuration. If the problem goes away, then work with the openVPN contrib developer to fix the problem with DHCP broadcasts.

The bridge device br0 appears to be relaying DHCP broadcasts, which is being blocked by iptables. SME server base had no need to relay those broadcasts, and has no reason to include iptables rules to allow the broadcasts to be relayed.