YDL & router (#2 of 2)

[Beartooth]

	This is the reply to specific points which follows my previous 
post, prefacing it with the development they engendered.

---------- Forwarded message ----------
Date: Sun, 30 Mar 2003 14:20:03 -0700 (MST)
Subject: yellowdog-general digest, Vol 1 #738 - 12 msgs

   1. Re: yellowdog-general digest, Vol 1 #736 - 13 msgs (Jonathan Walton)
  11. Re: YDL & router -- progress, maybe (Ron McCall)
--__--__--

> Message: 1
> From: "Jonathan Walton" <jwalton@hotpop.com>

> >	Two problems, perhaps related. One: I'm pretty sure WEP was off 
> > when I did that -- and I'm sure it was late last night; but when I
> > went into Setup just now, I had to turn it off again, without having
> > touched it in the mean time.

> I had this problem the first few times with the Netgear MR314.  It
> turned out to be user-error (I kept forgetting to click "save).

	Do you mean "apply" on the configuration screen for the router? 

> > I will assume you're going to use a static IP address.  I have not
> > messed with DHCP so I can't help you with that.  Your ifcfg-eth1
> > file (in /etc/sysconfig/network-scripts) should look something like
> > this:

> I was actually using DHCP just fine.  I followed the wireless HOWTO on
> the ydl site to do so.  The notes I kept at that time and the relevant
> files are below.  I hope this helps.

> Jonathan

	I'm using the manual instead of the site now, just because I'm 
getting so much valuable help from this list that I don't want to spare 
the screen space from it for the site. Apart from that mysterious hint 
that I can't find again, the text is the same. (I had thought it was in 
the howto.)

>  created an /etc/sysconfig/network-scripts/ifcfg-eth1 for airport 
> (DHCP)

	Mine is there; so I just keep re-editing it. 

>   set up /etc/rc.modules to load it
>   [try /etc/sysconfig/network gateway = eth1]

	Here you lose me. Do you mean type the second line without "try" 
and hit enter -- in order to accomplish the first?? Or ....???

> changed /etc/sysconfig/network-scripts/ifcfg-eth0 to not try eth0 on 
> boot  [since DHCP without mods locks up]

	Haven't tried that yet; but I haven't rebooted since the latest 
development, adumbrated in my last previous post.

> my /etc/sysconfig/network-scripts/ifcfg-eth1 file reads:
>    NAME=localhost
>     DEVICE=eth1
>     IPADDR=
>     BOOTPROTO=dhcp
>     ONBOOT=yes
>     NETMASK=
>     GATEWAY=
>     ESSID="XXX"
>     KEY="YYY"

	Is putting KEY=in that the same as the "enc s:yyy" that I 
described in the other post? And similarly for ESSID?

> my /etc/rc.modules reads:
>     #!/bin/sh
>     /sbin/modprobe airport

	Where do you have to be to get that? And how? I can't seem to 
get into mine -- assuming it does exist by now ... If I do cd /etc from 
root home, then ls, the list goes from rc.local to rc.sysinit

> and my /etc/sysconfig/network reads:
>     NETWORKING=yes
>     HOSTNAME=localhost.localdomain
>     FORWARD_IPV4=no
>     DEFRAG_IPV4=no
>     GATEWAY=
>     GATEWAYDEV=eth1
>     NISDOMAIN=
>     IPX=no
>     IPXAUTOPRIMARY=off
>     IPXAUTOFRAME=off
>     IPXINTERNALNETNUM=
>     IPXINTERNALNODENUM=

	Mine differs in having 192.168.1.1 where you have a blank after 
GATEWAY=, and in having eth0 where you have eth1. Change those?
	[snip]
> SideNote 2: I strongly suggest WEP, hardware-filtering, and changing
>   your default password.  I'm glad my neightbor with DSL _doesn't_  
> ... [snip]

	How about the SSID and password on the router? And at one point 
in my afternoon's tinkering, I was getting errors because I tried 
following the man page to put in a MAC address: they said eth1 didn't 
support it!

--__--__--
Message: 11
From: Ron McCall <ronald.mccall@snet.net>
Subject: Re: YDL & router -- progress, maybe

> On Sun, Mar 30, 2003 at 10:06:01AM -0800, Beartooth wrote:
> > 	Oops! No, I have to do dhcp. I'll try all the rest anyway, 
> > except that I'll make BOOTPROTO=dhcp, and see what happens. 

> I would be interested to hear if it is just that simple.  I've seen
> talk about dhcpcd and some others but I forget now if that's only for
> dialup connections or what.

	Running a router with Verizon DSL pretty much requires it -- or 
maybe even without the router, afaik. So it's not just dialup. (Fwiw, 
Verizon does PPP0E.)

	(snip)

> The modprobe command is for loading kernel modules, like the airport
> driver.  It should already be loaded automatically due to an "alias
> eth1 airport" in your /etc/modules.conf file.  

	I see "alias eth0 sungem" in mine, buth nothing containing eth1; 
the rest all start with "sound".

> You shouldn't need to mess with this (you could verify via lsmod that
> your airport module is already loaded just to be sure though).

	The olist that gives has a size and a column saying "used by 0" 
-- and then blank -- after airport.

> The failure on eth1 may very well may be due to a DHCP problem.  Can
> you try static IP first and then worry about DHCP later?

> I think you can just pick a low numbered IP address like 192.168.1.2
> since the DHCP server in the router usually starts at 192.168.1.100
> and counts up, if I remember correctly.

	Does the second paragraph above explain the first? My 
understanding has been that dhcp was it.

> I'm not sure you want that ppp interface coming up.  You may want to
> set its ONBOOT parameter to NO (do you have an ifcfg-ppp1 file?).  I
> haven't messed around with PPP either.

	How do I tell? And I do recall that, where i was stuck with a 
flaky dialup, I never did manage to make YDL connect at all. That's 
quite possibly the largest single reason I want to ge tupgraded to 3.0 
-- OSX makes my teeth itch and my fingernails crawl.
-- 
Beartooth the Stubborn <karhunhammas (at) lserv.com>
double retiree, linux duffer, curmudgeon
RH 8.0, YDL 2.3, OSX 10.1.5; Pine 4.44, Pan 0.13.3; 
Privoxy 3.0.0; Phoenix 0.5, Opera 6.11, Galeon 1.2.5
Keep in mind that I have little idea what I am talking about.