devil-linux-discuss — General Mailing List for all discussions

[Devil-Linux-discuss] Mounted Drives

[James K. <jke...@gm...>]

Hello.

I am currently using a computer that boots Devil Linux from CD. I would like
to know if there is a way to save-config mounted devices such as USB drives
and Hard Drives. I can mount both devices within Devil Linux without issue,
however I am unable to save those mounts using save-config.

Is there a way this can be accomplished? Any help is welcome. Thank you.

-- 
James E. Kessler

Re: [Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Aaron M. <aa...@uw...>]

Hi Marcello,

Thank you - starting to have some progress.  Your suggestion did not work 
directly, but it did remind me to just try adding the address separately too 
see what the results were.  I was able to create a vlan274:0 interface and 
assign it the second IP needed, and both IPs were reachable on the network.

The difference is that when binding the second IP as a sub-interface, it's 
already in that vlan, so adding a VLANID is unnecessary. So in the second 
file, I commented out the VLANID and otherwise went with your suggestion - 
that worked!  Thank you for your help - this makes a migration project MUCH 
easier. :)

-- 

Aaron McDonnell
Network Administrator
Network Operations Centre
University of Western Ontario
Tel: 519-661-2111 ext. 86558

On 13/01/2010 1:42 PM, Marcello Desantis wrote:
> Il giorno mer, 13/01/2010 alle 12.43 -0500, Aaron McDonnell ha scritto:
>> In the /etc/sysconfig/nic directory, there are a number of interface config
>> files for the various vlans involved.  What I tried this time was to copy
>> the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed
>> the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the
>> IP address to the second IP I needed in that VLAN.
>
> I would try the following:
>
> 1st file: ifcfg-vlan274
> DEVICE=eth0
>
> 2nd file: ifcfg-vlan274:0
> DEVICE=vlan274:0
>
> Note that the former points to the physical device while the latter
> points to the "vlan" device.
>
> This is because the fist file is a "vlan definition" and the DEVICE
> value is used together with the VLANID value as parameter to the vconfig
> command in order to define a NEW vlan on the specified physical nic. The
> second file is a "standard alias definition" (regardless of the
> interface type you're defining the alias on) and the DEVICE value is
> used as a parameter to the ifconfig command. And the command you want
> the system to execute for the second IP is something like:
> ifconfig vlan274:0 $IPADRR netmask $NETMASK broadcast $BROADCAST
>
> Hope it helps.
>
> Ciao
>
> Marcello
>
>
>>
>> When I restarted the network services, it again overwrote the first IP with
>> the second, and the second IP behaved oddly and I could not attach to it.  I
>> reverted back to the single IP in VLAN 274.  Any other ideas?
>>
>> --
>>
>> Aaron McDonnell
>> Network Administrator
>> Network Operations Centre
>> University of Western Ontario
>> Tel: 519-661-2111 ext. 86558
>>
>> On 13/01/2010 12:26 PM, Heiko Zuerker wrote:
>>> Quoting Aaron McDonnell<aa...@uw...>:
>>>
>>>> Hi All,
>>>>
>>>> I'm wondering if anyone knows of a way to add a second IP in the same subnet
>>>> to a tagged VLAN interface?
>>>>
>>>> We use Devil Linux to implement a Quarantine network on campus, currently
>>>> provided by two boxes.  I would like to consolidate the boxes by merging one
>>>> into the other, and easiest way to migrate things would be to give the
>>>> primary box the IPs of the secondary in addition to its own.  Both boxes
>>>> have around 30+ networks them via tagged interfaces.
>>>>
>>>> Initially, I tried this by taking the interface and using the technique
>>>> you'd use on a normal one, eg:
>>>>
>>>> cp ifcfg-vlan274 ifcfg-vlan274:1
>>>>
>>>> And I edited to :1 version to have the second IP.  This only seemed to
>>>> overwrite the first interface though when I restarted network services.  Is
>>>> there another way to do this?
>>>
>>> As far as I recall you have to edit the file and change the line:
>>> DEVICE=eth2
>>> to
>>> DEVICE=eth2:1
>>>
>>> The name of the file doesn't provide any functionality, the content if
>>> what counts.
>>>
>>> In addition to that, uou may have to start counting at 0.
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Verizon Developer Community
>> Take advantage of Verizon's best-in-class app development support
>> A streamlined, 14 day to market process makes app distribution fast and easy
>> Join now and get one step closer to millions of Verizon customers
>> http://p.sf.net/sfu/verizon-dev2dev
>> _______________________________________________
>> Devil-linux-discuss mailing list
>> Dev...@li...
>> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
>

Re: [Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Heiko Z. <he...@zu...>]

Quoting Aaron McDonnell <aa...@uw...>:

> Hi Heiko,
>
> Thanks to you and Marcello for the responses.  I gave this a try, but it
> does not fix the issue.  I should provide a bit more info for you...
>
> In the /etc/sysconfig/nic directory, there are a number of interface config
> files for the various vlans involved.  What I tried this time was to copy
> the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed
> the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the
> IP address to the second IP I needed in that VLAN.
>
> When I restarted the network services, it again overwrote the first IP with
> the second, and the second IP behaved oddly and I could not attach to it.  I
> reverted back to the single IP in VLAN 274.  Any other ideas?

It's been a very long time since I did something like that.
Try not using just "eth0" alone, always specify it as "eth0:x", even  
on the main interface.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Marcello D. <mar...@st...>]

Il giorno mer, 13/01/2010 alle 12.43 -0500, Aaron McDonnell ha scritto:
> In the /etc/sysconfig/nic directory, there are a number of interface config 
> files for the various vlans involved.  What I tried this time was to copy 
> the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed 
> the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the 
> IP address to the second IP I needed in that VLAN.

I would try the following:

1st file: ifcfg-vlan274
DEVICE=eth0

2nd file: ifcfg-vlan274:0
DEVICE=vlan274:0

Note that the former points to the physical device while the latter
points to the "vlan" device.

This is because the fist file is a "vlan definition" and the DEVICE
value is used together with the VLANID value as parameter to the vconfig
command in order to define a NEW vlan on the specified physical nic. The
second file is a "standard alias definition" (regardless of the
interface type you're defining the alias on) and the DEVICE value is
used as a parameter to the ifconfig command. And the command you want
the system to execute for the second IP is something like:
ifconfig vlan274:0 $IPADRR netmask $NETMASK broadcast $BROADCAST

Hope it helps.

Ciao

Marcello


> 
> When I restarted the network services, it again overwrote the first IP with 
> the second, and the second IP behaved oddly and I could not attach to it.  I 
> reverted back to the single IP in VLAN 274.  Any other ideas?
> 
> --
> 
> Aaron McDonnell
> Network Administrator
> Network Operations Centre
> University of Western Ontario
> Tel: 519-661-2111 ext. 86558
> 
> On 13/01/2010 12:26 PM, Heiko Zuerker wrote:
> > Quoting Aaron McDonnell<aa...@uw...>:
> >
> >> Hi All,
> >>
> >> I'm wondering if anyone knows of a way to add a second IP in the same subnet
> >> to a tagged VLAN interface?
> >>
> >> We use Devil Linux to implement a Quarantine network on campus, currently
> >> provided by two boxes.  I would like to consolidate the boxes by merging one
> >> into the other, and easiest way to migrate things would be to give the
> >> primary box the IPs of the secondary in addition to its own.  Both boxes
> >> have around 30+ networks them via tagged interfaces.
> >>
> >> Initially, I tried this by taking the interface and using the technique
> >> you'd use on a normal one, eg:
> >>
> >> cp ifcfg-vlan274 ifcfg-vlan274:1
> >>
> >> And I edited to :1 version to have the second IP.  This only seemed to
> >> overwrite the first interface though when I restarted network services.  Is
> >> there another way to do this?
> >
> > As far as I recall you have to edit the file and change the line:
> > DEVICE=eth2
> > to
> > DEVICE=eth2:1
> >
> > The name of the file doesn't provide any functionality, the content if
> > what counts.
> >
> > In addition to that, uou may have to start counting at 0.
> >
> >
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Aaron M. <aa...@uw...>]

