Send list mailing list submissions to
        list <at> tagcose.com

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.tagcose.com/mailman/listinfo/list
or, via email, send a message with subject or body 'help' to
        list-request <at> tagcose.com

You can reach the person managing the list at
        list-owner <at> tagcose.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of list digest..."


Today's Topics:

   1. Re: list Digest, Vol 56, Issue 1 (James Dugger)
   2. Re: Can't access proxmox web UI of TAgCoSe after  configuring
      vmbr's (Eric Shubert)


----------------------------------------------------------------------

Message: 1
Date: Mon, 31 Dec 2012 01:27:36 -0700
From: James Dugger <james.dugger <at> gmail.com>
To: list <at> tagcose.com
Subject: Re: [tagcose] list Digest, Vol 56, Issue 1
Message-ID:
        <CAOXWiHhut0DyNW-2tQ=BTW8UX1JO96nLK2NyojCcJbBi8-RYrA <at> mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I have networking up again.  I had to change the eth0 to static and not
bridge it with vmbr0.  Regarding the ip addressing from the tutorial, I
can't seem to get this to work?

   - vmbr0 - IP is *192.168.100.1*, subnet is *255.255.255.0*, gateway is *
   192.168.100.2*, bridged to port eth0.
   - vmbr1 - IP is *169.254.1.1*, subnet is *255.255.255.255*, no gateway,
   bridged to port eth1.
   - vmbr2 - IP is *192.168.101.1*, subnet is *255.255.255.0*, gateway is *
   192.168.101.2*, bridged to port eth2.

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.tagcose.com/mailman/private/list/attachments/20121231/1290d3df/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 31 Dec 2012 10:17:48 -0700
From: Eric Shubert <ejs <at> shubes.net>
To: Tagcose General List <list <at> tagcose.com>
Subject: Re: [tagcose] Can't access proxmox web UI of TAgCoSe after
        configuring vmbr's
Message-ID: <50E1C8BC.9030809 <at> shubes.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 12/31/2012 01:27 AM, James Dugger wrote:
> Ihave networking up again.  I hadto change the eth0 to static and not
> bridge it with vmbr0. Regarding the ip addressing from the tutorial,I
> can't seem to getthis to work?
>
>   * vmbr0 - IP is *192.168.100.1*, subnet is *255.255.255.0*, gateway is
>     *192.168.100.2*, bridged to port eth0.
>   * vmbr1 - IP is *169.254.1.1*, subnet is *255.255.255.255*, no
>     gateway, bridged to port eth1.
>   * vmbr2 - IP is *192.168.101.1*, subnet is *255.255.255.0*, gateway is
>     *192.168.101.2*, bridged to port eth2.
>
> James
>
> _______________________________________________

Hey James,

Glad to see you on the list, and building a tagcose server! I've been
*very* busy lately, so please be patient with list activity. We'll get
to things as we can. Hope to see you at the tagcose meetings too
occasionally. We meet on the 2nd Sat of each month at UAT in room 208.
10am-4pm or so.

I had a little trouble my first time with PVE networking as well. My
best success has been to use the web interface to configure networking,
and let PVE handle things the way it does. I expect I'll learn much of
what's going on under the covers eventually, but debian is still a
little new to me as well, so I still have a bit of a learning curve
ahead (as usual).

I've taken a look at the configuration I have (I have 6 of these
presently in production), and here's what I have in interfaces:
# network interface settings
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto eth2
iface eth2 inet manual

auto vmbr0
iface vmbr0 inet static
        address  192.168.130.1
        netmask  255.255.255.0
        gateway  192.168.130.2
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet static
        address  169.254.130.1
        netmask  255.255.255.255
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

auto vmbr2
iface vmbr2 inet static
        address  192.168.131.1
        netmask  255.255.255.0
        bridge_ports none
        bridge_stp off
        bridge_fd 0

auto vmbr3
iface vmbr3 inet static
        address  192.168.132.1
        netmask  255.255.255.0
        bridge_ports eth2
        bridge_stp off
        bridge_fd 0

auto vmbr4
iface vmbr4 inet static
        address  192.168.252.1
        netmask  255.255.255.0
        bridge_ports none
        bridge_stp off
        bridge_fd 0

auto vmbr5
iface vmbr5 inet static
        address  192.168.253.1
        netmask  255.255.255.0
        bridge_ports none
        bridge_stp off
        bridge_fd 0

The .130. .131. and .132. networks correspond to IPCop green, DMZ and
Blue respectively. These will be subnet numbers that you choose which
are appropriate for your host. The IPCop VM has 4 network interfaces:
green/LAN, red/WAN, orange/DMZ and blue/WIFI which correspond to vmbr0-3
respectively. The IPCop's addresses all (except red) end in .2 for
consistency.

I hope this gets you back in line.

Now that I look at this, the vmbr2,3 host addresses should probably be
169.254 numbers. There's no reason why the DMZ and WIFI subnets should
have direct access to the host, and it would be more secure if they didn't.

As the wiki is a work in progress, anything you can suggest (or do)
regarding improvements there will be welcome.

Thanks for keeping us abreast of your progress.

--
-Eric 'shubes'

--
-Eric 'shubes'


------------------------------

_______________________________________________
list mailing list
list <at> tagcose.com
https://lists.tagcose.com/mailman/listinfo/list


End of list Digest, Vol 57, Issue 1
***********************************