[lug] Network interconnection question....

[John Hernandez]

Ah, yes, that makes sense.  tun0 is a layer 3 device - it doesn't speak
Ethernet.  You can bridge using a tap0 interface, so it may be worth
exploring if the IBM s390 emulator can be configured to support a tap
tunnel.

On 6/29/07, Dave Pitts <dpitts at cozx.com> wrote:
>
> >
> > If the goal is to make the emulator reachable on 205.250.10.5, I think
> you
> > can achieve that by bridging eth0 and tun0, then assigning the
> > 205.250.10.5IP to the IBM s390 emulator.  You probably won't need the
> > 10.x addresses to accomplish this.  You might also need to move your
> > 205.250.10.4 IP to the new br0 interface, rather than assigning it to
> eth0,
> > but I'm not sure about that.
> >
> > brctl addif br0 eth0
> > brctl addif br0 tun0
> > ifconfig br0 up
> >
> I've tried this and you can't assign the tunnel device to the bridge.
> You get:
>
> can't add tun0 to bridge br0: Invalid argument
>
> > On 6/27/07, Dave Pitts <dpitts at cozx.com> wrote:
> >
> >> >
> >> > Hello:
> >> >
> >> > I've a got an internal (to the Linux box) network question. First the
> >> > scenario:
> >> >
> >> > 1. I've got a tunnel interface running that connects to an emulator
> >> > (Hercules)
> >> >    that is running the IBM s390 Linux.
> >> >
> >> > 2. A Linux host with a single ethernet connection.
> >> >
> >> > All is well so far. Now I want to configure the network (I don't have
> >> > sufficient network addresses to subnet) such that the ethernet
> interface
> >> > has
> >> > two IP addresses and bridge (or whatever) to the tunnel interface.
> >> >
> >> > To look like this:
> >> >
> >> >
> >> >         +----------------------------------+
> >> >         |
> >> >         |               +---- local services
> >> >         |               |
> >> >         |               |
> >> > --------+---- eth0 -----+
> >> >         |               |
> >> >         |               tun0
> >> >         |               |
> >> >         |               +---- Hercules (s390 Linux)
> >> >         |
> >> >         +-----------------------------------+
> >> >
> >> > The tun0 interface addresses are configured with non-routable IP
> address:
> >> >
> >> > 10.90.1.1 <-> 10.90.1.2
> >> >
> >> > And the Ethernet (for example) to have the addresses:
> >> >
> >> > 205.250.10.4 and 205.250.10.5
> >> >
> >> > Where the second eth0 address connects to the 10.90.1.0 network.
> >> > And the first ethernet address works normally.
> >> >
> >> > I've tried several things without success. Any Ideas???
> >> >
>
> --
> Dave Pitts             PULLMAN: Travel and sleep in safety and comfort.
> dpitts at cozx.com        My other RV IS a Pullman (Colorado Pine).
> http://www.cozx.com/~dpitts
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20070630/5faa1d1e/attachment.html>