Hi Heiko,

Thanks to you and Marcello for the responses.  I gave this a try, but it 
does not fix the issue.  I should provide a bit more info for you...

In the /etc/sysconfig/nic directory, there are a number of interface config 
files for the various vlans involved.  What I tried this time was to copy 
the file "ifcfg-vlan274" to "ifcfg-vlan274a", and in the new file, I changed 
the device entry from "DEVICE=eth0" to "DEVICE=eth0:0", and also changed the 
IP address to the second IP I needed in that VLAN.

When I restarted the network services, it again overwrote the first IP with 
the second, and the second IP behaved oddly and I could not attach to it.  I 
reverted back to the single IP in VLAN 274.  Any other ideas?

--

Aaron McDonnell
Network Administrator
Network Operations Centre
University of Western Ontario
Tel: 519-661-2111 ext. 86558

On 13/01/2010 12:26 PM, Heiko Zuerker wrote:
> Quoting Aaron McDonnell<aa...@uw...>:
>
>> Hi All,
>>
>> I'm wondering if anyone knows of a way to add a second IP in the same subnet
>> to a tagged VLAN interface?
>>
>> We use Devil Linux to implement a Quarantine network on campus, currently
>> provided by two boxes.  I would like to consolidate the boxes by merging one
>> into the other, and easiest way to migrate things would be to give the
>> primary box the IPs of the secondary in addition to its own.  Both boxes
>> have around 30+ networks them via tagged interfaces.
>>
>> Initially, I tried this by taking the interface and using the technique
>> you'd use on a normal one, eg:
>>
>> cp ifcfg-vlan274 ifcfg-vlan274:1
>>
>> And I edited to :1 version to have the second IP.  This only seemed to
>> overwrite the first interface though when I restarted network services.  Is
>> there another way to do this?
>
> As far as I recall you have to edit the file and change the line:
> DEVICE=eth2
> to
> DEVICE=eth2:1
>
> The name of the file doesn't provide any functionality, the content if
> what counts.
>
> In addition to that, uou may have to start counting at 0.
>
>

Re: [Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Heiko Z. <he...@zu...>]

Quoting Aaron McDonnell <aa...@uw...>:

> Hi All,
>
> I'm wondering if anyone knows of a way to add a second IP in the same subnet
> to a tagged VLAN interface?
>
> We use Devil Linux to implement a Quarantine network on campus, currently
> provided by two boxes.  I would like to consolidate the boxes by merging one
> into the other, and easiest way to migrate things would be to give the
> primary box the IPs of the secondary in addition to its own.  Both boxes
> have around 30+ networks them via tagged interfaces.
>
> Initially, I tried this by taking the interface and using the technique
> you'd use on a normal one, eg:
>
> cp ifcfg-vlan274 ifcfg-vlan274:1
>
> And I edited to :1 version to have the second IP.  This only seemed to
> overwrite the first interface though when I restarted network services.  Is
> there another way to do this?

As far as I recall you have to edit the file and change the line:
DEVICE=eth2
to
DEVICE=eth2:1

The name of the file doesn't provide any functionality, the content if  
what counts.

In addition to that, uou may have to start counting at 0.


-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Marcello D. <mar...@st...>]

Hi Aaron,

I'm quite sure to have had it working...

Did you edit the DEVICE= line? Following your sample it should be:

DEVICE=vlan274:1

Ciao

Marcello

Il giorno mer, 13/01/2010 alle 10.21 -0500, Aaron McDonnell ha scritto:
> Hi All,
> 
> I'm wondering if anyone knows of a way to add a second IP in the same subnet 
> to a tagged VLAN interface?
> 
> We use Devil Linux to implement a Quarantine network on campus, currently 
> provided by two boxes.  I would like to consolidate the boxes by merging one 
> into the other, and easiest way to migrate things would be to give the 
> primary box the IPs of the secondary in addition to its own.  Both boxes 
> have around 30+ networks them via tagged interfaces.
> 
> Initially, I tried this by taking the interface and using the technique 
> you'd use on a normal one, eg:
> 
> cp ifcfg-vlan274 ifcfg-vlan274:1
> 
> And I edited to :1 version to have the second IP.  This only seemed to 
> overwrite the first interface though when I restarted network services.  Is 
> there another way to do this?
> 
> --
> 
> Aaron McDonnell
> Network Administrator
> Network Operations Centre
> University of Western Ontario
> Tel: 519-661-2111 ext. 86558
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

[Devil-Linux-discuss] Adding multiple IPs, same subnet, to 802.1q interfaces

[Aaron M. <aa...@uw...>]

Hi All,

I'm wondering if anyone knows of a way to add a second IP in the same subnet 
to a tagged VLAN interface?

We use Devil Linux to implement a Quarantine network on campus, currently 
provided by two boxes.  I would like to consolidate the boxes by merging one 
into the other, and easiest way to migrate things would be to give the 
primary box the IPs of the secondary in addition to its own.  Both boxes 
have around 30+ networks them via tagged interfaces.

Initially, I tried this by taking the interface and using the technique 
you'd use on a normal one, eg:

cp ifcfg-vlan274 ifcfg-vlan274:1

And I edited to :1 version to have the second IP.  This only seemed to 
overwrite the first interface though when I restarted network services.  Is 
there another way to do this?

--

Aaron McDonnell
Network Administrator
Network Operations Centre
University of Western Ontario
Tel: 519-661-2111 ext. 86558

Re: [Devil-Linux-discuss] anybody using wvdial?

[Heiko Z. <he...@zu...>]

Quoting Frank Weis <Fra...@ct...>:

> Heiko Zuerker wrote:
>> Is anybody using wvdial?
>
> I don't. But I wonder if you want responses from non-users also?

I think I found a workaround for my problem, so I can leave it in (for now).

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Devil-Linux-discuss] anybody using wvdial?

[Frank W. <Fra...@ct...>]

Heiko Zuerker wrote:
> Is anybody using wvdial?

I don't. But I wonder if you want responses from non-users also?

Regards,

Frank


> 
> If not, then I may nuke the package.
> 


-- 
_______________________________________________
 Centre de Technologie de l'Education
 29 avenue John F. Kennedy
 L-1855 Luxembourg-Kirchberg
 email: Fra...@ct...
 tél.: +352 247-85973
 fax: +352 333797
_______________________________________________

[Devil-Linux-discuss] anybody using wvdial?

[Heiko Z. <he...@zu...>]

Is anybody using wvdial?

If not, then I may nuke the package.

-- 

Regards
   Heiko Zuerker
   http://www.devil-linux.org


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Devil-Linux-discuss] Devil Linux wireless Access Point - now working - here's HowTo

[K.G.H. N. <kg...@tt...>]

