Hello,
I have been using Paldo for some time on virtual machines, but now I decided to install it on my Toshiba laptop (ia64). I had Slackware, but needed a native 64 bit distro (no, I didn't like Slamd64) for my VMWare experiments. First of all the installer didn't add the Vista partition to the GRUB config. It's easy to fix for the most users, but I think it would be cool to add such functionality to the installer. Now I'm having some bigger trouble with the NetworkManager. It's constantly crashing on startup and you can see the (not very helpful) details here.
I'm not familiar with the /etc/network/interfaces file and I don't know if the problems are connected, but I'm not able to connect to my wireless network with this config:

Code	[In neuem Fenster öffnen]
auto lo iface lo inet loopback iface default inet dhcp auto wlan0 iface wlan0 inet static wpa-driver wext wpa-conf /etc/wpa_supplicant.conf address 192.168.0.44 netmask 255.255.255.0 gateway 192.168.0.1

And I had to write a shell script instead:

Code	[In neuem Fenster öffnen]
sudo wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -Bw sudo ifconfig wlan0 192.168.0.44 netmask 255.255.255.0 up sudo route add default gw 192.168.0.1

Any ideas how to fix the "interfaces" file in order to use static IP with wpa_supplicant?
By the way, no flaming, but I think the wireless config in Slackware was a bit more simple and fast.
I will appreciate any help, thanks in advance! And sorry for my broken English.
 
..............................
Do less. Live longer.

Paldo uses NetworkManager by default for managing all network interfaces. Unfortunately, NetworkManager 0.6 doesn't support static ip addresses yet (planned for next major version). To use static ip addresses in paldo, you need to disable NetworkManager by editing /etc/default/NetworkManager (TRUE into FALSE). You can set the static ip address in /etc/network/interfaces, exactly the same as in Debian (see man interfaces for details). Or read my guide:

Paldo and static IP

Your main network configuration file is /etc/network/interfaces

Desired new sample settings:
=> Host IP address 192.168.1.100
=> Netmask: 255.255.255.0
=> Network ID: 192.168.1.0
=> Broadcast IP: 192.168.1.255
=> Gateway/Router IP: 192.168.1.254
=> DNS Server: 192.168.1.254

Open network configuration file

Code	[In neuem Fenster öffnen]
$ sudo vi /etc/network/interfaces

OR

Code	[In neuem Fenster öffnen]
$ sudo nano /etc/network/interfaces

Find and remove dhcp entry:

Code	[In neuem Fenster öffnen]
iface eth0 inet dhcp

Append new network settings:

Code	[In neuem Fenster öffnen]
iface eth0 inet static address 192.168.1.100 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.254

Save and close the file. Restart the network:

Code	[In neuem Fenster öffnen]
$ sudo /etc/init.d/network restart

Task: Define new DNS servers

Open /etc/resolv.conf file

Code	[In neuem Fenster öffnen]
$ sudo vi /etc/resolv.conf

You need to remove old DNS server assigned by DHCP server:
search myisp.com

Code	[In neuem Fenster öffnen]
nameserver 192.168.1.254 nameserver 202.54.1.20 nameserver 202.54.1.30

Save and close the file.

Task: Test DNS server

Code	[In neuem Fenster öffnen]
$ host cyberciti.biz

Network command line cheat sheet

You can also use commands to change settings. Please note that these settings are temporary and not the permanent. Use above method to make network changes permanent or GUI tool as described below.

Task: Display network interface information

Code	[In neuem Fenster öffnen]
$ ifconfig

Task: Take down network interface eth0 / take a network interface down

Code	[In neuem Fenster öffnen]
$ sudo ifconfig eth0 down

OR

Code	[In neuem Fenster öffnen]
$ sudo ifdown eth0

Task: Bring a network interface eth0 up

Code	[In neuem Fenster öffnen]
$ sudo ifconfig eth0 up

OR

Code	[In neuem Fenster öffnen]
$ sudo ifup eth0

Task: Change IP address and netmask from command line

Activate network interface eth0 with a new IP (192.168.1.50) / netmask:

Code	[In neuem Fenster öffnen]
$ sudo ifconfig eth0 192.168.1.50 netmask 255.255.255.0 up

Task: Display the routing table

Code	[In neuem Fenster öffnen]
$ /sbin/route

OR$

Code	[In neuem Fenster öffnen]
/sbin/route -n

Output:

Code	[In neuem Fenster öffnen]
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface localnet * 255.255.255.0 U 0 0 0 ra0 172.16.114.0 * 255.255.255.0 U 0 0 0 eth0 172.16.236.0 * 255.255.255.0 U 0 0 0 eth1 default 192.168.1.254 0.0.0.0 UG 0 0 0 ra0

Task: Add a new gateway

Code	[In neuem Fenster öffnen]
$ sudo route add default gw 172.16.236.0

Task: Display current active Internet connections (servers and established connection)

Code	[In neuem Fenster öffnen]
$ netstat -nat

Task: Display open ports

Code	[In neuem Fenster öffnen]
$ sudo netstat -tulp

OR

Code	[In neuem Fenster öffnen]
$ sudo netstat -tulpn

Task: Display network interfaces stats (RX/TX etc)

Code	[In neuem Fenster öffnen]
$ netstat -i

Task: Display output for active/established connections only

Code	[In neuem Fenster öffnen]
$ netstat -e $ netstat -te $ netstat -tue

Where,

• -t : TCP connections
  
• -u : UDP connections
  
• -e : Established

Task: Test network connectivity

Send ICMP ECHO_REQUEST to network hosts, routers, servers etc with ping command. This verifies connectivity exists between local host and remote network system:

Code	[In neuem Fenster öffnen]
$ ping router $ ping 192.168.1.254 $ ping cyberciti.biz

See simple Linux system monitoring with ping command and scripts for more information.

A man page is your best friend when you wanted to learn more about particular command or syntax. For example, read detailed information about ifconfig and netstat command:

Code	[In neuem Fenster öffnen]
$ man ifconfig $ man netstat

Just get a short help with all command options by appending --help option to each command:

Code	[In neuem Fenster öffnen]
$ netstat --help

Find out what command is used for particular task by searching the short descriptions and manual page names for the keyword:

Code	[In neuem Fenster öffnen]
$ man -k 'delete directory' $ apropos -s 1 remove

Display short descriptions of a command:

Code	[In neuem Fenster öffnen]
$ whatis rm $ whatis netstat

Linux offers an excellent collection of utilities, which can be use to finding the files and executables, remember you cannot memorize all the commands and files.

Sorry for my perfect English

Thanks for the advice, I have already "defused" NetworkManager with the dirty "chmod a-x /etc/init.d/NetworkManager*", this is a nicer one. But I don't think that should be its normal way to "cope" with static config. There is an assertion so it's likely to be a bug. And this one is reported in some bugtrackers of other distros. There is a newer NetworkManager in the unstable branch, but I don't want to break other things with the upgrade.
I fixed the problem with the netconfig too. I found that I should invoke wpa_supplicant in the documentation from other distros so I tried:

Code	[In neuem Fenster öffnen]
auto lo iface lo inet loopback iface default inet dhcp auto wlan0 iface wlan0 inet static pre-up wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -Bw post-down killall wpa_supplicant address 192.168.0.44 netmask 255.255.255.0 gateway 192.168.0.1

But it seems that wpa_supplicant is called automatically anyway. So I removed the directives to launch (or kill it):

Code	[In neuem Fenster öffnen]
auto lo iface lo inet loopback iface default inet dhcp auto wlan0 iface wlan0 inet static address 192.168.0.44 netmask 255.255.255.0 gateway 192.168.0.1

Nothing wpa-related in the interfaces file and now everything works perfectly.
 
..............................
Do less. Live longer.

Good to read that you fixed your problem. Have fun with paldo ...

Hi, I had this problems with network and it's works for me... thanks Amnon82
 
..............................
Paldo 1.19 - testing - gnome 2.28