Hey Giulio,
Have you had any chance to run the commands I supplied ? I'm curious as to wether you're running the same network on the 1 physical and 1 logical interface, or running 2 different ones, like 192.168.0.0/24 and 192.168.1.0/24. Removing -stable from the cc list so as to not crosspost. On 25 August 2012 13:22, Damien Fleuriot <m...@my.gd> wrote: > In the meantime kindly post: > > > Ifconfig for your igb0 > Netstat -rn > Netstat -aln | grep 22 > > > > On 25 Aug 2012, at 13:18, Damien Fleuriot <m...@my.gd> wrote: > >> I'll get back to you regarding link aggregation when I'm done with groceries. >> >> We use it here in production and it works flawlessly. >> >> >> >> On 25 Aug 2012, at 09:54, Giulio Ferro <au...@zirakzigil.org> wrote: >> >>> No answer, so it seems that link aggregation doesn't really work in freebsd, >>> this may help others with the same problem... >>> >>> I reverted back to one link for management and one for service, and ssh >>> works as it should... >>> >>> >>> On 08/21/2012 11:18 PM, Giulio Ferro wrote: >>>> Scenario : freebsd 9 stable (yesterday) amd64 on HP server with 4 nic (igb) >>>> >>>> 1 nic is connected standalone to the management switch, the 3 other nics >>>> are connected to a switch configured for aggregation. >>>> >>>> If I configure the first nic (igb0) there is no problem, I can operate >>>> as I normally do and sshd functions normally. >>>> >>>> The problems start when I configure the 3 other nics for aggregation: >>>> >>>> in /etc/rc.conf >>>> ... >>>> ifconfig_igb1="up" >>>> ifconfig_igb2="up" >>>> ifconfig_igb3="up" >>>> >>>> cloned_interfaces=lagg0 >>>> ifconfig_lagg0="laggproto lacp laggport igb1 laggport igb2 laggport igb3 >>>> 192.168.12.7/24" >>>> ... >>>> >>>> I restart the server and the aggregation seems to work correctly, in >>>> fact ifconfig returns the correct lagg0 interface with the aggregated >>>> links, the correct protocol (lacp) and the correct ip address and the >>>> status is active. I can ping other IPs on the aggregated link. >>>> >>>> Also the other (standalone) link seems to work correctly. I can ping >>>> that address from other machines, and I can ping other IPs from that >>>> server. >>>> >>>> DNS lookups work ok too I can also use telnet to connect to pop3 >>>> servers so there seems to be no problem on the network stack. >>>> >>>> But if I try to connect to the sshd service on that server, it hangs >>>> indefinitely. On the server I find two sshd processes: >>>> /usr/sbin/sshd >>>> /usr/sbin/sshd -R >>>> >>>> There is no message in the logs. >>>> >>>> If I try to kill sshd (/etc/rc.d/sshd stop) I can't. it just stays there >>>> forever waiting for the pid to die (it never does) >>>> >>>> Even ssh client doesn't seem to work. In fact, if I try to connect to >>>> another server, the ssh client may start to work correctly, then soon >>>> or later it just hangs there forever, and I can't kill it with ctrl-c. >>>> >>>> No firewall is configured, there is nothing else working on this server. >>>> >>>> Thanks for any suggestions... >>>> _______________________________________________ >>>> freebsd-sta...@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >>> >>> _______________________________________________ >>> freebsd-sta...@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