Hello, all, and thanks for your attention and help.  It became clear my wireless card was not easily capable of being an access point under Linux, and I found little advice about setting Devil Linux up with an Ad Hoc wireless service.  So, I took the advice of a helpful person at Devil-linux-discuss (a wonderful group) and bought a used Linksys Wireless G (WRT54G ver6) router on eBay.

Last night I got the Access Point working, and as I had to draw together many sites' and manuals' info I will share with you how I ended up doing it.  (By the way, the 85 page Linksys router's manual on its CD is amazingly good, with lots of vocabulary definitions and background information.)

My goal:  to provide secure wireless access to our network behind our Devil Linux gateway-to-the-Internet dedicated firewall machine.  All devices using fixed IPs, including our ADSL connection.
	My solution:  I set up a Linksys WRT54G (Wireless G) router as an Infrastructure Access Point on an CAT5e wired network.
	Here we go:

***Changing the WRT54G's IP disables access via your browser until the computer's IP is changed to match the first three groups of numbers (with netmask 255.255.255.0), so I did that last.***
1) The WRT54G should not be connected to the LAN during initial configuration.
2) Connect a standalone computer's Ethernet into one of the four WRT54G LAN ports (not its Internet port.)
3) Reset the WRT54G by holding its reset button for 15 seconds with power connected.  Wait for the power light to stop blinking.
4) (Win2000pro) CtrlPanel >> Network & Dialup Connections >> RtClick Ethernet >> click Internet Protocol (TCP/IP) >> click Properties >> set IP address to 192.168.1.3 ...OK OK, minimize window.
5) In Firefox or Internet Explorer enter URL/Address 192.168.1.1 and give Username (none) Password Admin, Linksys config utility now showing.
6) Setup Basic Setup:  Internet Connection type Automatic Configuration - DHCP, Router name [optional name], domain name [optional name], DHCP server DISABLE, set time zone ...Save settings.
7) Setup DDNS disable, MAC disable, Advanced Routing Operating Mode ***ROUTER***, Dynamic Routing Disabled, no static routing ...Save settings.
8) Wireless SSID [name], SSID Broadcast [enable for now] ...Save settings.
9) Wireless security mode WPA2 Personal/AES (best security compatible with Wii), key [10 chr hex string] ...Save settings.
10) MAC filter disable, Advanced Wireless Secure Easy Setup DISABLE ...Save settings.
11) Security leave defaults alone, Access Restrictions leave disabled, Applications & Gaming leave disabled.
12) Administration set new password, wireless access web enable, remote management disable ...Save settings.
13) It will ask you to login again.  Enter new password for continued access.
14) Log disable, config management BACKUP to file.
15) Status - firmware version should be v1.02.7 build 011, Jul. 27.2009 (as of 12/2009)  I updated our firmware with the file from Linksys' site.  It was easy.  I did plug the router into a UPS for the procedure.  Updating did not lose my saved configuration.
16) Return to Setup - Basic Setup. Change Local IP Address to one in your fixed-IP LAN range...Save settings.  It says "Settings are successful. Please release/renew IP. "Close" button doesn't work in Firefox, but does close IE.  (The release/renew business is for DHCP IP addresses, you can ignore that if you are working with fixed IPs.)
17) Restore the Network window, go back to TCP/IP properties (see step 4).  Set IP address to the machine's proper one in your fixed-IP LAN range.  OK OK
18) Unplug WRT54G's power cord, wait 20 seconds.  While you are waiting, plug an Ethernet cable into one of your LAN's ports and one of the WRT54G's LAN ports.  (NOT the Internet port.)  Replug the WRT54G's power cord, wait for the power light to stop blinking.
19) The machine should now have net access, and the WRT54G's WLAN light should be lit.  Entering the URL of the WRT54G's Local IP Address should make it ask for the (new) password, and the Linksys config utility then shows.
20) Once all the wireless user devices are configured & working, I believe we can disable SSID Broadcast for greater security without disturbing user connections.  I plan to do this.

The Wii is happy and my kids downloaded some game demos on it last night to prove it works.  One advantage to this configuration is that the Access Point can be connected to our LAN anywhere, it doesn't need to be connected to the ADSL modem or live in the room with the ADSL jack. 

Good luck to anyone with a similar project.  I hope this post helps.
KGHN

[Devil-Linux-discuss] Devil-Linux 1.4RC2 released

[Heiko Z. <he...@zu...>]

Hello DL Community

 

the second Release Candidate of Devil-Linux 1.4 is available for download.

 

All known bugs of RC1 have been resolved, in addition to many software
updates.

 

Please report any problems on hour mailinglist.

 

Regards

  Heiko Zuerker

  http://www.devil-linux.org

 

[Devil-Linux-discuss] Tinc-VPN in Devil-Linux

[Andreas G. <a.g...@gu...>]

hello,

i'm using devil-linux for a long time. and it's great :-)

now i have a question. did someone made a tinc-vpn patch/package 
for including into devil-linux?

if not, i think i have to start a build-session. 
o.k. it might take longer as one session ...

cheers,
andreas

-- 
OpenPGP
Key id: 23016BC8
Key fingerprint = FEC3 6C68 44AA C2EE D4EF  99BD 83E1 3353 2301 6BC8
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x23016BC8

[Devil-Linux-discuss] Tinc-VPN in Devil-Linux

[Andreas G. <a.g...@gu...>]

hello,

i'm using devil-linux for a long time. and it's great :-)

now i have a question. did someone made a tinc-vpn patch/package 
for including into devil-linux?

if not, i think i have to start a build-session. 
o.k. it might take longer as one session ...

cheers,
andreas


-- 
OpenPGP
Key id: 23016BC8
Key fingerprint = FEC3 6C68 44AA C2EE D4EF  99BD 83E1 3353 2301 6BC8
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x23016BC8

Re: [Devil-Linux-discuss] Running VMware Server on Devil-Linux

[John B. <sag...@gm...>]

Hi,

