[02:16] <Guest4844> hi 
[14:58] <zeref> ok guys, here's one.  Setup ICS(internet connection sharing) on my one ubuntu box. connected to my other buntu box, and it works. connected to my debian box, not working. so i'm mising some software. does anybost know exactly what software it is??
[15:03] <tumbleweed> no, you aren't. The debian box is probably misconfigured
[15:10] <zeref> hmmm
[15:12] <tumbleweed> you have set it up to use dhcp?
[15:13] <zeref> on the deb box, i'm  using network-manger. so shouldn't it auto detect on eth0?
[15:13] <zeref> tumbleweed: yes
[15:15] <tumbleweed> yes
[15:15] <tumbleweed> so, did it get an IP? a default route? a nameserver?
[15:17] <zeref-lappy> nope.
[15:17] <zeref-lappy> did not have to set those for the other ubuntu box
[15:19] <tumbleweed> I'm trying to suggest how you go about debugging this
[15:20] <tumbleweed> did it receive a DHCP lease?
[15:20] <zeref-lappy> nope
[15:21] <tumbleweed> what's in /etc/network/interfaces ? and /var/lib/NetworkManager/NetworkManager.state
[15:23] <Kilos> afternoon all
[15:23] <zeref-lappy> in interfaces: just auto lo
[15:24] <zeref-lappy> the state file: networkingEnabled, Wireless enabled, WWANEnabled, all true
[15:25] <tumbleweed> zeref-lappy: that seems good, although you should have also had "iface lo inet loopback" in /etc/network/interfaces
[15:26] <zeref-lappy> yep i do have that :-)
[15:28] <tumbleweed> zeref-lappy: do you see entries from dhclient in /var/log/daemon.log ?
[15:31] <zeref-lappy> hmmm
[15:31] <tumbleweed> if you tail it while connecting, you should see interesting things :)
[15:32] <tumbleweed> anyway, I must run off
[15:32] <zeref-lappy> nope no dhclient entry
[17:31] <inetpro> good evening
[17:31] <Kilos> lo inetpro 
[17:33] <inetpro> Kilos: heh, how goes?
[17:33] <Kilos> so so en daar?
[17:34] <inetpro> hmm... so bietjie lyf seer maar verder ok
[17:35] <Kilos> lyf seer van wat inetpro ?
[17:35] <inetpro> Kilos: het Vrydag oggend saam met my bromponie so bietjie kennis gemaak met die teerpad
[17:35] <Kilos> eish
[17:36] <inetpro> maar niks ernstig nie, kon gelukkig opstaan en verder ry
[17:36] <Kilos> sjoe
[17:36] <inetpro> net die ego so bietjie aangetas
[17:36] <Kilos> lol
[17:37] <Kilos> bitjie skaam nê
[17:37] <Kilos> bietjie ook
[17:37] <inetpro> ai, die dinge gebeur te vinnig
[17:37] <Kilos> ja jy moet wakker wees hele tyd op twee wiele
[17:38] <inetpro> een oomblik nog lekker gery teen 60km om die draai by die duikweg uit Pretoria Noord uit
[17:38] <Kilos> was die pad nat?
[17:38] <inetpro> volgende oomblik was dit of ek op ys skaats
[17:38] <Kilos> of olie op die pad
[17:38] <inetpro> nee maar ek dink daar was 'n olie kol
[17:39] <inetpro> maar ek was onvoorbereid en het betaal daarvoor
[17:39] <Kilos> eish jy kan bly wees daar was nie karre of trokke wat verby gejaag het nie
[17:39] <inetpro> yep
[17:39] <inetpro> net karre agter wat onmiddelik gestop het 
[17:39] <Kilos> sjoe jy is baie gelukkig
[17:40] <inetpro> en drie mense uit verskillende karre wat my onmiddelik opgehelp het nog voor ek behoorlik kon opstaan
[17:40] <Kilos> sjoe dis gaaf
[17:41] <Kilos> meeste ry net verby deesdaie
[17:41] <Kilos> sjoe vergeet hoe om dit te spel
[17:41] <Kilos> het jy erg seer gekry
[17:43] <inetpro> net skrapies op de enkel en op die knieg
[17:44] <Kilos> sjoe
[17:44] <inetpro> en 'n skoenveter wat weggeskraap is
[17:44] <Kilos> jy moet versigtig ry man
[17:45] <inetpro> gelukkig my baadjie aangehad anders was ek ene roasties aan my arm
[17:45] <inetpro> ja, so leer 'n mens om nog meer respek te hê vir die ding
[17:46] <Kilos> o het jy n leer baadjie
[17:46] <Kilos> beste klere vir af val
[17:46] <inetpro> nie leer nie
[17:46] <Kilos> zeref-lappy, dit you win with the modem?
[17:47] <zeref-lappy> Yebo
[17:47] <Kilos> hoe lyk die baadjie
[17:47] <Kilos> what dit you need to do zeref-lappy ?
[17:47] <inetpro> sintetiese baadjie
[17:48] <inetpro> zeref-lappy: ehlo
[17:48] <Kilos> eks bly jy is ok inetpro 
[17:48] <Kilos> dank die groot baas nê
[17:49] <inetpro> Kilos: dankie, vir seker
[17:49] <zeref-lappy> had to install us-moden app
[17:49] <zeref-lappy> stop network-manager
[17:50] <zeref-lappy> restart, than bam, working
[17:51] <Kilos> wow on maverick the modem is normally seen straight off as long as you have usb-modeswitch installed so it doesnt see it as a storage device
[17:51] <Kilos> i think i got modem-manager as well
[17:52] <Kilos> but good to know its working
[17:52] <Kilos> poor old squirm still hasnt got his working i think
[17:53] <zeref-lappy> thing is that there are so many solutions, is usb-modem method is not working
[17:53] <zeref-lappy> *if
[17:53] <Kilos> yeah
[18:22] <Kilos> lo sdehaan 
[18:25] <Kilos> nuvolari, lewe jy nog?
[18:27] <Kilos> night guys sleep tight
[19:20] <tumbleweed> zeref-lappy: right, do you have dhclient installed?
[19:31] <zeref-lappy> wait, wait, before we continue. i initially wanted my debian box to be a dhcp server. so i've gone back to that
[19:32] <zeref-lappy> its setup up correctly if i connect a win box to debian
[19:32] <zeref-lappy> now the conectins for ubuntu box
[19:33] <tumbleweed> if it is the dhcp server, shouldn't it also be the gateway?
[19:33] <tumbleweed> (it's generally sensible to keep networks simple)
[19:33] <zeref-lappy> yeah
[19:34] <zeref-lappy> wlan0 is on 192.169.1.xx, the eth0 is on 192.168.0.xx
[19:34] <tumbleweed> where does the internet connectivity come from?
[19:35] <zeref-lappy> debian, managed by the interfaces file
[19:39] <zeref-lappy> when i tail messagaes file i get eth0 link not ready
[19:41] <tumbleweed> is the cable plugged in?
[19:41] <tumbleweed> does the cable work? :)
[19:41] <zeref-lappy> yep
[19:42] <tumbleweed> if it says the link down, then it's either the cable or the interface at one of the ends...
[19:43] <zeref-lappy> ummm, must be the buntu box, cos when i connect a windows box all is good.
[19:44] <zeref-lappy> i put the details in the interfaces file instead of network-manager, same thing
[19:45] <tumbleweed> let me just see if I understand
[19:45] <tumbleweed> you have an ADSL modem or something connected to eth0 of the debian box
[19:45] <zeref-lappy> *wlan0
[19:45] <tumbleweed> ok, it connects to the router by wifi
[19:46] <zeref-lappy> yebo
[19:46] <tumbleweed> and eth0 is a local LAN that this machine will be the gateway for?
[19:46] <zeref-lappy> yep
[19:46] <tumbleweed> but you don't want the LAN and wifi network to be bridged?
[19:47] <zeref-lappy> ummm, i read around and most sites said that bridging was not a good idea
[19:48] <tumbleweed> depends
[19:48] <tumbleweed> it's utulaly the simplest solution
[19:48] <tumbleweed> because you don't need another layer of NAT, another DHCP server, etc
[19:48] <tumbleweed> (assuming a small home network)
[19:48] <zeref-lappy> + for wlan0 i'm using ndiswrapper, and with niswrapper you can change the mode to master, needed for bridging
[19:48] <zeref-lappy> *can't
[19:48] <tumbleweed> ndiswrapper, urgh
[19:49] <zeref-lappy> :P
[19:49] <tumbleweed> hrm, can a wifi client not be bridged?
[19:49] <tumbleweed> master is for making the machine an AP
[19:51] <zeref-lappy> o0o0
[19:51] <superfly> surely you can just shut down dhcp on the wireless router, and then the server will hand out ip addresses there too?
[19:52] <superfly> you manually set the ip address of the router itself, so that you can route internet through its modem, but the rest of the network gets their addresses from the server
[19:53] <zeref-lappy> ummm, i'll read up on: http://wiki.debian.org/BridgeNetworkConnections
[19:53] <zeref-lappy> superfly: i dont have access to the router..
[19:54] <tumbleweed> superfly: I'm suggesting the other way around, having the router handle everything, but yeah, same thing
[19:54] <tumbleweed> zeref-lappy: aah, someone else's router?
[19:54] <tumbleweed> in that case maybe you don't want to bridge
[19:54] <superfly> tumbleweed: yeah, I'd do something like that
[19:55] <zeref-lappy> tumbleweed: yeah, res..
[19:55] <tumbleweed> zeref-lappy: aah, yes you don't want to bridge then
[19:55] <tumbleweed> you want your own network
[19:55] <tumbleweed> so, what's plugged into eth0? a switch?
[19:56] <zeref-lappy> just a eth cable
[19:56] <tumbleweed> running to another machine?
[19:57] <tumbleweed> is it on?
[19:57] <zeref-lappy> yes
[19:57] <tumbleweed> do they show link lights?
[19:57] <Tonberry> any of the two still 100mbit?
[19:57] <tumbleweed> maybe you need a crossover cable (if both of them are oldish)
[19:57] <Tonberry> yes
[19:57] <tumbleweed> yeah, gigabit interfaces have auto-crossover, many 100mbit interfaces don't
[19:57] <zeref-lappy> no, link lights only go on with windows box connected
[19:58] <tumbleweed> debian<->windows = link,  debian<->ubuntu = no link?
[19:58] <tumbleweed> is the windows box newer?
[19:58] <zeref-lappy> yeah
[19:58] <tumbleweed> right, you need a crossover cable :)
[19:58] <zeref-lappy> win dox is new
[19:58] <Tonberry> or at switch
[19:58] <Tonberry> a*
[19:59] <tumbleweed> yeah
[19:59] <zeref-lappy> :-)
[20:01] <zeref-lappy> thanks guys