Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 May 2011 20:07:14 +0200
From:      Frank Razenberg <frank@zzattack.org>
To:        freebsd-virtualization@freebsd.org
Subject:   Re: epair not reachable outside host
Message-ID:  <4DD40AD2.9000602@zzattack.org>
In-Reply-To: <E5981B2D-A4D3-4BED-BB27-F715DAC25B5B@lists.zabbadoz.net>
References:  <4DD3F6AF.6070503@zzattack.org> <E5981B2D-A4D3-4BED-BB27-F715DAC25B5B@lists.zabbadoz.net>

next in thread | previous in thread | raw e-mail | index | archive | help
As requested

[root@ /root]# ifconfig -a
em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 
mtu 1500
     
options=219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC>
     ether bc:ae:c5:27:ae:57
     media: Ethernet autoselect (1000baseT <full-duplex>)
     status: active
em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 
mtu 1500
     
options=219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC>
     ether bc:ae:c5:27:ae:57
     media: Ethernet autoselect (1000baseT <full-duplex>)
     status: active
usbus0: flags=10001<UP> metric 0 mtu 0
usbus1: flags=10001<UP> metric 0 mtu 0
usbus2: flags=10001<UP> metric 0 mtu 0
usbus3: flags=10001<UP> metric 0 mtu 0
usbus4: flags=10001<UP> metric 0 mtu 0
usbus5: flags=10001<UP> metric 0 mtu 0
usbus6: flags=10001<UP> metric 0 mtu 0
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
     options=3<RXCSUM,TXCSUM>
     inet6 fe80::1%lo0 prefixlen 64 scopeid 0xa
     inet6 ::1 prefixlen 128
     inet 127.0.0.1 netmask 0xff000000
     nd6 options=3<PERFORMNUD,ACCEPT_RTADV>
vboxnet0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
     ether 0a:00:27:00:00:00
lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 
0 mtu 1500
     
options=219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC>
     ether bc:ae:c5:27:ae:57
     inet 10.31.45.11 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.13 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.14 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.15 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.16 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.17 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.54 netmask 0xffffff00 broadcast 10.31.45.255
     inet 10.31.45.10 netmask 0xffffff00 broadcast 10.31.45.255
     media: Ethernet autoselect
     status: active
     laggproto lacp
     laggport: em1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
     laggport: em0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
     ether 32:9f:31:8f:6a:1c
     id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
     maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
     root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
     member: lagg0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
             ifmaxaddr 0 port 12 priority 128 path cost 20000
     member: epair0a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
             ifmaxaddr 0 port 14 priority 128 path cost 2000
epair0a: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> 
metric 0 mtu 1500
     ether 02:a6:7d:00:0e:0a


[root@ /root]# arp -an
? (10.31.45.16) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.17) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.20) at 00:1b:21:7d:70:94 on lagg0 expires in 1196 seconds 
[ethernet]
? (10.31.45.54) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.10) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.11) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.13) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.14) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.15) at bc:ae:c5:27:ae:57 on lagg0 permanent [ethernet]
? (10.31.45.1) at 00:24:01:2a:37:52 on lagg0 expires in 1200 seconds 
[ethernet]


[root@ /root]# ndp -n -i bridge0
linkmtu=0, maxmtu=0, curhlim=64, basereachable=30s0ms, reachable=36s, 
retrans=1s0ms
Flags: nud accept_rtadv
[root@ /root]# ndp -n -i epair0a
linkmtu=0, maxmtu=0, curhlim=64, basereachable=30s0ms, reachable=15s, 
retrans=1s0ms
Flags: nud accept_rtadv
[root@ /root]# ndp -n -a
Neighbor                             Linklayer Address  Netif Expire    
S Flags
[root@ /root]#


[root@ /root]# netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            10.31.45.1         UGS        83   625017  lagg0
10.31.45.0/24      link#12            U          11     2393  lagg0
10.31.45.10        link#12            UHS         0       19    lo0
10.31.45.11        link#12            UHS         0       67    lo0
10.31.45.13        link#12            UHS         0        0    lo0
10.31.45.14        link#12            UHS         0        0    lo0
10.31.45.15        link#12            UHS         0        0    lo0
10.31.45.16        link#12            UHS         0        0    lo0
10.31.45.17        link#12            UHS         0        0    lo0
10.31.45.54        link#12            UHS         0    42503    lo0
127.0.0.1          link#10            UH          0        0    lo0

Internet6:
Destination                       Gateway                       
Flags      Netif Expire
::1                               ::1                           
UH          lo0
fe80::%lo0/64                     link#10                       
U           lo0
fe80::1%lo0                       link#10                       
UHS         lo0
ff01:a::/32                       fe80::1%lo0                   
U           lo0
ff02::%lo0/32                     fe80::1%lo0                   
U           lo0


Frank

On 5/18/2011 7:10 PM, Bjoern A. Zeeb wrote:
> On May 18, 2011, at 4:41 PM, Frank Razenberg wrote:
>
>> The combination of VirtualBox 4.0.6 + VIMAGE gave me a lot of kernel panics so yesterday I checked out 8.2-STABLE and VirtualBox 4.0.8. The kernel panics are mostly gone. My problem now is that the epair interface is not reachable from any pc other than the freebsd host. Services on the jail can be accessed from the host but inside the jail no network connectivity seems to work.
>> I've put epair0a and lagg0 on a bridge. This used to work. Is there anything I am missing or is this a bug?
> Someone output of ifconfig -a, arp -an, ndp -n, netstat -rn, ... would
> certainly help.  I am aware of one bug that epair can stop passing packets
> but ETIME currently to look.
>
> /bz
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DD40AD2.9000602>