Thanks for the input Frank & I'm sorry my thanks is so belated.
(I've neglected much in the past 2 months.)  My other problem with
Virtual Box was that the utility of snapshots was so limited,
the feature was useless.  Has this been addressed?

In VM Workstation, one is free to take as many snapshots
as there is disk space & restart from any of them without
affecting other snapshots.

Thanks,
Chip
(I've no affiliation whatsoever with VMWare or Sun.)

Re: [Devil-Linux-discuss] Running VMware Server on Devil-Linux

[Kari M. <kar...@tr...>]

----- "Bruce Smith" <bw...@re...> wrote:

> >>Under the hood, ESX and ESXi are really Linux, so it seems silly to
> me
> >>that it requires a Windows client to admin the server.
> >
> > I wondered about this, because ESXi claims one of its differences
> with
> > ESX is that it doesn't rely on an underlying OS. To which I thought:
> eh?
> 
> They try to hide it, but it's still Linux (or based on Linux).  A
> more
> stripped down version of Linux, but still Linux.  There is a hack you
> can do to let you SSH into ESXi and get a shell prompt to prove it to
> yourself.

ESX Classic v4 Service Console is 64-bit Redhat Enterprise Linux, or actually a VMware's stripped down version of it. Compatible 'tough. You may even install your own RPMs there if you really want. Third parties like IBM/Tivoli, EMC/Legato, etc. utilise this when installing backup or management agents etc.

ESXi v4 has a µClibc (uClibc, http://www.uclibc.org/) based Linux builtin. Just like FloppyFW and some others. You may compily static binaries and excute them there, but there is really no need for that.

Both are very well remote managed with vSphere CLI, available for Linux and Windows. It is a set of Perl scripts which allows you to do just anything remotely. Windows version contains a version of ActivePerl.

In vSphere 4, interesing thing about both ESX Classic and ESXi is that the boot process is just like any other Linux, but there is something peculiar in the initrd. It contains the hypervisor code. And it is enabled early.

It also means, what you see after booting up either ESX version, is really a virtual machine! It is a special virtual machine (in ESX Classic called Service Console), which is used for management, and which can access the hardware.

So, everything you see, the management etc. is Linux, but the hypervisor beneath really is VMware's own. History on that hypervisor goes to Stanford and the SimOS project there (google: simos vmware).

I hope this clarifies things.

br, Kari

>  - BS
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

-- 

Kari Mattsson | Voice & SMS: +358-50-69000 
Trivore Corp., P.O. Box 6, FI-20541 Turku, Finland 
http://trivore.com | http://mysync.eu | http://mysync.asia 

mySync Express - always in sync 
mySync Management - managed, secured, always 

Re: [Devil-Linux-discuss] Running VMware Server on Devil-Linux

[Kari M. <kar...@tr...>]

----- "John Jore" <jo...@jo...> wrote:

> and Virtual Center Server and Client for Linux is on the horizon
> afaik... (Think I heard / read it was in beta testing, but i could be
> very, very wrong.)

Luckily you are not wrong :-)

/KMa

> JJ
> 
> 
> ________________________________________
> From: Bruce Smith [bw...@re...]
> Sent: 21 October 2009 15:02
> To: dev...@li...
> Subject: Re: [Devil-Linux-discuss] Running VMware Server on
> Devil-Linux
> 
> >>> The main problem with ESXi
> >>
> >> The other main problem with ESXi is a Windows-only client is
> required
> >> to administer it.  Which for us Mac & Linux only households, it
> means
> >> I still need a copy of the old VMware-server (free) on Linux, or
> >> VMware-Fusion (not free) on Mac to run Windows to admin
> VMware-ESXi.
> >> :-(
> >
> > I have a Windows VM running with the client installed. ;-)
> 
> Hopefully the VM is auto boot, and it has RDP enabled!   :-)
> 
> >>> is the limited hardware support, I ended up
> >>> replacing a few components of my server to be able to use ESXi.
> >>
> >> I'd love to be able to run ESXi at home on an old PC, but I
> haven't
> >> attempted it yet.  (and I don't want to spend thousands of dollars
> on
> >> "supported" server hardware)
> >>
> >> What problems did you run into?  What hardware did you replace to
> >> make it run?
> >
> > It was a step-by-step process, but I basically I ended up replacing
> my
> > 3ware sata raid controller with a LSI1068E one (supermicro has a
> cheap
> > one), replaced the NIC with a Intel based Gig desktop card and also
> > ended up replacing my board/cpu/ram since I wanted the hw
> > virtualization support.
> 
> So basically, you ended up building a whole new machine.  :-)
> 
> Do you have a shopping list for anyone who wants to build one cheap?
> 
> I've got a bunch of old IDE drives.  Is there any way to make them
> work, or do I have to go SATA?
> 
>  - BS
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart
> your
> developing skills, take BlackBerry mobile applications to market and
> stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss

Re: [Devil-Linux-discuss] Devil Linux wireless internet access - followup - not there yet

[Markus W. <ml...@ir...>]

On 13.12.2009 17:29 K.G.H. Nicholes wrote:

> I finally snagged a used Linksys Wireless G
> router on eBay for not too much more.

And if it is a supported model: perhaps this alternative firmware
http://www.dd-wrt.com/ is an option for you. I'm using this on my
Linksys WRT54G for years with great success. Current uptime: 211 days.

Regards,
Markus

[Devil-Linux-discuss] Devil Linux wireless internet access - followup - not there yet

[K.G.H. N. <kg...@tt...>]

12/13/2009
Hello Serge and Heiko,
	I have been pursuing your advice, and have given up hope of a Devil Linux wireless Access Point with my current PCI wireless board.  I looked briefly for a board with one of the Prism chipsets, recommended at linux.com (/archive/articles/55617) as being able to be a "Master mode" access point, but without any luck.  I then started shopping for a wireless access point or router stand-alone module.  The cheapest ones have reputations for unreliability - both dropping sessions and breaking after a few months' use.  I finally snagged a used Linksys Wireless G router on eBay for not too much more.  I hope it will arrive soon.
	Thanks for your advice and help.  I may indeed have some firewall questions in a bit.
	KGHN

Re: [Devil-Linux-discuss] Devil Linux wireless internet access - followup - not there yet

[Serge L. <fi...@in...>]

Hello  K.G.H. Nicholes,

As far as I can see you have chosen not the easiest way to build the setup. I'd
suggest you doing it a bit another way - i.e. something like Heiko suggested.

Linux as a Access Point is a big problem due to wifi drivers. Only a few drivers
have full featured support of AP mode. Depending on HW revision and drivers
version you, probably, cannot create AP at all. However, if you buy any AP and
will use it as a WiFi bridge for LAN, it simplifies your task significantly. DL
may be a DHCP server and gateway for the LAN, but it's better to delegate wifi
and security (WPA2 I guess) tasks to $10-15 AccessPoint.

All your cards will be commodity Ethernet NICs and Dl works perfectly with them.

I suppose we can help you with the firewall for you network but it's necessary
to have a clear understanding what services in your network are allowed, who
should have an access to what resources etc.

Sincerely,
Serge


