Recent Posts

Pages: 1 ... 8 9 [10]
91
Users / Re: Svn broken?
« Last post by Govo on January 23, 2016, 09:52:13 pm »
Cool. No problem at all. Is our username and passwords still the same?

Cheers
Govo
92
Users / Re: Svn broken?
« Last post by posde on January 23, 2016, 08:04:06 pm »
govo,

thank you for your generous offer.

We went ahead and gone to git(hub). https://git.linuxmce.org
93
Users / Re: Svn broken?
« Last post by Govo on January 23, 2016, 06:32:02 pm »
Hi Posde

what's required in hosting a Svn system, my assumption is that when a ticket is raised in relation to a bug, the ticket is then assigned to a developer, where the developer updates the ticket with information regarding the fix, the  ticket holds all information as its updated. each issue or  bug is assigned to an equine record or ID.

If this is the case, then I can build it over the next three weeks, if  you could provide exactly what's required for such system that would be great, here's a screenshot of a site  I quickly put together locally on my home system just now . modifications can be done to to whats required


https://www.dropbox.com/s/7fdd9aiuog3diec/Screenshot%20from%202016-01-23%2017%3A22%3A32.png?dl=0

https://www.dropbox.com/s/x16qpgvyatgyald/Screenshot%20from%202016-01-23%2017%3A21%3A56.png?dl=0

Let know if you require such website and I will work on it.

Cheers
Govo


94
Users / Re: EIB segmentation fault
« Last post by posde on January 22, 2016, 10:26:36 am »
Is it save to say that the system didn't start as a 1404 system but got upgraded from a different version?

95
Users / Re: To 'bridge' or not to 'bridge'
« Last post by ardirtbiker on January 22, 2016, 01:27:49 am »
Thanks Alblasco,

Here is my /etc/network/interfaces file:
Code: [Select]
# Activating interfaces
auto eth0 br0 lo

#####
# Loopback interface
#####
iface lo inet loopback

#####
# IPv4 network interfaces
#####

# --- External NIC ---
iface eth0 inet dhcp
pre-up sysctl -q -e -w  net.ipv6.conf.eth0.disable_ipv6=1
up /sbin/ifconfig eth0 up
down /sbin/ifconfig eth0 down

# --- Internal NIC ---
iface eth1 inet manual
pre-up sysctl -q -e -w net.ipv6.conf.eth1.disable_ipv6=1
up /sbin/ifconfig eth1 up
down /sbin/ifconfig eth1 down
#####

# --- Wireless NIC ---
iface wlan0 inet manual

# --- Bridge ---
iface br0 inet static
address 192.168.80.1
network 192.168.80.0
netmask 255.255.255.0
broadcast 192.168.80.255
gateway 192.168.1.254
pre-up /usr/sbin/hostapd -B /etc/hostapd/hostapd.conf
bridge_ports eth1 wlan0
dns-nameservers 192.168.1.254 8.8.8.8
dns-search LinuxMCE.local
down /sbin/ifconfig br0 down

Here is /etc/default/isc-dhcp-server:
Code: [Select]
INTERFACES="br0"
and here is the output of iptables -vnL
Code: [Select]
Chain INPUT (policy DROP 3 packets, 116 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x3F/0x29
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x3F/0x3F
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x3F/0x00
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x06/0x06
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x03/0x03
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x11/0x01
    0     0 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x3F/0x37
    0     0 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            mark match 0x1
    2    92 ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0            /* Allow_Loopback */
  492 57564 ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED /* Allow_Established */
    0     0 ACCEPT     udp  --  eth0   *       0.0.0.0/0            0.0.0.0/0            /* Allow_DHCP */
    6  1616 ACCEPT     udp  --  br0    *       0.0.0.0/0            0.0.0.0/0            /* Allow_DHCP */
    0     0 ACCEPT     udp  --  eth0   *       0.0.0.0/0            0.0.0.0/0            /* Allow_DHCP */
    2   120 ACCEPT     tcp  --  br0    *       192.168.80.0/24      0.0.0.0/0            /* Allow_Local_Network */

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     all  --  lo     lo      0.0.0.0/0            0.0.0.0/0            /* Allow_Loopback */
    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED /* Allow_Established */
    4  2563 ACCEPT     tcp  --  br0    *       192.168.80.0/24      0.0.0.0/0            /* Allow_Local_Network */

Chain OUTPUT (policy ACCEPT 317 packets, 45260 bytes)
 pkts bytes target     prot opt in     out     source               destination         
       



Let me know if you need anything else.

Dennis
96
Users / Re: To 'bridge' or not to 'bridge'
« Last post by Alblasco1702 on January 22, 2016, 12:37:40 am »
Hello Dennis,

it isn't yet supported to bridge but to  help you further to test this.
I need some information from you.
- /etc/network/interfaces
- /etc/default/isc-dhcp-server
- iptables -vnL
97
Users / Re: EIB segmentation fault
« Last post by phenigma on January 22, 2016, 12:08:54 am »
When I check the database, the ID285 is assigned to CORE, template 7, with the internal IP.

That is very, very wrong.  Your core device should be #1.  If it has added another then something went very wrong at some point.  Best I can figure is that somehow portions of firstboot were re-run. 

J.
98
Users / To 'bridge' or not to 'bridge'
« Last post by ardirtbiker on January 21, 2016, 05:28:59 pm »
In lmce 1204 and 1404, bridging appears to have changed within the linux kernel.   In 1004 i had bridged eth1 (internal NIC) with wlan0 (AP) following  the instructions here:http://wiki.linuxmce.org/index.php/Access_Point
After changing 'eth1' in the firewall to 'br0' (the bridge interface), verything worked without a hitch.

In 1204 and 1404, when the bridge is set up the same, the MDs cannot access the nfs storage drives, but my wifi devices work fine. 

Is there a better route to take other than bridging?     Is there something else I need to do to the firewall?   

Some internet sources suggest installing ebtables and set up some rules there and add other rules to iptables.   I dont quite grasp firewalls  and am stuck.

Any suggestions will be greatly appreciated.

Dennis
99
Users / Re: EIB segmentation fault
« Last post by brononius on January 21, 2016, 05:17:55 pm »
I've done a lot (except rebooting in timeto know when it started to fail)...

Main changes of last days:
   apt-get upgrades
   apt-get dist-upgrade
   dpkg -i libpthsem20_2.0.8_i386.deb
   apt-get remove bcudsk (and some reinstalls)
   apt-get install linuxmce-eib-eibd
   played around with the eggtimer
   Tried the qorbiter (and removed it), this was device ID 284

But I never touched the /etc/pluto.conf file.
I had some mayor issues after the dist-upgrade (?), my second network card didn't came up after the reboot.
I'm using VMWare, and in /etc/network/interfaces, I had 2 times an eth1? With default ip 192.168.80.1 and my real ip 192.168.111.1. After removing the 80 with 111, ubuntu started to boot properly.

When I check the database, the ID285 is assigned to CORE, template 7, with the internal IP.
100
Users / Re: EIB segmentation fault
« Last post by phenigma on January 21, 2016, 04:16:30 pm »
Um.  Now I'm curious.  What did you do to cause pluto.conf to be re-written with PK_Device=285?  It should set that based on the Core Device and nothing else.

J.
Pages: 1 ... 8 9 [10]