Sorry about my late reply, I was away for a while.
I've fixed that. It was quite trivial but sometimes trivial issues make
you get stuck for a while. :-/
ifconfig_bge0="up"
ifconfig_bge1="up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport bge0 laggport bge1
10.0.0.56/26"
ifconfig_lagg0_alias_0="inet 10.0.0.40 netmask 255.255.255.255"
ifconfig_lagg0_alias_1="inet 10.0.0.41 netmask 255.255.255.255"
ifconfig_lagg0_alias_2="inet 10.0.0.42 netmask 255.255.255.255"
ifconfig_lagg0_alias_3="inet 10.0.0.43 netmask 255.255.255.255"
ifconfig_lagg0_alias_4="inet 10.0.0.44 netmask 255.255.255.255"
ifconfig_lagg0_alias_5="inet 10.0.0.45 netmask 255.255.255.255"
ifconfig_lagg0_alias_6="inet 10.0.0.46 netmask 255.255.255.255"
ifconfig_lagg0_alias_7="inet 10.0.0.47 netmask 255.255.255.255"
I thought that the first two lines wouldn't be necessary as the
"cloned_interface" parameter would have done the job. I was wrong.
Without specifying "up" the lagg0 interface comes up but not the
physical interfaces.
Now everything works well:
bge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
ether 00:14:5e:80:8a:c0
media: Ethernet autoselect (100baseTX
<full-duplex,flowcontrol,rxpause,txpause>)
status: active
bge1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
ether 00:14:5e:80:8a:c0
media: Ethernet autoselect (100baseTX
<full-duplex,flowcontrol,rxpause,txpause>)
status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
inet6 ::1 prefixlen 128
inet 127.0.0.1 netmask 0xff000000
nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE>
ether 00:14:5e:80:8a:c0
inet 10.0.0.56 netmask 0xffffffc0 broadcast 10.0.0.63
inet 10.0.0.40 netmask 0xffffffff broadcast 10.0.0.40
inet 10.0.0.41 netmask 0xffffffff broadcast 10.0.0.41
inet 10.0.0.42 netmask 0xffffffff broadcast 10.0.0.42
inet 10.0.0.43 netmask 0xffffffff broadcast 10.0.0.43
inet 10.0.0.44 netmask 0xffffffff broadcast 10.0.0.44
inet 10.0.0.45 netmask 0xffffffff broadcast 10.0.0.45
inet 10.0.0.46 netmask 0xffffffff broadcast 10.0.0.46
inet 10.0.0.47 netmask 0xffffffff broadcast 10.0.0.47
media: Ethernet autoselect
status: active
laggproto failover
laggport: bge1 flags=0<>
laggport: bge0 flags=5<MASTER,ACTIVE>
Sorry for bothering you guys.
Hope this would save some time to someone else.
Cheers.
On Fri, 2011-11-18 at 13:37 +0100, Damien Fleuriot wrote:
> On 11/18/11 8:09 AM, Snoop wrote:
> > Does anyone know if it's possible to configure lagg for network
> > redundancy on a FreeBSD server containing jails? I'm having problems
> > with that. I couldn't found much around therefore I'm not even sure it's
> > "doable".
> >
> > Thanks in advance, any tip will be appreciated.
> >
>
>
> Show your ifconfig output, I'm curious about how you configure your lagg
>
> Also please post your uname -a output and rc.conf
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
--
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu' IMAP, POP3 e SMTP
autenticato? GRATIS solo con Email.it http://www.email.it/f
Sponsor:
Conto Arancio al 4,20%. Zero spese e massima liberta', aprilo in due minuti!
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=11919&d=24-11
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