On 12/06/2009 08:06 PM, K.G.H. Nicholes wrote:
> 12/6/2009
> Thanks, Heiko, you sent me a very helpful message.
> 
> I realized it could be helpful to someone helping me if I am more clear about what I am trying to do, so I'll start there.  We have a wired LAN of 3 hubs, connected by BNC co-ax.  The hubs are distributing signals on CAT5e ethernet to about 10 assorted Linux & Win OS computers.  (A legacy situation, obviously.)  We have ADSL service that is connected, on arrival from our ISP, through a plain non-wireless Paradyne 6211 modem.  Between that modem and our wired LAN is a "gateway" firewall computer running Devil Linux.  For years we had just two ethernet cards and Devil has served us well.
> 	Now we would like to add wireless internet access to our building.  We don't care whether the machines receiving wireless can see the wired LAN members, they just need to be able to reach the internet.  So far, the machines wanting to use wireless are a Wii and two linux laptops (one Slackware and one Ubuntu.)
> 
> Big overview questions, read on before answering:  Can you confirm that Devil Linux is a good choice for this three-network-card "gateway" project?  Is our Belkin Wireless G Desktop Card - Atheros AR2413 802.11bg - adequate?  Should I aim for a full Master-mode "access point" or a more modest Ad-Hoc peer-to-peer wireless configuration?  (I am not sure the Wii can talk to an Ad-Hoc, but the Wii's access is not as important as the laptops.)
> 
> In your message you said,
> "Edit the file [ifcfg-eth2] directly under DL (using vi, joe or even mc).
> cd /etc/sysconfig/nic/
> Rename ifcfg-eth2 to ifcfg-wlan0 and (as you already guessed) change the
> DEVICE line to DEVICE=wlan0 .
> Take a look at the file ifcfg-eth4.sample , which has examples for a wireless setup.
> You can easily test if the changes work with:
> /etc/init.d/network restart
> (Of course this will affect other users currently using the gateway.)"
> 
> On my Devil 1.4RC1 system, there is no /etc/sysconfig/nic/ directory, but 
> ifcfg-* appears in 
>   /shm/etc-mods/sysconfig/nic/ and
>   /shm/etc/sysconfig/nic/
> (Also /etc-cd/sysconfig/nic/ has .sample files.)  I believe the etc-mods.tar.bz2 configuration file that gets saved to the floppy by save-config contains the etc-mods tree (and a single file in a root directory.)
> 
> So, in /shm/etc-mods/sysconfig/nic/ifcfg-eth2, I tried changing (using vi) DEVICE=eth2 to
>   DEVICE=wlan0
> save-config/restart.  Yes!  The wireless card as wlan0 now boots to an UP BROADCAST MULTICAST state per ifconfig.  (ifconfig also added an entry for wmaster0.)
> 
> While waiting for your answer, I did find the ifcfg-*.sample series you mention, and they are enlightening, especially "eth4" relating to a wireless setup.  I did
>   man iwconfig
> as the sample file suggests in a comment, but only some of the parameters seem to work for me in the ifcfg-eth2 file.  For example,
>   KEY=NNNNNNNNNN or
>   ENC=NNNNNNNNNN in ifcfg-eth2 doesn't seem to take (with or without quotes around the hex number), though interactively
>   iwconfig wlan0 key 1234567890
> or
>   iwconfig wlan0 enc 1234567890
> works fine and sets the encryption key to 1234-5678-90.
> 
> I have also figured out that if I modify the files in /shm/etc-mods/sysconfig/nic, and then do save-config, the modifications are written to the floppy and are used in the next boot.  Your suggestion to 
>   /etc/init.d/network restart
> is a pretty handy command for on-the-fly configuration testing, though it does not seem to reset the devices to all their defaults before applying the ifcfg- commands.  It's much faster than writing/rebooting, thank you.
> 
> Here's my current ifcfg-eth2 file:
> DEVICE=wlan0
> MODULE="ath5k"
> WIRELESS=yes
> ONBOOT=yes
> MODE=Ad-Hoc
> ESSID=(security alphanumeric SSID string, currently 8 chrs)
> ENC=(security WEP string hex 10 digits, a-f in lowercase)
> RATE=auto
> DHCP=no
> IP="(LAN ip I want to point the wireless at, as the wireless gateway/access point)"
> NETMASK="255.255.255.0"
> BROADCAST="(same as IP except .255)"
> 
> I tried renaming /shm/etc-mods/sysconfig/nic/ifcfg-eth2 to ifcfg-wlan0 as you suggested.  With the rename, after a save-config/reboot, ifconfig doesn't see wlan0 unless I give it the -a parameter, so it's there but not UP.  iwconfig does not show wlan0 configured beyond its defaults, and Tx-Power=0 dBm.  ("ifconfig wlan0 up" changes that to 27 dBm.)  If I /etc/init.d/network restart, iwconfig wlan0 does not show any changes to dummy settings I made interactively with iwconfig before the restart, so I gather that the ifcfg-wlan0 file is not being processed under the new name.
> 	I suspected that the name "eth2" is specified in some other configuration file that lists the network's devices and calls for the ifcfg- files to be processed.  I unpacked the floppy's bz2 on my Win2000 machine and searched for the string "eth2".  It's there, in firewall.rules 
>   DMZ_DEV=eth2	# DMZ network
> and .viminfo has several mentions of 
>   /shm/etc-mods/sysconfig/nic/ifcfg-eth2
> Neither file mentioned wlan0.  I think I'll try editing them...  Made the single change in firewall.rules to
>   DMZ_DEV=wlan0	# DMZ network
> Hmmm, /shm/root/.viminfo seems to include several mentions of ifcfg-wlan0, even ifcfg-master0.  A vi change log?  I think I'll leave that alone.  ":q!"
> 	So I went back to the name ifcfg-eth2.  (Should I change the firewall.rules file back?)
> 
> OK, When I restart the network, or reboot, with ifcfg-eth2, I see 
>   Setting wireless options for interface wlan0Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Device or resource busy
> I have found that interactively I need to 
>   ifconfig wlan0 down
> before I can "iwconfig wlan0 mode (option)" without an error, then
>   ifconfig wlan0 up
> I am not sure how to do this in the configuration file.  Does the order of the lines matter?  I tried swapping them around some to put the iwconfig-type commands before the ifconfig-type commands (the file as listed above) but it didn't seem to help.  wlan0 comes up in "Managed" mode as default, and I wonder if there is a way to get it to work in that mode... seems unlikely.
> 
> Hmmm, when I edit ifcfg-eth2, or add a new file (ifcfg-master0, for example) to 
>   /shm/etc-mods/sysconfig/nic/
> my change immediately shows up in
>   /shm/etc/sysconfig/nic/
> This apparently works vice versa, too.  The .sample files only are in /shm/etc/sysconfig/nic/, though.  (I bet they link similarly to /etc-cd/sysconfig/nic/.)
> 
> As I am booting now (or a /etc/init.d/network restart), the process sets wlan0 and also another link called wmaster0 UP.  When I hopefully Googled wmaster0, I gathered it's not likely to be helpful to me.  (The experimental ifcfg-master0 file I created is now erased.)
> 
> I am not sure my Atheros AR2413 802.11bg card with Devil's ath5k driver can be an access point.  When I
>   iwconfig wlan0 mode Master
> it complains SET failed on device wlan0 ; Invalid argument
> It takes 
>   iwconfig wlan0 mode Ad-Hoc
> happily, and also Managed.  We have no other wireless around, so I gather Managed isn't applicable - there's no Master machine to manage this service.  Can I use Ad-Hoc and talk to our few other machines peer-to-peer?
> 
> In setup, Devil 1.4RC1 presents only two firewall options, FW2 two-network-card and DMZFW3 three-card-with-DMZ.  Can I use one of these, or am I better off modifying a configuration file?  I see /shm/etc/init.d/firewall.rules and firewall.rules.2nic and firewall.rules.3nic, perhaps the latter two are useful sample files.
> 
> You said,
>   "I don't think the 'dmz' firewall setup in DL is what you're looking for. Our FW rules are meant to be a fairly secure starting point, but need customizations depending on the user's environment.  You may be best of [off] using the Shorewall scripts to configure the firewall. I think they're simpler to use."
> 	I am a programmer, but don't know the bash(?) script language.  If we can make life simple and use the DMZ firewall as Devil hands it to me, it would help us get up and running much quicker.
> 
> How do I let Devil know which encryption scheme I want to use?  On the Wii I've been choosing WEP (our town has 4 houses) for testing.  (The Wii doesn't seem to have an "encryption off" choice.  I am not sure what happens if I choose WEP and leave the key blank.)
> 
> FYI Wii setup: Wireless connection/manual setup/SSID to match/WEP to match/advanced IPs/advanced DNSs/no proxy.  I have never set up a Wii before and might not be doing it right.  The Wii manual's troubleshooting says "check the signal strength", but doesn't explain how.  I assume the default wlan0 Frequency: 2.412 GHz is OK for the Wii as the Wii manual does not specify what the unit can accept.
> 	I am located in "cow country", rural central Montana, so I don't have easy access to any working wireless access points to test my laptops on.  Our valley doesn't even have cell phone service...
> 
> As you suggested, I googled "linux access point" and variations thereon, and found advice like, 
>   "If you can't set the device into master mode with iwconfig, it isn't going to work with anything else." and 
>   "I thought that putting a device into master mode was so easy, but so far I have not come across one single interface that accepts this via iwconfig."
> I think maybe my Belkin/Atheros just isn't suitable to be an access point device.  That's why I'm wondering if Ad-Hoc will work for me.
> 
> Thanks for describing the setup you use, and recommending openvpn.  (Which linux distro?)  If I ever get a wireless router, I may try that approach.  For now, I'm hoping I can use the equipment on hand and be happy with just basic access.
> 
> Thanks very much for sharing your expertise.  How neat you have a Wii, too.  I hope this long post isn't too much to ask.
> 
> KGHN
> 
> 
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Devil-linux-discuss mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss
> 

