**** BEGIN LOGGING AT Sat Feb 19 23:59:56 2005
Feb 20 04:24:25 <Guest1305> hey
Feb 20 04:24:32 <Gorx> hey
Feb 20 04:24:36 <Gorx> gotta prob
Feb 20 04:41:20 <caplink811-away> whar a problem?
Feb 20 04:41:27 <caplink811-away> s/whar/what
Feb 20 04:43:14 <caplink811-away> Gorx: ping
Feb 20 07:23:38 <caplink811-away> ok, so what's the problem, and irc isn't my familar ;-)
Feb 20 07:24:56 <JWynen> just put uNSLUng 3.17beta on my NSLU last night, can ping ipkg.nslu2-linux.org, but get an error on ipkg update
Feb 20 07:25:33 <caplink811-away> so do you fill in the dns and gateway in the web-interface?
Feb 20 07:26:34 <caplink811-away> administration-LAN page
Feb 20 07:26:58 <JWynen> i did.  Question, it is behind a wrt54g router, is the gateway the 192.168 gateway address or the external gateway?
Feb 20 07:27:32 <caplink811-away> nope, it's your local gateway, the router adress
Feb 20 07:27:47 <caplink811-away> and the router get manage to find a way to the target
Feb 20 07:28:00 <JWynen> thats what I did.  here is the error
Feb 20 07:28:29 <caplink811-away> and your netmask is 255.255.255.0?
Feb 20 07:28:44 <JWynen> it is 255.255.255.0
Feb 20 07:29:10 <caplink811-away> do you have a firewall on your router?
Feb 20 07:29:47 <JWynen> if i do -verbose_wget the error mes is Resolving %22192,.168.1.1%22 ... failed.  Host not found
Feb 20 07:29:52 <JWynen> i do have a firewall
Feb 20 07:31:27 <caplink811-away> obscour, ipkg.nslu2-linux.org have ip 66.35.250.210
Feb 20 07:32:00 <caplink811-away> aeh, do you ping from nslu2 or from your pc?
Feb 20 07:32:47 <JWynen> i telnet into the nslu, and then ping from there
Feb 20 07:33:32 <JWynen> do the %22 at the beginning and end indicate something?  which config file does the gateway go into do you know?
Feb 20 07:35:47 <caplink811-away> ipkg don't know everything about ip adresses, only names, and so i think your name resolution is bad
Feb 20 07:37:20 <JWynen> PING vhost.sourceforge.net (66.35.250.210): 56 data bytes
Feb 20 07:37:52 <caplink811-away> and ping ipkg.nslu2-linux.org give the same result?
Feb 20 07:38:50 <JWynen> thats what I get after the ping ipkg.nslu2-linux.org.   so dns seems to be working.  Do you think the wrt54 firewall is the problem?
Feb 20 07:39:40 <caplink811-away> can you telnet from nslu2 to a known www server something like telnet www.arcor.de 80
Feb 20 07:43:03 <JWynen> telnet returns no such file or directory.  is it /bin/telnet or somewhere else?
Feb 20 07:43:53 <caplink811-away> oh, sorry it's from inetutils, so you can nothing install, you can't have telnet :-(
Feb 20 07:44:16 <JWynen> i can ping www.arcor.de anyway
Feb 20 07:45:45 <caplink811-away> so your name resolution seems to be ok... must think on it..
Feb 20 07:46:13 <JWynen> i appreciate the help.  I've only dabbled with linux.
Feb 20 07:52:25 <caplink811-away> hm, your network adress are 192.168.1.x?
Feb 20 07:52:32 <caplink811-away> s/adress/adresses
Feb 20 07:52:44 <JWynen> yep
Feb 20 07:53:01 <caplink811-away> and your router is 192.168.1.1?
Feb 20 07:53:13 <JWynen> i suppose i could put the slug in the DMZ and see if that changes anything.  yep router is 192.168.1.1
Feb 20 07:54:36 <caplink811-away> can you check the /etc/sysconfig/network file?
Feb 20 07:54:56 <caplink811-away> GATEWAY should point to your router
Feb 20 07:55:16 <JWynen> networking=yes
Feb 20 07:55:21 <JWynen> hostname=nas1
Feb 20 07:55:26 <JWynen> domainname=
Feb 20 07:55:35 <JWynen> gateway=192.168.1.1
Feb 20 07:55:44 <JWynen> gatewaydev=ixp0
Feb 20 07:55:45 <caplink811-away> equals to mine
Feb 20 07:57:33 <caplink811-away> and /sbin/route gives something like that
Feb 20 07:57:47 <caplink811-away> default         192.168.10.100  0.0.0.0         UG    1      0        0 ixp0
Feb 20 07:58:02 <caplink811-away> where 10.100 is my gateway
Feb 20 07:59:05 <caplink811-away> does your firewall on the router forwards everything from every local ip adress, or can you differs which ip could use which port?
Feb 20 08:00:07 <JWynen> right now it should be passing everything from that ip.  but i will check
Feb 20 08:04:41 <JWynen> i explicitly forward all ports from 0 to 1024 to that ip, but no difference.  I think your initial guess is right tho,  it does seem to be a name resolution problem
Feb 20 08:05:31 <JWynen> verbose ipkg gives Resolving %22192.168.1.1%22... failed: Host not found.
Feb 20 08:06:27 <caplink811-away> i think %22 is something like ", but i've no idea why your router answer to the dns question with it's own ip
Feb 20 08:09:29 <JWynen> well, i will have to play with the router tonight.  gotta get the kids moving.  THanks for your help.  I appreciate it.
Feb 20 08:10:29 <caplink811-away> last idea, let your nslu2 use the dns from your provider, and not the dns from the router, may help, dunno
Feb 20 08:11:41 <JWynen> hmm thats interesting.  I set the first two DNS addresses to the ip from the provider, not the router.  maybe i should try the other way
Feb 20 08:14:34 <JWynen> does the nslu need to be restarted before changes to the web admin take effect?
Feb 20 08:17:17 <caplink811-away> i think so
Feb 20 08:22:57 <JWynen> ok, gotta roll.  Thanks again.
Feb 20 08:23:03 <caplink811-away> fine, bye
Feb 20 18:00:52 <JWynen> Hi everyone.  Anyone have time to help troubleshoot an ipkg problem?
**** ENDING LOGGING AT Sun Feb 20 23:59:56 2005