[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Has there been some major changes to the way interfaces
add arp entries in 3.0 as opposed to 2.9 and less ?
Reason I ask is that it appears for some strange reason
unbeknownst that for some reason the arp cache entries
will not change or appear to be willing to change.
on 2.9 running NAT on inner interface
change hostname.$if on any internal host and translation
Adding of new hosts work fine with new MAC addr added
as expected. Then n ++ works fine with each assigned
a unique ip in the nat.cf and is ok.
However on 3.0
eg: change hostname.$if of any internal host and can
no longer access any services outgoing. Whereas access
on that internal network from inner hosts is ok as expected.
I should mention that I have tried to manually add arp entries
and this fails as well. Now the arp cache refused to add
any more hosts mac address period to the cache. Is this a
feature of 3.0 or does one need a workaround. The 3.0
firewall is running 3.0 stable with updated stable patch
branch. Then if when following this same proceedure I am
unable to either add any more ip mac strings to arp cache
or gw period. Try new ip addr make certain that the pf.rules
reflects the changes and nat.conf is ok. It refuses to
either add manually the new arp entry or absorb by itself
the new pairing.
Anyone have a solution for this?
Sure hope I articulated this well enough.
/* Security is a work in progress - dreamwvr */
# Note: To begin Journey type man afterboot,man help,man hier[.]
// "Who's Afraid of Schrodinger's Cat?" /var/(.)?mail/me \? ;-]