[Devil-Linux-discuss] Devil Linux wireless internet access - followup - not there yet

[K.G.H. N. <kg...@tt...>]

12/6/2009
Thanks, Heiko, you sent me a very helpful message.

I realized it could be helpful to someone helping me if I am more clear about what I am trying to do, so I'll start there.  We have a wired LAN of 3 hubs, connected by BNC co-ax.  The hubs are distributing signals on CAT5e ethernet to about 10 assorted Linux & Win OS computers.  (A legacy situation, obviously.)  We have ADSL service that is connected, on arrival from our ISP, through a plain non-wireless Paradyne 6211 modem.  Between that modem and our wired LAN is a "gateway" firewall computer running Devil Linux.  For years we had just two ethernet cards and Devil has served us well.
	Now we would like to add wireless internet access to our building.  We don't care whether the machines receiving wireless can see the wired LAN members, they just need to be able to reach the internet.  So far, the machines wanting to use wireless are a Wii and two linux laptops (one Slackware and one Ubuntu.)

Big overview questions, read on before answering:  Can you confirm that Devil Linux is a good choice for this three-network-card "gateway" project?  Is our Belkin Wireless G Desktop Card - Atheros AR2413 802.11bg - adequate?  Should I aim for a full Master-mode "access point" or a more modest Ad-Hoc peer-to-peer wireless configuration?  (I am not sure the Wii can talk to an Ad-Hoc, but the Wii's access is not as important as the laptops.)

In your message you said,
"Edit the file [ifcfg-eth2] directly under DL (using vi, joe or even mc).
cd /etc/sysconfig/nic/
Rename ifcfg-eth2 to ifcfg-wlan0 and (as you already guessed) change the
DEVICE line to DEVICE=wlan0 .
Take a look at the file ifcfg-eth4.sample , which has examples for a wireless setup.
You can easily test if the changes work with:
/etc/init.d/network restart
(Of course this will affect other users currently using the gateway.)"

On my Devil 1.4RC1 system, there is no /etc/sysconfig/nic/ directory, but 
ifcfg-* appears in 
  /shm/etc-mods/sysconfig/nic/ and
  /shm/etc/sysconfig/nic/
(Also /etc-cd/sysconfig/nic/ has .sample files.)  I believe the etc-mods.tar.bz2 configuration file that gets saved to the floppy by save-config contains the etc-mods tree (and a single file in a root directory.)

So, in /shm/etc-mods/sysconfig/nic/ifcfg-eth2, I tried changing (using vi) DEVICE=eth2 to
  DEVICE=wlan0
save-config/restart.  Yes!  The wireless card as wlan0 now boots to an UP BROADCAST MULTICAST state per ifconfig.  (ifconfig also added an entry for wmaster0.)

While waiting for your answer, I did find the ifcfg-*.sample series you mention, and they are enlightening, especially "eth4" relating to a wireless setup.  I did
  man iwconfig
as the sample file suggests in a comment, but only some of the parameters seem to work for me in the ifcfg-eth2 file.  For example,
  KEY=NNNNNNNNNN or
  ENC=NNNNNNNNNN in ifcfg-eth2 doesn't seem to take (with or without quotes around the hex number), though interactively
  iwconfig wlan0 key 1234567890
or
  iwconfig wlan0 enc 1234567890
works fine and sets the encryption key to 1234-5678-90.

I have also figured out that if I modify the files in /shm/etc-mods/sysconfig/nic, and then do save-config, the modifications are written to the floppy and are used in the next boot.  Your suggestion to 
  /etc/init.d/network restart
is a pretty handy command for on-the-fly configuration testing, though it does not seem to reset the devices to all their defaults before applying the ifcfg- commands.  It's much faster than writing/rebooting, thank you.

Here's my current ifcfg-eth2 file:
DEVICE=wlan0
MODULE="ath5k"
WIRELESS=yes
ONBOOT=yes
MODE=Ad-Hoc
ESSID=(security alphanumeric SSID string, currently 8 chrs)
ENC=(security WEP string hex 10 digits, a-f in lowercase)
RATE=auto
DHCP=no
IP="(LAN ip I want to point the wireless at, as the wireless gateway/access point)"
NETMASK="255.255.255.0"
BROADCAST="(same as IP except .255)"

I tried renaming /shm/etc-mods/sysconfig/nic/ifcfg-eth2 to ifcfg-wlan0 as you suggested.  With the rename, after a save-config/reboot, ifconfig doesn't see wlan0 unless I give it the -a parameter, so it's there but not UP.  iwconfig does not show wlan0 configured beyond its defaults, and Tx-Power=0 dBm.  ("ifconfig wlan0 up" changes that to 27 dBm.)  If I /etc/init.d/network restart, iwconfig wlan0 does not show any changes to dummy settings I made interactively with iwconfig before the restart, so I gather that the ifcfg-wlan0 file is not being processed under the new name.
	I suspected that the name "eth2" is specified in some other configuration file that lists the network's devices and calls for the ifcfg- files to be processed.  I unpacked the floppy's bz2 on my Win2000 machine and searched for the string "eth2".  It's there, in firewall.rules 
  DMZ_DEV=eth2	# DMZ network
and .viminfo has several mentions of 
  /shm/etc-mods/sysconfig/nic/ifcfg-eth2
Neither file mentioned wlan0.  I think I'll try editing them...  Made the single change in firewall.rules to
  DMZ_DEV=wlan0	# DMZ network
Hmmm, /shm/root/.viminfo seems to include several mentions of ifcfg-wlan0, even ifcfg-master0.  A vi change log?  I think I'll leave that alone.  ":q!"
	So I went back to the name ifcfg-eth2.  (Should I change the firewall.rules file back?)

OK, When I restart the network, or reboot, with ifcfg-eth2, I see 
  Setting wireless options for interface wlan0Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Device or resource busy
I have found that interactively I need to 
  ifconfig wlan0 down
before I can "iwconfig wlan0 mode (option)" without an error, then
  ifconfig wlan0 up
I am not sure how to do this in the configuration file.  Does the order of the lines matter?  I tried swapping them around some to put the iwconfig-type commands before the ifconfig-type commands (the file as listed above) but it didn't seem to help.  wlan0 comes up in "Managed" mode as default, and I wonder if there is a way to get it to work in that mode... seems unlikely.

Hmmm, when I edit ifcfg-eth2, or add a new file (ifcfg-master0, for example) to 
  /shm/etc-mods/sysconfig/nic/
my change immediately shows up in
  /shm/etc/sysconfig/nic/
This apparently works vice versa, too.  The .sample files only are in /shm/etc/sysconfig/nic/, though.  (I bet they link similarly to /etc-cd/sysconfig/nic/.)

As I am booting now (or a /etc/init.d/network restart), the process sets wlan0 and also another link called wmaster0 UP.  When I hopefully Googled wmaster0, I gathered it's not likely to be helpful to me.  (The experimental ifcfg-master0 file I created is now erased.)

I am not sure my Atheros AR2413 802.11bg card with Devil's ath5k driver can be an access point.  When I
  iwconfig wlan0 mode Master
it complains SET failed on device wlan0 ; Invalid argument
It takes 
  iwconfig wlan0 mode Ad-Hoc
happily, and also Managed.  We have no other wireless around, so I gather Managed isn't applicable - there's no Master machine to manage this service.  Can I use Ad-Hoc and talk to our few other machines peer-to-peer?

In setup, Devil 1.4RC1 presents only two firewall options, FW2 two-network-card and DMZFW3 three-card-with-DMZ.  Can I use one of these, or am I better off modifying a configuration file?  I see /shm/etc/init.d/firewall.rules and firewall.rules.2nic and firewall.rules.3nic, perhaps the latter two are useful sample files.

You said,
  "I don't think the 'dmz' firewall setup in DL is what you're looking for. Our FW rules are meant to be a fairly secure starting point, but need customizations depending on the user's environment.  You may be best of [off] using the Shorewall scripts to configure the firewall. I think they're simpler to use."
	I am a programmer, but don't know the bash(?) script language.  If we can make life simple and use the DMZ firewall as Devil hands it to me, it would help us get up and running much quicker.

How do I let Devil know which encryption scheme I want to use?  On the Wii I've been choosing WEP (our town has 4 houses) for testing.  (The Wii doesn't seem to have an "encryption off" choice.  I am not sure what happens if I choose WEP and leave the key blank.)

