On 1/3/15 1:06 PM, Mike Tancsa wrote:
> On 1/3/2015 9:19 AM, Paul Thornton wrote:
>> Hi,
>>
>> I can also replicate this behaviour on 10.1-RELEASE by simply creating
>> an additional vlan interface. It affects IPv4 and IPv6 forwarding.
>
> Strange, I dont see that on RELENG_10
>
> 0{marble}# ifc
Hi,
On 03/01/2015 18:06, Mike Tancsa wrote:
do you set forwarding via just /etc/sysctl.conf or in /etc/rc.conf via
ipv6_gateway_enable and gateway_enable. I seem to recall some discussion
about there being a difference. Perhaps devd is calling something that
then fiddles with the setting ignor
On 1/3/2015 9:19 AM, Paul Thornton wrote:
Hi,
I can also replicate this behaviour on 10.1-RELEASE by simply creating
an additional vlan interface. It affects IPv4 and IPv6 forwarding.
Strange, I dont see that on RELENG_10
0{marble}# ifconfig em2 up
0{marble}# ifconfig em2.3 create 1.1.1.2/24
Hi,
I can also replicate this behaviour on 10.1-RELEASE by simply creating
an additional vlan interface. It affects IPv4 and IPv6 forwarding.
This is taken from a test setup of FreeBSD boxes running Quagga as BGP
routers - but with a default GENERIC kernel. This machine has 2x ixgbe,
4x ig
Hi,
I have been seeing strange behavior of my system lately. After creating new
interface the system variable net.inet.ip.forwarding becomes "0".
E.g. manually load if_ral kernel module, then rel0 interface appears and
net.inet.ip.forwarding becomes "0".
Previously this happened when I att
Hi, list.
Server works as router for small network and some services in the jails. When I
connect Android-based smartphone and attempt to use USB Tethering, the
net.inet.ip.forwarding becomes 0 and I must change it to 1 every time.
Is this normal behavior?
FreeBSD server.local 10.1-STABLE Fre
