Re: netstat output issue

On Thu, Feb 28, 2008 at 02:18:45PM -0800, Barney Cordoba wrote:
When using bridging, netstat apparently can only
display 5 characters, so "bridge" is shown as the
route. If you have multiple bridges defined, you'd
have no way of knowing which bridge was being
specified.

A workaround is to rename your interfaces,

ifconfig bridge0 name b0
ifconfig bridge1 name b1
...

It would be nice to fix netstat too.


Andrew
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: if_bridge crash
    ... I use this script to set up the bridge: ... ifconfig bridge0 addm vr0 addm tap0 up ... confused and managed to ignore the pcb_onfault marker left by copyout. ...
    (freebsd-current)
  • Re: if_bridge crash
    ... I use this script to set up the bridge: ... ifconfig bridge0 addm vr0 addm tap0 up ... confused and managed to ignore the pcb_onfault marker left by copyout. ...
    (freebsd-current)
  • Re: Adding interfaces to bridge0
    ... I have benn using qemu to roll a windows XP machine, ... I closed qemu and tried to set up the bridge manually. ... ifconfig bridge0 addm rl0 addm tap0 up ...
    (freebsd-questions)
  • if_bridge crash
    ... I've been using if_bridge and if_tap to join various qemu virtual ... I use this script to set up the bridge: ... ifconfig bridge0 addm vr0 addm tap0 up ... As far as I can see, the bridge code is calling copyout with a mutex ...
    (freebsd-current)
  • if_bridge problem
    ... Suddenly I can no longer create a bridge. ... I use it with qemu and ... ifconfig bridge0 create ...
    (freebsd-current)