FYI Wii setup: Wireless connection/manual setup/SSID to match/WEP to match/advanced IPs/advanced DNSs/no proxy.  I have never set up a Wii before and might not be doing it right.  The Wii manual's troubleshooting says "check the signal strength", but doesn't explain how.  I assume the default wlan0 Frequency: 2.412 GHz is OK for the Wii as the Wii manual does not specify what the unit can accept.
	I am located in "cow country", rural central Montana, so I don't have easy access to any working wireless access points to test my laptops on.  Our valley doesn't even have cell phone service...

As you suggested, I googled "linux access point" and variations thereon, and found advice like, 
  "If you can't set the device into master mode with iwconfig, it isn't going to work with anything else." and 
  "I thought that putting a device into master mode was so easy, but so far I have not come across one single interface that accepts this via iwconfig."
I think maybe my Belkin/Atheros just isn't suitable to be an access point device.  That's why I'm wondering if Ad-Hoc will work for me.

Thanks for describing the setup you use, and recommending openvpn.  (Which linux distro?)  If I ever get a wireless router, I may try that approach.  For now, I'm hoping I can use the equipment on hand and be happy with just basic access.

Thanks very much for sharing your expertise.  How neat you have a Wii, too.  I hope this long post isn't too much to ask.

KGHN

Re: [Devil-Linux-discuss] Please assist Devil Linux to provide our wireless internet access

[Heiko Z. <he...@zu...>]

> -----Original Message-----
> From: K.G.H. Nicholes [mailto:kg...@tt...]
> Sent: Wednesday, December 02, 2009 4:25 PM
> To: dev...@li...
> Subject: [Devil-Linux-discuss] Please assist Devil Linux to provide our
> wireless internet access
> 
> Howdy from Montana, where it's 10 degrees F out, a good time to be
> inside working on our network.
> 
> We are longtime Devil Linux users.  For years, we have run Devil on a
> "gateway" Pentium machine, equipped with two ethernet boards, to
> protect our household LAN computers.
> 
> Now we want wireless, too, in addition to our wired network, which we
> want to keep.  I have assigned a computer to the updated job and we are
> trying to configure Devil Linux 1.4RC1, which I recently downloaded and
> burned to CDR.  (Configuration on floppy.)  The new gateway machine
> has:
> 	A) an on-motherboard Intel 82801 assigned to eth0, running
> Devil's e100 driver happily.  It is CAT5e connected to our Paradyne
> 6211 ADSL modem.
> 	B) a PCI RTL8029(AS) assigned to eth1, running the realtek driver
> happily.  It is CAT5e connected to our LAN.
> 	C) a PCI Belkin Wireless G Desktop Card - Atheros AR2413
> 802.11bg, assigned in Devil's setup to eth2. running the ath5k driver.
> It is not happy on boot; Devil reports eth2 as [IPv4]SIOCSIFADDR No
> such device [FAILED].  I did ask Devil to set up DMZFW3, the three
> network-card firewall.
> 
> Our wireless testing equipment is scanty - we have two laptops with
> wireless.  One runs Ubuntu which did not work with the wireless on
> campus, and one runs Slackware with untested wireless.  (Being able to
> work on and test them is one reason we want wireless here.)  We also
> have a new Wii, which presumably has working wireless if we configure
> it right.
> 
> At this time, after a day's configuration work, our wired LAN members
> do have their normal access to the Internet through the new gateway.
> I've put several hours into the wireless setup, and feel I'm to the
> point where I could really benefit from some help from experienced
> people who understand wireless setup for Devil.
> 
> Here's what I think I've figured out so far:
>   ath5k sets up device wlan0, not eth2
> I can log in the to gateway as root, and then interactively configure
> the wireless card:
>   ifconfig wlan0 (LAN ip I want to point the wireless at, as the
> wireless gateway/access point) netmask 255.255.255.0
>   iwconfig wlan0 essid (security alphanumeric SSID string, currently 8
> chrs)
>   ifconfig wlan0 down
>   iwconfig wlan0 mode managed key (security WEP string hex 10 digits)
>   ifconfig wlan0 up
> ifconfig and iwconfig now see wlan0
> save-config does not make these configuration changes last through the
> next boot, nor does going into setup and choosing "Save your
> configuration".
> 
> When I configure manually as shown above, ifconfig wlan0 says UP
> BROADCAST MULTICAST, but when I test with the Wii, it is not
> successful.  (Wii setup: Wireless connection/manual setup/SSID to
> match/WEP to match/advanced IPs/advanced DNSs/no proxy).  The Wii
> manual's troubleshooting says "check the signal strength", but doesn't
> explain how.  (I assume the default wlan0 Frequency: 2.412 GHz is OK
> for the Wii as the Wii manual does not specify what the unit can
> accept.)
> 
> I copied etc-mods.tar.bz2 from the Devil configuration floppy to
> another (Win2000pro) machine and used 7zip to extract etc-mods.tar,
> which can then be opened with WinZip.  The etc-
> mods\sysconfig\nic\ifcfg-eth2 file contains
> DEVICE=eth2
> ONBOOT=yes
> MODULE="ath5k"
> DHCP=no
> IP="(LAN ip I want to point the wireless user machines at)"
> NETMASK="255.255.255.0"
> BROADCAST="(LAN ip I want to point the wireless users at except the
> last number is replaced by .255)"
> 
> I'd like to try setting DEVICE=wlan0, but I don't know how to put the
> changed file back into the archive so that it appears in the right
> place to Devil.

Edit the file directly under DL (using vi, joe or even mc).
cd /etc/sysconfig/nic/
Rename ifcfg-eth2 to ifcfg-wlan0 and (as you already guessed) change the
DEVICE line to DEVICE=wlan0 .
Take a look at the file ifcfg-eth4.sample , which has examples for a
wireless setup.

You can easily test if the changes work with:
/etc/init.d/network restart
(Of course this will affect other users currently using the gateway.)
 
