[01:33] <cheeseboy> hi
[01:33] <cheeseboy> why cant i ping my server?
[01:33] <cheeseboy> but it can ping other pcs
[01:33] <cheeseboy> and other pcs can ping other pcs
[01:34] <cheeseboy> internet is working
[03:22] <cheeseboy> anyone there
[03:37] <olem> yap
[03:38] <cheeseboy> cal u help
[03:38] <cheeseboy> can*
[03:39] <olem> beg you pardon? 
[03:41] <olem> have you got any problem/issue?
 why cant i ping my server?
 but it can ping other pcs
 and other pcs can ping other pcs
 internet is working
[03:41] <olem> netmask issue?
[03:41] <cheeseboy> how i check?
[03:41] <olem> I mean, perhaps you set a incorrect netmask value on your server, for example:
[03:41] <olem>  . you're on (V)LAN /26
[03:41] <olem>  . you set a /24 netmask on your server
[03:41] <olem>  . so your server can ping others
[03:41] <olem>  . while other cannot
[03:41] <cheeseboy> i dont rember setting that
[03:41] <cheeseboy> ever
[03:41] <cheeseboy> put it can ping others
[03:42] <olem> see your network admin, he will probably help you better than I (I dunno you network plan)
[03:42] <cheeseboy> im network admin
[03:42] <olem> yes. you can if you've got a broader netmask (and are in the same wire)
[03:42] <olem> ah.
[03:42] <olem> so you're sure about your netmask on your server?
[03:42] <cheeseboy> no
[03:42] <olem> I mean, sure to be the correct one?
[03:43] <cheeseboy> dunno how to check or change
[03:43] <olem> to check, see /etc/network/interfaces
[03:44] <olem> for example, a valid entry could be:
[03:44] <olem> iface eth0 inet static
[03:44] <olem>  address 192.168.1.2
[03:44] <olem>  network 192.168.1.0
[03:44] <olem>  netmask 255.255.255.0
[03:44] <olem>  broadcast 192.168.1.255
[03:44] <olem>  gateway 192.168.100.1
[03:44] <cheeseboy> eth1 is set
[03:44] <cheeseboy> but supposed to be eth0
[03:45] <cheeseboy> olem so if i change to eth0 think thayll fix it?
[03:46] <olem> can you issue an 'sudo mii-tool' to see what iface is connected out there ?
[03:46] <cheeseboy> i usally dhclient eth0 to bring internet up
[03:46] <olem> can you copy/paste here your /etc/network/interfaces ?
[03:46] <cheeseboy> how?
[03:47] <cheeseboy> i have no x
[03:47] <olem> ah... then... manually copy past it :-)
[03:47] <olem> (albeith you have mouse support of course)
[03:47] <cheeseboy> X(
[03:47] <cheeseboy> ??
[03:48] <olem> so, what you're /etc/network/interfaces tells us about eth0 and eth1 ?
[03:48] <cheeseboy> auto lo
[03:48] <cheeseboy> iface lo inet loopback
[03:48] <olem> ok - fine
[03:48] <olem> next
[03:48] <cheeseboy> that all u want?
[03:49] <olem> next : eth0 and eth1
[03:49] <olem> lo is the loopback iface (lo0/127.0.0.1)
[03:49] <cheeseboy> iface eth0 inet static
[03:49] <cheeseboy> i just changed from eth1
[03:50] <cheeseboy> adress 192.168.1.102
[03:50] <cheeseboy> netmask 255.255.0
[03:50] <cheeseboy> gateways wrong too
[03:50] <cheeseboy> h/o
[03:51] <cheeseboy> gateway 192.168.1.1
[03:51] <cheeseboy> auto eth0
[03:51] <cheeseboy> thats it
[03:51] <olem> ok. I see the following error: s/adress/address/
[03:52] <cheeseboy> ??
[03:52] <olem> and, are you sure to be on a Class B network (/16) ? not in a Class C (/24) ?
[03:52] <cheeseboy> no i dont even know what that means
[03:52] <olem> I guess your in a Class C. If so, your issue is 'netmask 255.255.0' which should be 'netmask 255.255.255.0'
[03:53] <olem> Class B network are 'large' network from 16xxx addresses.
[03:53] <cheeseboy> oh yea it is that
[03:53] <cheeseboy> typo my bad
[03:53] <cheeseboy> how i reset all my internet on ubuntu?
[03:53] <olem> Class C are 'tiny' networks (even if your may subnet them in tinier ones) for 255 addresses
[03:54] <olem> what do you mean by "resetting all my internet"?
[03:54] <cheeseboy> disconnect reconnect w/ new settings
[03:54] <olem> If you want to 'restart your network' to apply new parameters, you just have to issue 'sudo /etc/init.d/networking restart'
[03:55] <olem> but be sure of your parameters prior to network restart... if you're teleworking :-)
[03:55] <cheeseboy> failed to bring up eth0
[03:55] <olem> sudo tail -f /var/log/messages ?
[03:56] <olem> could inform you about why
[03:57] <cheeseboy> not much info there
[03:57] <olem> ok. so, you should issue an 'sudo mii-tool'
[03:57] <olem> to see to what physical iface you've got a jack plugged in.
[03:57] <olem> (to be sure about eth0 and eth1)
[03:58] <cheeseboy> fails on both
[03:58] <olem> for example, on my laptop, I don't use eth0 and when I issue 'sudo mii-tool', it returns me something like :
[03:58] <olem> olem@lembox:~$ sudo mii-tool 
[03:58] <olem> eth0: no link
[03:58] <olem> SIOCGMIIPHY on 'eth1' failed: Operation not supported
[03:58] <cheeseboy> yes
[03:58] <olem> to tell me:
[03:58] <olem>  . hey dude, no cable in eth0 ('no link')
[03:58] <cheeseboy> cept  oppisite eth0 and eth 1
[03:59] <cheeseboy> eth1 no link
[03:59] <cheeseboy> eth0 that other error
[03:59] <olem>  . hey dude, I cannot stat about your eth1 (cause it's the wireless iface, and don't support this interrogation)
[03:59] <olem> what does eth0 tells?
[03:59] <olem> exactly
[03:59] <cheeseboy> yes its wireless
[04:00] <olem> So, you'r mii-tool reports that :
[04:00] <olem>  . eth1 is a wired interface, with no link (no cable in)
[04:00] <olem>  . eth0 ??? (I did not understand)
[04:00] <olem> ?
[04:00] <cheeseboy> no..
 eth0: no link
 SIOCGMIIPHY on 'eth1' failed: Operation not supported
[04:01] <cheeseboy> cept switch et1 w/ eth0
[04:01] <olem> so you're mii-tool tells you that:
[04:02] <olem>  . SIOCGMIIPHY on 'eth0' failed: Operation not supported
[04:02] <olem>  . eth1: no link
[04:02] <olem> ?
[04:02] <cheeseboy> yes
[04:02] <olem> and your /etc/network/interfaces is configured this way:
[04:02] <olem> auto lo0
[04:02] <olem> oups...
[04:02] <olem> auto lo
[04:02] <olem> iface lo inet loopback
[04:02] <olem> # wireless
[04:03] <olem> iface eth0 inet dhcp
[04:03] <olem> # wired
[04:03] <olem> iface eth1 inet static
[04:03] <olem> address 192.168.1.102
[04:03] <cheeseboy> eth0 and eth1 are wireless
[04:04] <cheeseboy> but eth1 doesnt work
[04:04] <cheeseboy> and i have eth0 configures as static
[04:04] <cheeseboy> so i can rember ip easier
[04:05] <olem> hum... strange mii-tools returned a eth1 with 'no link' if it's a wireless iface... but, well, who knows (perhaps some drivers support this PHy...)
[04:05] <olem> anyway, can you please spell me the /etc/network/interfaces relating to eth0, to be sure there is no issue?
[04:06] <cheeseboy> auto lo
[04:06] <cheeseboy> iface lo inet loopback
[04:06] <cheeseboy> iface eth0 inet static
[04:07] <cheeseboy> adress 192168.1.102
[04:07] <cheeseboy> netmask 255.255.2550
[04:07] <olem>   ==> be sure to have exactly : address 192.168.1.102
[04:07] <cheeseboy> ya typos here
[04:07] <olem> (2 'd' to address)
[04:07] <olem> ok. 
[04:07] <olem> and netmask 255.255.255.0 :)
[04:07] <cheeseboy> gateway 192.168.1.1
[04:08] <cheeseboy> auto eth0
[04:08] <olem> add (before auto eth0) :
[04:08] <olem>  network 192.168.1.0
[04:08] <olem>  broadcast 192.168.1.255
[04:09] <olem> and /etc/init.d/networking restart again
[04:09] <olem> (after saving the file of course :)
[04:09] <cheeseboy> olem
[04:10] <cheeseboy> failed to bring up eth0
[04:10] <olem> ok :(
[04:10] <olem> can you comment all the declarative parts for you eth0 and try these ones:
[04:10] <olem> iface eth0 inet dhcp
[04:10] <olem> auto eth0
[04:11] <olem> and (save) /etc/init.d/networking restart ?
[04:11] <cheeseboy> ya h/o
[04:11] <olem> just to see
[04:11] <cheeseboy> dhclient brings it up
[04:11] <olem> what does your ifconfig (or ip addr show) returns?
[04:12] <olem> regarding eth0 of course
[04:12] <cheeseboy> 192.168.1.102 wen i use dhclient
[04:12] <olem> netmask/broadcast/ ?
[04:13] <cheeseboy> ??
[04:14] <olem> 'ip addr show' should returns you something like that, relating to eth1 :
[04:14] <olem> inet 192.168.1.102/24 brd 192.168.1.255 scope global eth1
[04:14] <olem> s/eth1/eth0 :) 
[04:15] <olem> In fact, if you can negociate an @IP via DHCP and ping outside, you are sure you wireless conf is okay (wpa_supplicant.conf I suppose)
[04:16] <cheeseboy> i nvr touched it
[04:16] <olem> So, if your /etc/network/interfaces configured in static mode (iface eth0 inet static, and all the stuff) does not bring up your iface, the problem is in the /etc/network/interfaces : a typo error or something like that
[04:17] <Burgundavia> olem: can you pastebin your /etc/network/interfaces?
[04:17] <olem> From my point of view, with what I understand of your network topology, your /etc/network/interfaces should be exactly this one :
[04:17] <olem> # loopback
[04:17] <olem> auto lo
[04:17] <Burgundavia> olem: ahh, pastebin
[04:17] <olem> iface lo inet loobpack
[04:17] <olem> # eth0 - wireless but static
[04:17] <olem> auto eth0
[04:17] <cheeseboy> Burgundavia, olem is helping me w/ the problem
[04:18] <olem> iface eth0 inet static
[04:18] <Burgundavia> right, sorry
[04:18] <olem>  address 192.168.1.102
[04:18] <olem>  network 192.168.1.0
[04:18] <olem>  netmask 255.255.255.0
[04:18] <olem>  broadcast 192.168.1.255
[04:19] <cheeseboy> i had those but in different order
[04:19] <olem>  gateway 192.168.1.XXX (I dunno what is your gw, but you should)
[04:19] <Burgundavia> olem: please use pastebin next time
[04:19] <olem> place them in that order (I'm not sure this will impact)
[04:19] <Burgundavia> you also will want a auto eth0 before the iface line
[04:19] <cheeseboy> thats what it said
[04:19] <olem> Burgundavia, why do you want me to c/p my /etc/network/interfaces with all my gory comments in there? :)
[04:20] <Burgundavia> olem: because I thought you were cheeseboy
[04:20] <Burgundavia> cheeseboy can you pastebin that file?
[04:20] <cheeseboy> no
[04:20] <cheeseboy> no x
[04:20] <olem> Burgundavia, I dunno what the hell you're drinking, but I'm okay for the same thing ;)
[04:21] <olem> uh... 4:20 AM! I'm gonna go to bed... 
[04:21] <cheeseboy> where i put auto eth0?
[04:22] <cheeseboy> wait olem
[04:22] <cheeseboy> i need help :(
[04:22] <olem> you can put 'auto eth0' before, or after the declaration segment for an iface.
[04:22] <olem> usually, I place them in the begining of my /etc/network/interfaces
[04:22] <olem> like: 
[04:22] <olem> auto lo
[04:22] <olem> auto eth0
[04:22] <olem> auto eth1
[04:23] <olem> and then, I declare those interfaces (lo, eth0 and eth1)
[04:23] <olem> but, well, you can in fact place the 'auto' directive anywhere in you file, excepted in a declarative bloc
[04:23] <olem> (man interfaces for more
[04:24] <olem> ok. I'm gonna go to bed. 
[04:24] <cheeseboy> X(
[04:24] <olem> cheeseboy, cross check your /etc/network/interfaces with Burgundavia 
[04:24] <cheeseboy> it broke worst
[04:24] <cheeseboy> now says network is down
[04:24] <Burgundavia> cheeseboy: can you pm me that file then?
[04:25] <olem> I' pretty sure you've got an error in it. It's trivial to correct, if you repeat _exactly_ your /etc/network/interfaces here.
[04:25] <olem> thx Burgundavia :)
[04:25] <olem> seeya
[04:25] <cheeseboy> Burgundavia, how?
[04:25] <cheeseboy> Burgundavia, i have to type it all :(
[04:27] <cheeseboy> Burgundavia, wait it just magically fixed
[04:27] <cheeseboy> X(
[04:29] <cheeseboy> how i add samba user and pass?  
[05:37] <foo> w22
[04:35] <massctrl> hi all, does ubuntu server have xen packages?
[04:42] <necrite_> hi all
[04:43] <lionel> hi necrite_
[04:43] <lionel> massctrl: yes, xen packages are in ubuntu server. 
[04:44] <massctrl> tnx lionel
[04:44] <massctrl> I have found a link meanwhile
[04:50] <massctrl> k I'm not familiar with ubuntu-server, what's the default mailserver ?
[04:50] <massctrl> is it exim like Debian's ?
[05:13] <lionel> massctrl: no one is installed by default
[06:16] <massctrl> lionel: ok good to know, docs are talking about postfix,... https://help.ubuntu.com/ubuntu/serverguide/C/email-services.html 
[06:16] <massctrl> my fav anyway ;-)
[06:16] <massctrl> by the way anyone knows if there are any hardware vendors that will support ubuntu server ?
[06:16] <lionel> I would also advice postfix, but you're free to choose :)
[06:17] <massctrl> I mean Hp is offering commercial debian support, which is kind of nice, ... but i'm not that keen on debian,...
[06:17] <lionel> massctrl: I use Dell, HP is also well supported (as used in Canonical DC :))
[07:09] <Ali_ix> hi
[07:09] <Ali_ix> does apt-pinning work on ubuntu at all?
[07:09] <Ali_ix> how do i get it working on feisty?
[07:52] <shawarma> It just does.
[07:52] <shawarma> If that's all the detail you're going to give, all I can say is: it already works.
[08:26] <Ali_ix> thanks shawarma,
[08:27] <Ali_ix> shawarma: i want to exclude linux-headers and linux-image package to being updated with auto update,
[08:27] <Ali_ix> how can i do this? which priority  to set?
[09:08] <shawarma> Ali_ix: Just put them on hold.
[09:08] <shawarma> Ali_ix: Much easier.
[09:08] <shawarma> Ali_ix: Heck, it's even easier than that. :)
[09:08] <Ali_ix> shawarma: on hold? ho to do this?
[09:08] <shawarma> Ali_ix: Just remove linux-image.
[09:09] <shawarma> Ali_ix: Not linux-image-2.6.whatever, but linux-image and either linux-image-server or linux-image-generic.
[09:09] <shawarma> Ali_ix: Those are the packages that depend on the newest and hence it's them that take care of having your kernel uptodate.
[09:09] <shawarma> Ali_ix: Why do you want to do this?
[09:10] <Ali_ix> shawarma: i have some good and stable config with 2.6.20-13 kernel on ubuntu, and dont need any kernel update now :}
[09:10] <Ali_ix> shawarma: i want to exclude kernel-related packages fro auto update
[09:10] <shawarma> Ali_ix: Um.. Ok.
[09:10] <Ali_ix> shawarma: some one advised to use pinning
[09:11] <shawarma> Ali_ix: There's no need.
[09:11] <shawarma> Ali_ix: You using the server images?
[09:11] <Ali_ix> shawarma: no, desktop images on feisty
[09:12] <shawarma> Ali_ix: Ok. "apt-get remove linux-image-generic"
[09:12] <shawarma> Ali_ix: That should do it.
[09:13] <shawarma> Ali_ix: I'm curious why you're asking here, though?
[09:13] <Ali_ix> shawarma: isnt it nessecary for later?
[09:13] <Ali_ix> *necessary 
[09:14] <Ali_ix> shawarma: what is within linux-image-generic-* package? just linux headers and sources? :)
[09:14] <shawarma> Ali_ix: Well.. Yes, in the same sense as the kernel updates are necessary, but it's those you don't want?
[09:14] <shawarma> Ali_ix: linux-image-generic-* are the actual kernels.
[09:14] <shawarma> Ali_ix: The headers are in linux-headers-generic-*
[09:15] <shawarma> Ali_ix: You should *not* remove linux-image-generic-*.
[09:15] <shawarma> Ali_ix: Only linux-image-generic.
[09:15] <shawarma> (no suffix)
[09:15] <Ali_ix> oh, got it :d
[09:15] <Ali_ix> thanks shawarma :)
[09:16] <Ali_ix> shawarma: this is a virtual package to the latest apackage build, isnt it?
[09:17] <shawarma> Ali_ix: Yes. That's how we make sure people get kernel updates.
[09:17] <shawarma> Ali_ix: Well.. Kernel updates when there are ABI changes, anyway.
[09:17] <shawarma> Ali_ix: If you want to be completely sure nothing updates your kernel without asking, you should do:
[09:18] <shawarma> Ali_ix: "echo linux-image-generic-`uname -r` hold | sudo dpkg --set-selections"
[09:18] <shawarma> Ali_ix: Gotta run!
[09:18] <Ali_ix> :D some strange command :D
[09:18] <Ali_ix> shawarma: thanks very much 
[09:33] <Ali_ix> shawarma: thanks again, and bye ;)