Thanks for the prompt response.
problem is likely a config issues, but docs appear to be sparse and I
can't find much reference to the problem/solution on the 'net; trial
and error really isn't working...
Has this been logged in Ubuntu bug tracker. It would help.
The vtun package is currently unsupported by ubuntu and taken from
the debian universe. There's currently a bug (#148808) in the debian
bug system on vtun's terse documentation.
Yes, most likely brctl is sending request to vtun
and it is crashing.
vtun or brctl? Surely vtun is just connected to the tap0 interface
and brctl sets up the kernel to bridge between that and eth1? I
suppose it only crashes on vtun restart because one (or more) of the
up/down lines are ordered incorrectly. Is it valid to remove/add
interfaces in this order? Would it be valid to just have tap0
sitting there with IP 0.0.0.0 and the bridge set up statically? Is
there any reason why on initial connection setup brctly show shows
"can't get port info: Function not implemented", but on restart it
shows the interfaces correctly?
Sorry for the many questions, just trying to work out how this all
fits together. Thanks again for your quick response.
James
_______________________________________________
Bridge mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/bridge
