Re: Routing stops working when we create a new vlan
On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: Routing stops working when we create a new vlan
On 08/06/2015 22:09, Marcelo Gondim wrote: PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 The output of ifconfig and netstat -nr -f inet, before and after you create the new vlan, would be most helpful. Eric Hi Eric, I put the information you requested in PR. Wow, the only difference in the output is the new vlan interface. This is odd. I'm afraid I have no ideas off-hand, and I don't have enough spare cycles to dive in. Best of luck. Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On Fri, Aug 7, 2015 at 4:29 PM, Marcelo Gondim gon...@bsdinfo.com.br wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. []'s Gondim The change to 0 is probably due to not having gateway_enable=YES in rc.conf Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On Fri, Aug 07, 2015 at 05:33:51PM +0300, Andrey V. Elsukov wrote: On 07.08.2015 17:29, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? AFAIR, devd starts some scripts and if you don't have gateway_enable=YES net.inet.ip.forwarding will be reset to zero. And since devd doesn't restart sysctl.conf you lose your gateway. I think this is incorrect behavior. The right way to configure router - use gateway_enable=YES in rc.conf. Changing gateway_enable in rc.conf don't have immediatly effect. Changing gateway_enable and plug interface do unexpectedly effect. Why forwarding controlling not only by /etc/rc.d/routing but also by /etc/rc.d/netif? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 07-08-2015 11:33, Andrey V. Elsukov wrote: On 07.08.2015 17:29, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? AFAIR, devd starts some scripts and if you don't have gateway_enable=YES net.inet.ip.forwarding will be reset to zero. And since devd doesn't restart sysctl.conf you lose your gateway. The right way to configure router - use gateway_enable=YES in rc.conf. I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. This seems strange, are you sure? Problem solved using gateway_enable = YES in /etc/rc.conf. But I still think it does wrong. Why to create a vlan I need to have this parameter configured in rc.conf? Or why it needs to change net.inet.ip.forwarding? []'s Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. []'s Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 07.08.2015 17:29, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? AFAIR, devd starts some scripts and if you don't have gateway_enable=YES net.inet.ip.forwarding will be reset to zero. And since devd doesn't restart sysctl.conf you lose your gateway. The right way to configure router - use gateway_enable=YES in rc.conf. I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. This seems strange, are you sure? -- WBR, Andrey V. Elsukov signature.asc Description: OpenPGP digital signature
Re: Routing stops working when we create a new vlan
On Fri, Aug 7, 2015 at 9:54 AM, Marcelo Gondim gon...@bsdinfo.com.br
wrote:
But I still think it does wrong. Why to create a vlan I need to have this
parameter configured in rc.conf? Or why it needs to change
net.inet.ip.forwarding?
Because that is what the directions for configuring a default gateway
state, and the directions are based off of code behavior.
/etc/rc.d/routing:
if checkyesno gateway_enable; then
ropts_init inet
echo -n ' gateway=YES'
${SYSCTL} net.inet.ip.forwarding=1 /dev/null
else
${SYSCTL} net.inet.ip.forwarding=0 /dev/null
fi
--
Adam
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 8/7/2015 10:29 AM, Marcelo Gondim wrote: On 07-08-2015 10:16, Andrey V. Elsukov wrote: On 07.08.2015 01:57, Marcelo Gondim wrote: For all work again I need to restart the router. I don't know if I could correctly explain the problem. Do you have gateway_enable=YES in your /etc/rc.conf? I have net.inet.ip.forwarding=1 but when I create a new vlan, the system is changing to: net.inet.ip.forwarding=0. Why? I try to go back to the value 1 and the system does not return to work. Only back to work if I restart the system. devd. As suggested, have gateway_enable=YES in rc.conf so interface creations dont mess that up. I am not sure why devd wants/needs to do this, but it does. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 06-08-2015 21:03, Eric van Gyzen wrote: On 8/6/15 5:57 PM, Marcelo Gondim wrote: Hi all, Let me illustrate a network topology, to tell where the problem occurs: PC station: 192.168.8.253/24 (FreeBSD 10.2-PRERELEASE) Router: 192.168.8.177/24 and 10.254.215.1/24 (FreeBSD 10.2-RC2) router(CPE): 10.254.215.188/24 (a customer) From Router: === # ifconfig vlan201 vlan201: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=103RXCSUM,TXCSUM,TSO4 ether 70:71:bc:87:31:2d inet 10.254.215.1 netmask 0xff00 broadcast 10.254.215.255 inet6 fe80::7271:bcff:fe87:312d%vlan201 prefixlen 64 scopeid 0x1a nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 201 parent interface: em0 From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes 64 bytes from 10.254.215.188: icmp_seq=0 ttl=127 time=1.012 ms 64 bytes from 10.254.215.188: icmp_seq=1 ttl=127 time=0.864 ms 64 bytes from 10.254.215.188: icmp_seq=2 ttl=127 time=1.084 ms 64 bytes from 10.254.215.188: icmp_seq=3 ttl=127 time=1.618 ms 64 bytes from 10.254.215.188: icmp_seq=4 ttl=127 time=1.006 ms --- 10.254.215.188 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.864/1.117/1.618/0.261 ms It works perfectly. Now I'm going on the router and I just create a new vlan 202. From Router: === # ifconfig vlan202 create # At that moment my PC station stops to ping the IP 10.254.215.188. From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes --- 10.254.215.188 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss For all work again I need to restart the router. I don't know if I could correctly explain the problem. PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 The output of ifconfig and netstat -nr -f inet, before and after you create the new vlan, would be most helpful. Eric Hi Eric, I put the information you requested in PR. []'s Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Routing stops working when we create a new vlan
On 8/6/15 5:57 PM, Marcelo Gondim wrote: Hi all, Let me illustrate a network topology, to tell where the problem occurs: PC station: 192.168.8.253/24 (FreeBSD 10.2-PRERELEASE) Router: 192.168.8.177/24 and 10.254.215.1/24 (FreeBSD 10.2-RC2) router(CPE): 10.254.215.188/24 (a customer) From Router: === # ifconfig vlan201 vlan201: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=103RXCSUM,TXCSUM,TSO4 ether 70:71:bc:87:31:2d inet 10.254.215.1 netmask 0xff00 broadcast 10.254.215.255 inet6 fe80::7271:bcff:fe87:312d%vlan201 prefixlen 64 scopeid 0x1a nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 201 parent interface: em0 From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes 64 bytes from 10.254.215.188: icmp_seq=0 ttl=127 time=1.012 ms 64 bytes from 10.254.215.188: icmp_seq=1 ttl=127 time=0.864 ms 64 bytes from 10.254.215.188: icmp_seq=2 ttl=127 time=1.084 ms 64 bytes from 10.254.215.188: icmp_seq=3 ttl=127 time=1.618 ms 64 bytes from 10.254.215.188: icmp_seq=4 ttl=127 time=1.006 ms --- 10.254.215.188 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.864/1.117/1.618/0.261 ms It works perfectly. Now I'm going on the router and I just create a new vlan 202. From Router: === # ifconfig vlan202 create # At that moment my PC station stops to ping the IP 10.254.215.188. From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes --- 10.254.215.188 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss For all work again I need to restart the router. I don't know if I could correctly explain the problem. PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 The output of ifconfig and netstat -nr -f inet, before and after you create the new vlan, would be most helpful. Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Routing stops working when we create a new vlan
Hi all, Let me illustrate a network topology, to tell where the problem occurs: PC station: 192.168.8.253/24 (FreeBSD 10.2-PRERELEASE) Router: 192.168.8.177/24 and 10.254.215.1/24 (FreeBSD 10.2-RC2) router(CPE): 10.254.215.188/24 (a customer) From Router: === # ifconfig vlan201 vlan201: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=103RXCSUM,TXCSUM,TSO4 ether 70:71:bc:87:31:2d inet 10.254.215.1 netmask 0xff00 broadcast 10.254.215.255 inet6 fe80::7271:bcff:fe87:312d%vlan201 prefixlen 64 scopeid 0x1a nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 201 parent interface: em0 From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes 64 bytes from 10.254.215.188: icmp_seq=0 ttl=127 time=1.012 ms 64 bytes from 10.254.215.188: icmp_seq=1 ttl=127 time=0.864 ms 64 bytes from 10.254.215.188: icmp_seq=2 ttl=127 time=1.084 ms 64 bytes from 10.254.215.188: icmp_seq=3 ttl=127 time=1.618 ms 64 bytes from 10.254.215.188: icmp_seq=4 ttl=127 time=1.006 ms --- 10.254.215.188 ping statistics --- 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.864/1.117/1.618/0.261 ms It works perfectly. Now I'm going on the router and I just create a new vlan 202. From Router: === # ifconfig vlan202 create # At that moment my PC station stops to ping the IP 10.254.215.188. From PC station (192.168.8.253): === # ping -c 5 10.254.215.188 PING 10.254.215.188 (10.254.215.188): 56 data bytes --- 10.254.215.188 ping statistics --- 5 packets transmitted, 0 packets received, 100.0% packet loss For all work again I need to restart the router. I don't know if I could correctly explain the problem. PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202144 []'s Gondim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