> I've got the Devil 1.3 documentation up on another machine for
> reference.
> 
> Questions I'd love answered:
> A) Is Devil's "DMZ" network card setup appropriate for what I'm trying
> to do?  I don't understand DMZ very well.  Wikipedia has a rundown at
> http://en.wikipedia.org/wiki/DMZ_%28computing%29, which I read with
> partial understanding.
> B) How do I tell Devil to use wlan0 as eth2?
> C) How do I get the wlan0 ip etc configuration to save/load?
> D) iwconfig says wlan0's Access Point: Not-Associated.  Is this proper?
> E) What range should I expect from the wireless service?  The wireless
> devices are a couple of rooms away from my gateway machine.  It's an
> old frame house.  Do I need to move the Wii closer to the gateway or
> vice versa to get a good test?
> 
> Thank you for your patience in reading through my description.  I look
> forward to comments and tips from those who know.

I don't think the 'dmz' firewall setup in DL is what you're looking for. Our
FW rules are meant to be a fairly secure starting point, but need
customizations depending on the user's environment.
You may be best of using the Shorewall scripts to configure the firewall. I
think they're simpler to use. 

It's been a very long time since I used DL as an access point and I really
don't remember too much. I think I had to do something else to get it into
AP mode. See what you can find on google about that topic (not DL specific).
It is very important that you use some kind of encryption. I use a Linksys
wireless router as my AP (with WPA enabled to keep the neighbors and script
kiddies out), but do the following:
Access to the LAN (wired network) is only allowed via openvpn, access from
the wireless network to the Internet I didn't restrict (which makes my Wii
and Blueray happy).
This setup serves me well and is pretty secure.

Heiko

[Devil-Linux-discuss] Please assist Devil Linux to provide our wireless internet access

[K.G.H. N. <kg...@tt...>]

Howdy from Montana, where it's 10 degrees F out, a good time to be inside working on our network.

We are longtime Devil Linux users.  For years, we have run Devil on a "gateway" Pentium machine, equipped with two ethernet boards, to protect our household LAN computers.

Now we want wireless, too, in addition to our wired network, which we want to keep.  I have assigned a computer to the updated job and we are trying to configure Devil Linux 1.4RC1, which I recently downloaded and burned to CDR.  (Configuration on floppy.)  The new gateway machine has:
	A) an on-motherboard Intel 82801 assigned to eth0, running Devil's e100 driver happily.  It is CAT5e connected to our Paradyne 6211 ADSL modem.
	B) a PCI RTL8029(AS) assigned to eth1, running the realtek driver happily.  It is CAT5e connected to our LAN.
	C) a PCI Belkin Wireless G Desktop Card - Atheros AR2413 802.11bg, assigned in Devil's setup to eth2. running the ath5k driver.  It is not happy on boot; Devil reports eth2 as [IPv4]SIOCSIFADDR No such device [FAILED].  I did ask Devil to set up DMZFW3, the three network-card firewall.

Our wireless testing equipment is scanty - we have two laptops with wireless.  One runs Ubuntu which did not work with the wireless on campus, and one runs Slackware with untested wireless.  (Being able to work on and test them is one reason we want wireless here.)  We also have a new Wii, which presumably has working wireless if we configure it right.

At this time, after a day's configuration work, our wired LAN members do have their normal access to the Internet through the new gateway.  I've put several hours into the wireless setup, and feel I'm to the point where I could really benefit from some help from experienced people who understand wireless setup for Devil.

Here's what I think I've figured out so far:
  ath5k sets up device wlan0, not eth2
I can log in the to gateway as root, and then interactively configure the wireless card:
  ifconfig wlan0 (LAN ip I want to point the wireless at, as the wireless gateway/access point) netmask 255.255.255.0
  iwconfig wlan0 essid (security alphanumeric SSID string, currently 8 chrs)
  ifconfig wlan0 down
  iwconfig wlan0 mode managed key (security WEP string hex 10 digits)
  ifconfig wlan0 up
ifconfig and iwconfig now see wlan0
save-config does not make these configuration changes last through the next boot, nor does going into setup and choosing "Save your configuration".

When I configure manually as shown above, ifconfig wlan0 says UP BROADCAST MULTICAST, but when I test with the Wii, it is not successful.  (Wii setup: Wireless connection/manual setup/SSID to match/WEP to match/advanced IPs/advanced DNSs/no proxy).  The Wii manual's troubleshooting says "check the signal strength", but doesn't explain how.  (I assume the default wlan0 Frequency: 2.412 GHz is OK for the Wii as the Wii manual does not specify what the unit can accept.)

I copied etc-mods.tar.bz2 from the Devil configuration floppy to another (Win2000pro) machine and used 7zip to extract etc-mods.tar, which can then be opened with WinZip.  The etc-mods\sysconfig\nic\ifcfg-eth2 file contains
DEVICE=eth2
ONBOOT=yes
MODULE="ath5k"
DHCP=no
IP="(LAN ip I want to point the wireless user machines at)"
NETMASK="255.255.255.0"
BROADCAST="(LAN ip I want to point the wireless users at except the last number is replaced by .255)"

I'd like to try setting DEVICE=wlan0, but I don't know how to put the changed file back into the archive so that it appears in the right place to Devil.

I've got the Devil 1.3 documentation up on another machine for reference.

Questions I'd love answered:
A) Is Devil's "DMZ" network card setup appropriate for what I'm trying to do?  I don't understand DMZ very well.  Wikipedia has a rundown at http://en.wikipedia.org/wiki/DMZ_%28computing%29, which I read with partial understanding.
B) How do I tell Devil to use wlan0 as eth2?
C) How do I get the wlan0 ip etc configuration to save/load?
D) iwconfig says wlan0's Access Point: Not-Associated.  Is this proper?
E) What range should I expect from the wireless service?  The wireless devices are a couple of rooms away from my gateway machine.  It's an old frame house.  Do I need to move the Wii closer to the gateway or vice versa to get a good test?

Thank you for your patience in reading through my description.  I look forward to comments and tips from those who know.

KGHN

Re: [Devil-Linux-discuss] 1.4RC2 Oopsing on me ...

[Serge L. <fi...@in...>]

Hi Frank,

On 11/30/2009 05:03 AM, Frank Weis wrote:
> Hi Serge,
> 
> I have 2 questions regarding this...
> 
> *) will VPN with MS clients work without the mppc/mppe module?
mppe without mppc will work (i.e. encryption without compression), but without
mppe at all it will not work (at least with default settings).

> *) I remember trying IAS a long time ago, and I didn't really like it,
> but I can't recall why.... Doesn't it need the user's password to be
> stored in a special way in AD to work?
No, there are no special steps to make it operable.

PS. I can send my configs if you want to have a working example.

Serge

> 
> Thanks a lot,
> 
> Frank
> 
> 
> 
> 
> Serge Leschinsky wrote:
>> Hi Frank,
>>
>> On 11/27/2009 07:17 AM, Frank Weis wrote:
>>> Hi all,
>>>
>>> I am testing pptp authentication against an AD backend with pppd's
>>> winbind plugin.. (I use this without trouble on several DL-1.2.x
>>> releases...)
>> Do you use mppc patch for DL 1.4? I see the latest mppe-mppc patch was from you.
>> I haven't tested it, but all my attempts to adapt mppc caused the same result -
>> oops in mppe_mppc module. If it's not critical, I'd suggest omitting this patch.
>>
>> I have the similar setup but pptpd authenticates against AD via RADIUS (IAS
>> service). It works.
>>
>> Serge