Scratch

I think you would just go to 192.168.1.254 in your browser and then login. After that you should be able to configure your network/ip address normally. In the router I think you can set a static Internal IP if you know the MAC Address of your computer's wireless device.

I guess another way you can do it is open Network Connections select the Access Point you are using, click 'Edit', 'IPv4 Settings' change 'Method' to 'Manual', click '+Add', then input 192.168.1.93 for Network, 255.255.255.0 for Netmask (I think), and 192.168.1.254 for the Gateway.

The second way probably isn't something you should mess with (unless you are just using a network switch without a router/DNS server which in some cases you may need to do), but it works.

Last edited by Magnie (2012-12-27 21:29:30)

GeonoTRON2000 wrote:

Magnie wrote:

I think you would just go to 192.168.1.254 in your browser and then login. After that you should be able to configure your network/ip address normally. In the router I think you can set a static Internal IP if you know the MAC Address of your computer's wireless device.

I guess another way you can do it is open Network Connections select the Access Point you are using, click 'Edit', 'IPv4 Settings' change 'Method' to 'Manual', click '+Add', then input 192.168.1.93 for Network, 255.255.255.0 for Netmask (I think), and 192.168.1.254 for the Gateway.

The second way probably isn't something you should mess with (unless you are just using a network switch without a router/DNS server which in some cases you may need to do), but it works.

The trouble is, I need to connect the computer to the network.  All I have is shell access.

Are you using ethernet or wireless? With ethernet it should auto connect, and with wireless, you might need to configure some drivers and install some software.

Last edited by pwiter (2012-12-27 22:46:52)

GeonoTRON2000 wrote:

pwiter wrote:

GeonoTRON2000 wrote:

The trouble is, I need to connect the computer to the network.  All I have is shell access.

Are you using ethernet or wireless? With ethernet it should auto connect, and with wireless, you might need to configure some drivers and install some software.

I'm using wireless.

Run ifconfig to see what interface your wireless card is, it is normally wlan0 or eth1.

I know need to know if your wireless access point is wpa or wpa2, or wep(I don't recommend it).

Last edited by pwiter (2012-12-27 23:28:32)

Just to say something about pwiter not recommending WEP, WPA and WPA2, if you disable that, you are bringing down your network security by A LOT. Dont do it. Do YOU want your neighbours using your internet?

GeonoTRON2000 wrote:

pwiter wrote:

GeonoTRON2000 wrote:

I'm using wireless.

Run ifconfig to see what interface your wireless card is, it is normally wlan0 or eth1.

I know need to know if your wireless access point is wpa or wpa2, or wep(I don't recommend it).

wlan0 and wpa2

Ok, first thing you have to do is installl wpa_supplicant with

apt-get install wpasupplicant

it might be already installed. 

Next, you want to find the hex version of your passkey. This can be done by

wpa_passphrase ssid password

where the ssid is your ssid, and the password is the password. It will now come up with something like this:

 network={
        ssid="ssid"
        #psk="password"
        psk=24f87a7583001eb7cea2394bbdb04eb2d3641f0b907dd31bd286be628c1841f8
}

You will now need to put this into your /etc/wpa_supplicant.conf file with the command

wpa_passphrase ssid password > /etc/wpa_supplicant.conf

again where ssid is your ssid and the password is your password.

Now we need to configure some things. Run:

sudo nano /etc/wpa_supplicant.conf

You will now enter the file that has a network block. Enter

scan_ssid=1

underneath the ssid line. And you can also set priority(optional) by entering

  priority = 5

It will always go with the highest number.

Now you must configure a wpa startup script. You can do this by

sudo nano /etc/init.d/wpa.sh

Type this inside

#!/bin/bash
### BEGIN INIT INFO
# Provides:          wpa
# Required-Start:    $network $syslog $local_fs
# Required-Stop:     $network $syslog $local_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start/stop script for wpa supplicant
# Description:       Custom start/stop script for wpa_supplicant.
### END INIT INFO

SELF=`basename $0`
WPA=wpa_supplicant
PROGRAM=/sbin/${WPA}
CONF=/etc/${WPA}.conf
INTERFACE=wlan0
DRIVER=wext
DAEMONMODE="-B"
LOGFILE=/var/log/$WPA.log

function start() {

    # TODO: Support multiple interfaces and drivers
    OPTIONS="-c $CONF -i $INTERFACE -D $DRIVER $DAEMONMODE"

    ## You can remove this if you are running 8.10 and up.
    # Ubuntu 8.10 and up doesn't need the -w anymore..
    # And the logfile option is not valid on 8.04 and lower
    local ver=$(lsb_release -sr | sed -e 's/\.//g');
    [ $ver -lt 810 ] && OPTIONS="$OPTIONS -w" && LOGFILE=""
    ##

    # Log to a file
    [ -n "$LOGFILE" ] && OPTIONS="$OPTIONS -f $LOGFILE"

    echo " * Starting wpa supplicant"
    eval $PROGRAM $OPTIONS
}

function stop() {
    echo " * Stopping wpa supplicant"
    pkill $PROGRAM
}

function debug() {
    stop
    DAEMONMODE="-ddd"
    start
}

function restart() {
    stop
    start
}

function status() {
    pgrep -lf $PROGRAM
}

function usage() {
    echo "Usage: $SELF <start|stop|status|debug>"
    return 2
}

case $1 in
    start|stop|debug|status) $1 ;;
    *) usage ;;
esac

Then, chmod it by

sudo chmod +x /etc/init.d/wpa.sh

Now you can start wpa with

/etc/init.d/wpa.sh start

Let's make it start on startup by running

sudo update-rc.d wpa.sh defaults

Congratz! You can now reload network with

sudo /etc/init.d/networking restart

You can also edit your config file with

sudo wpa_cli

This is where you can configure static ips.

Last edited by pwiter (2012-12-28 08:52:03)

GeonoTRON2000 wrote:

pwiter wrote:

[Instructions]

I did all of that.  I tried a wget and I get:

Code:

--2012-12-28 02:30:49--  http://img.thegt.org/trolgle.png
Resolving img.thegt.org (img.thegt.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address `img.thegt.org`

Hm...
I forgot to check if your wireless card had drivers.

Just check the ubuntu documentation as I am too lazy to write more steps 

Last edited by pwiter (2012-12-28 16:50:32)

You should probably just stick a normal Ubuntu installation on the computer instead.

Or, put ubuntu server back on and configure it in the setup this time 

GeonoTRON2000 wrote:

Zeusking19 wrote:

Or, put ubuntu server back on and configure it in the setup this time 

Yeah, I tried that, but it's set up to use ethernet.

Generally servers are supposed to be connected to the internet via an ethernet cable. Unless you know exactly what you are doing, you should just stick with a normal install.