Network Bridge comes in handy. Its essentially the same as ICS, only more flexible, albeit less secure. You might want to have a firewall remain on your system with it.
Normally, using a series of commands will work when bridge-utils is installed, but they're only for the current session. We want to make it permanent.
Procedure to follow
1. Get bridge-utils through Synaptic. This is the software we'll use to create the Network Bridge.
sudo aptitude install bridge-utils
Now, keep in mind to either print this out or not exit your browser, because in this next step we'll stop the Networking Services to change them.
2. Open a terminal, and type
sudo /etc/init.d/networking stop
Keep the terminal open.
3. Now we're going to edit our interfaces file:
gksu gedit /etc/network/interfaces
Replace whatever is there with:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0 eth1
Save the changes.
4. Now we'll restart the Network Services
sudo /etc/init.d/networking start
And there we go. Your computer is now set up to automatically share its internet connection without dizzying settings for more advanced set-ups!
Have fun, and note longer boot-ups will occur due to creating the network upon boot.
Friday, 29 August 2008
Howto Share Internet Connections in Ubuntu
Posted by
Admin
at
17:51
1 comments
Labels: Share Internet Connections in Ubuntu, Share Internet Connections in Ubuntu hardy
Howto install manually nVidia drivers in Ubuntu
Firstly, go to the official nVidia website and download the official linux drivers. Of course nv's nice and all.. but I wouldn't use it over the real thing. Once you download the driver file (into your home folder), right click on it in nautilus (file browser), click properties, then permissions, checking the box that says "allow executing the file", then type into a TTY session ctrl+alt+f1-f3 (ctrl+alt+f7 to get back to GUI) and type in
sudo /etc/init.d/gdm stop
Which will stop your x-server.. (DON'T DO ANY OF THIS UNTIL YOU KNOW THE WHOLE PROCESS, BECAUSE TURNING BACK ON YOUR GRAPHICS COMES AT THE END!)
(Also note that this will be a text-only display! Remember or write down all the commands.) then hit
ls
to list the files in your home folder. Find the one with "nvidia" in it, and hit "sudo ./*nvidia filename*" it should install the "nvidia" driver on your computer. when it asks you whether or not you want to replace the existing "xorg.conf" file, let it do so. once that's done, type in "sudo /etc/init.d/gdm start" which will turn back on the graphical interface, allowing you to login again. (sorry. it logs you out of everything but the commandline part of ubuntu. save everything before you turn off gdm.) If your controls work perfectly in regards to the mouse and keyboard, rejoice, you're done! if your mouse isn't scrolling, or it's behaving funny.. you may have to hit alt+f2 (You'll still be in graphical mode after hitting this one. it's a nice little tool.), and type in
gksu gedit
then open your xorg.conf file (Usually in the "/etc/X11/" folder), looking somewhere other than me about how to fix that, if copying your "pointer" section doesn't fix it.
(Copying the pointer section worked for me, since I had it set up right in a previous xorg.conf file..)
Now, in case of kernel update, remember that the nvidia driver will NOT work without reinstallation. This is expected, so expect it. In this case, you'll be in CLI mode. Your previous driver installer will work just fine, I like to check for updates occasionally, just to be with the newest version.
Always make sure, with a new executable comes making it executable before trying to.. well.. execute it. With GDM (the graphical display) working, simply right click the file in the file browser and click properties, set it executable. In CLI: have the file in your home directory or know the directory it's in.. Then do "cd "/path/to/driver/" before finally setting it executable. Do this with "sudo chmod a+x "{driver file name}"" (You can use the ls command to once again list it exactly).
Now, execute the file by simply typing the filename into the command line. It will say there's a previous version installed, and ask to write over it. Do so. It shouldn't need to overwrite the xorg.conf file, as the NVIDIA driver's still being used. Don't let it and save some hassle.
So basically, set the file executable in the file browser, or use sudo chmod a+x "nvidiadrivernamehere", stop gdm if it's started (sudo /etc/init.d/gdm stop), then execute it, overwriting the driver, but not the xorg.conf. Then, start GDM back up (sudo /etc/init.d/gdm start)
If you overwrite the xorg configuration file (conf) just restore the backup. Look in the file browser (using alt+f2, typing in gksu nautilus and executing to get a root file browser. Needed for editing /boot/ files.) in "/boot/grub/" in list mode for the latest thing resembling .backup or .bak1 or something, listing files by date changed. delete the new xorg.conf, changing the name of xorg.conf.bak to xorg.conf.
So, in essence,
1: Download driver. Set as executable.
2: turn off graphics, going into only command line.
3: list files, execute driver installer.
4: follow installer's instructions, allowing it to replace your xorg.conf.
5: restart gdm. Hope everything goes smoothly.
6: *contingent upon condition in last step being met* DANCE! YOU WIN!
To reinstall,
1a: change file to executable if gdm's booted up through the properties prompt.
1b: do a sudo chmod a+x {filename} if it's not.
2a: kill gdm server (sudo /etc/init.d/gdm stop in CLI (ctrl+alt+f1)) proceed to 2b.
2b: execute file. (sudo ./NVIDIA-x86-173.x.x-pkg1.run (or -x86_64-))
3: Follow prompts, letting it overwrite the old driver. Don't let it overwrite xorg.conf unless it's been changed to use another driver.
4: Start gdm. (sudo /etc/init.d/gdm start)
5: Rejoice! If it worked before, it should work now! If it doesn't, despair. Boot from a livecd if you have one, or use a computer at a library to come here and flame me. It happens frequently.
Posted by
Admin
at
17:49
2
comments
Labels: nVidia drivers in Ubuntu, nVidia drivers in Ubuntu hardy
Saturday, 16 August 2008
Howto Setup Canon C3380/C3380i printer setup in Ubuntu 8.04(Hardy Heron)
Here are instructions for getting a Canon C3380/C3380i printer set up under Ubuntu 8.04 (Hardy Heron).
The printer is connected to via IPP, and in my case the printer requires authentication (username/password and mailbox authentication).
Drivers:
http://canon.codehost.com/
The normal system drivers (Generic->PCL 5c, etc.) will not work, because they do not have support for mailboxes (mailbox ID, password). If your printer is open to all and does not require mailbox authentication, then you may be able to use the normal system drivers.
The Codehost drivers are fully integrated with CUPS. Once installed you can print from any application without any special Codehost-specific process. Both color and black and white work.
NOTE: The most non-intutive part is that the username/password authentication for IPP and other protocols is not the same as mailbox authentication. Both must be specified, and this requires using the Codehost drivers.
Instructions:
1. Install the Codehost drivers
2. Using codehost-config:
- Add a Printer
- A remote printer using a network protocol
- Discover network printers
- Enter IP address of printer, select Any protocol, Start Discovery
- Expand the found printer
- Select IPP line
- Select Printer
- Enter Login/Password provided by the printer administrator (same as mailbox/password), Next
- Make sure the next window is maximized to edit the settings on the right hand side
- Under the Mode header
-- Job Mode: Print
-- Job Password: Empty
-- Mailbox number: Mailbox number provided by printer administrator
-- User ID: Mailbox number provided by printer administrator
-- Password: Mailbox password provided by printer administrator
- Next, Next
- Print Test Page, should work
- If you get an error when printing saying "can't prompt for authorization", or if Firefox seems to work but actually does not, then do this:
-- In codehost-config, right click on the printer and select Duplicate.
-- Now print to the duplicated printer and it should work.
Troubleshooting:
- Check the CUPS error log file, it is very useful.
- If you see "client-error-not-authorized", that means the mailbox authentication was not sent (most likely) or not accepted (less likely). This is the error you'll get when using the system drivers.
- You can log into the web interface for the printer and check the status of print jobs and see the log of previous print jobs.
- If you can't get the drivers working, you can also use the web interface on the printer to print PDFs and image files using Direct Print.
Wednesday, 13 August 2008
How to connect to HSDPA/3G trough USB with Ubuntu Linux and Windows Mobile 6
To connect your WM6 device via usb to your linux pc do the following
On your phone enable internet sharing via usb but do not connect the usb cable yet.
Run the following commands..you may need to install "svn" for this to work: (install by terminal: sudo apt-get install subversion)
svn co https://synce.svn.sourceforge.net/svnroot/synce/trunk/usb-rndis-lite/
cd usb-rndis-lite/
make
sudo ./clean.sh
sudo make install
Create the path "/etc/sysconfig/network/", in Hardy Heron the path "sysconfig/network/" doesnt exists, easy with nautilus trough terminal:
sudo nautilus
Nautilus opens, and browse to "/etc/" and create the path "sysconfig/network/" and futher. - Close nautilus.
The create the file "ifcfg-rndis0" in "/etc/sysconfig/network/", easy with gedit (gnome's text-editor) trough terminal:
sudo gedit /etc/sysconfig/network/ifcfg-rndis0
Fill the file with the text below:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU='1460'
MRU='1500'
NAME=''
PEERDNS=no
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='hotplug'
USERCONTROL='no'
_nm_name='static-0'
So, if you haven't start "Internet Sharing" on your WM-phone yet. Do it now..
- Now plug the phone into the usb cable going to the pc and if you do a "dmesg" you should see the following (or something similar):
[ 6539.589930] usb 5-1: USB disconnect, address 2
[ 6539.590829] rndis0: unregister 'rndis_host' usb-0000:00:1d.2-1, RNDIS device (SynCE patched)
[ 6540.972801] usb 5-1: new full speed USB device using uhci_hcd and address 3
[ 6541.019337] usb 5-1: configuration #1 chosen from 1 choice
[ 6541.628430] rndis0: register 'rndis_host' at usb-0000:00:1d.2-1, RNDIS device (SynCE patched), 80:00:60:0f:e8:00
and if you do an ifconfig you should have a new rndis0 device:
rndis0 Link encap:Ethernet HWaddr 80:00:60:0f:e8:00
inet addr:192.168.0.102 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::8200:60ff:fe0f:e800/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:8050 Metric:1
RX packets:3008 errors:2425 dropped:0 overruns:0 frame:225
TX packets:2993 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1915412 (1.8 MB) TX bytes:763519 (745.6 KB)
----
The rndis0 device will exist both when internet sharing is enabled via usb and when it is NOT....here is how it works:
If internet sharing IS enabled via usb you have access to the internet and will get an IP...default route will be set.
If internet sharing is NOT enabled via usb then the rndis0 device will exist and can be used by programs such as syncE to manage your contact list or transfer files but you will not have internet access (from the phone) and more than likely you will not get an ip address auto assigned (it may keep the ip it used last).
How to setup ndiswrapper with BT Voyager 1055 in Ubuntu
The guide should be the same whichever wireless adapter you have (I cannot see why it would not work if you had the correct drivers but someone more experienced in Linux is probably going to correct me on this) – you will just need the .inf and .sys driver files which should be installed under windows (mine were located here - “C:\Program Files\BT\BT Voyager”).
Step 1
Using the file manager in Ubuntu I mounted my windows xp drive and navigated to the above folder. Select the relevant driver files (for the BT Voyager 1055 they are usb8023.sys, RNDISMP.sys and bcmrndis.inf) and copy them to the Ubuntu desktop.
Step 2
Install the latest version of ndiswrapper. I used the Synaptics package manager, searched the cd for packages and selected ndisgtk which also installed the other two ndiswrapper files however you can use the command line – sudo apt-get install ndisgtk
Step 3
In Terminal type “cd Desktop” which will move you to the desktop directory and type
sudo ndiswrapper –i bcmrndis.inf (you will be asked for your user password and you should get an error message which states it will create the file anyway – just ignore and carry on with next steps).
This will copy the bcmrndis.inf to the ndiswrapper folder.
Step 4
Type:
sudo cp –v usb8023.sys RNDISMP.sys /etc/ndiswrapper/bcmrndis/
This will copy the sys files to the ndiswrapper folder.
Extra step if you are using this guide to install a different wireless adaptor otherwise skip to next step:
Type:
lsusb //Note: Is lowercase L
This will bring up a list of all the attached devices for your usb ports. Locate you wireless device in the list and you will see a set of numbers next to it – for BT it was 1690:0715. Make a note of these two numbers.
Step 5
You must now create the hardware configuration file by typing:
sudo gedit /etc/udev/rules.d/99-custom.rules
This will open the text editor for GNOME (KDE users replace gedit with kate) with a blank page. Copy the attached text and save and exit the text editor.
#START**
BUS=="usb",
SYSFS{idProduct}=="0715",
SYSFS{idVendor}=="1690",
RUN+="/bin/sh -c 'echo 1 > /sys/$devpath/device/bConfigurationValue'"
#END**
Please note the single and double quotes on the RUN line which need to be included or your configuration file will not work. If you are installing a different adapter you will need to substitute the two SYSFS numbers above with the ones for your card (see extra step above). After running lsusb BT Voyager shows as 1690:0715 with the first 4 numbers being the idVendor and the second set being the id Product
Step 6
Check the installation by typing:
sudo ndiswrapper –l //Note: Is lowercase L
You should see a message stating Driver: installed and Device: present. This means you have successfully setup the wireless adaptor (if you don't see Device: present unplug your adapter, plug back in and run the above command).
Type:
sudo depmod –a
sudo modprobe ndiswrapper
On the top toolbar, at the right hand side (near the date and time), there will be a icon of a terminal. Left click here and you should see the wireless networks in your area. Click on the network you wish to associate to. If you have security setup up on your router you should be presented with a window to enter your security key.
I had some difficulty with this as I could not connect to my router when security was enabled (even though the router and wireless dongle both support all the current encryption methods) so I had to disable my security through the router and change the mac address table so that only my adapter's mac address can connect to the router. I know this is not the safest of options as mac address spoofing is quite simple to do but it will do for now until I get chance to conduct further tests on the security.
In order to connect to your network each time you boot type:
sudo gedit /etc/modules
And add ndiswrapper to the list that appears in the editor, save and close.
Monday, 11 August 2008
How to Install aMSN 0.98b with anti-aliasing in Ubuntu
Install aMSN 0.98b with anti-aliasing in Ubuntu
Step 1
Open a terminal session by pressing "Alt+F2" then typing "gnome-terminal". Make sure your computer is connected to the Internet.
Step 2
Install the g++ compiler (can be skipped if already installed)
First, you need to make sure the g++ compiler is installed on you computer. At the prompt, simply enter the following code
sudo aptitude install g++
Step 3
Install subversion (can be skipped if already installed)
We are going to download the aMSN source code via subversion, so you need to have it installed. At the prompt, simply enter the following code
sudo aptitude install subversion
Step 4
Install the latest tcl/tk libraries
Since aMSN is written in tcl/tk, we need to download the latest libraries in order to compile properly. The good news is that v8.5 supports anti-aliasing. At the prompt, simply enter the following code
sudo aptitude install tk8.5-dev
It should install everything you need to compile aMSN, including the tcl8.5 libraries.
Step 5
Get the aMSN source code
Simply enter the following code at the prompt
svn co https://amsn.svn.sourceforge.net/svnroot/amsn/trunk/amsn amsn
This will download all the source code in your home directory. For more info, visit this page http://www.amsn-project.net/wiki/Enabling_antialiasing
Step 6
Build aMSN
Change your working directory by entering
cd amsn
Then you use the usual commands to build the app.
./configure
make
sudo make install
Now, some people have experienced problems while running the configure script, something about the tcl/tk libraries not found. If you experience such a problem, or if your compiler builds using an old version of tcl/tk, use the following commands instead
./configure --with-tcl=$HOME$INST_PATH/lib --with-tk=$HOME$INST_PATH/lib
make
sudo make install
And that's it! You should find your shiny new aMSN under Applications->Internet->aMSN.