On Tue, Nov 24, 2020 at 12:26 AM Tuomo Soini wrote:
>
> That's not quite enough. When dhcp clients want to renew leases they
> need unicast dhcp access to your dns server. You can do that in rules
> with DHCPfwd macro.
>
> DHCPfwd(ACCEPT) lan1ibs:10.215.137.54
>
> Macro will allow traffic to b
On Mon, 23 Nov 2020 23:11:26 +0100
Vieri Di Paola wrote:
> Correct me if I'm wrong, but it seems that a reload is enough (no
> restart needed) because it seems that the 'dhcp' option simply adds
> the udp 67:68 rules on the specified interfaces.
Right. For any rule change reload is always enough
Correct me if I'm wrong, but it seems that a reload is enough (no
restart needed) because it seems that the 'dhcp' option simply adds
the udp 67:68 rules on the specified interfaces. In my case, a
shorewall dump shows this kind rule was generated:
ACCEPT udp -- * * 0.0.0.0/0
On Mon, Nov 23, 2020 at 3:12 PM Simon Matter wrote:
>
> > lan1${IF_LAN}.1 routeback,arp_filter=1,proxyarp=1,dhcp
> > ibs $IF_IBS arp_filter=1,dhcp
>
> What is $IF_IBS? Is it a normal ethernet interface?
Yes, IF_IBS=ibs and IF_LAN=lan where ibs and lan are normal eth
interfaces
> Hi,
>
> I configured dhcrelay so that clients in my "lan1" zone should get IP
> addr. leases from a server in my "ibs" zone.
>
> This is the command I run:
>
> /usr/sbin/dhcrelay -q -i lan.1 10.215.137.54
>
> BTW, a foreground run shows messages such as:
>
> Forwarded BOOTREQUEST for a4:bb:6d:03:
Hi,
I configured dhcrelay so that clients in my "lan1" zone should get IP
addr. leases from a server in my "ibs" zone.
This is the command I run:
/usr/sbin/dhcrelay -q -i lan.1 10.215.137.54
BTW, a foreground run shows messages such as:
Forwarded BOOTREQUEST for a4:bb:6d:03:6d:c9 to 10.215.137
