YDL & router -- progress, maybe

Beartooth yellowdog-general@lists.terrasoftsolutions.com
Sun Mar 30 10:57:01 2003


	Thanks to a late snowstorm (I don't drive on snow in the 
South.), I have an extra day.

Ron McCall <ronald.mccall@snet.net> wrote: 

> On Sat, Mar 29, 2003 at 12:24:18PM -0800, Beartooth wrote:
> >       I do not. GATEWAY= [blank] is all; right below it may be
> > another problem : GATEWAYDEV=ppp0


> I don't know the details of your setup so let me see if I can guess.  
> You are going to have the router handle the PPPoE connection and
> you're going to access the router via your AirPort interface, right?

	Right.

> If so, just set GATEWAY=192.168.1.1 (or whatever other IP address you
> chose for your router) and set GATEWAYDEV=eth1 (assuming that eth0 is
> your built-in Ethernet and eth1 is your AirPort).

	OK; did that.

> 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:

	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. 

> DEVICE=eth1
> BOOTPROTO=static
> BROADCAST=192.168.1.255
> IPADDR=192.168.1.2
> NETMASK=255.255.255.0
> NETWORK=192.168.1.0
> ONBOOT=yes

	I've gotten the impression sequence doesn't matter here , so
long as all the lines are what they should be. If that's wrong, somebody 
please set me straight.

> I think you can stick your wireless parameters in here too (I am not
> currently using my AirPort at the moment and I think I just stuck an
> iwconfig command at the end of /etc/rc.local back when I last used it;
> probably not the best way to do it).  Usually you just need ESSID (and
> KEY if you're using WEP), if I remember correctly.

	I'm by no means sure how much of this I understand. WEP is
supposedly off, on the advice of someone else on this list; I reported
on that. I added in ESSID= with the name on my router.

> >       Oho! Does that mean that, by 0.0.0.0 addresses, the web site
> > was talking *neither* of the gateway *nor* the Genmask addresses
> > (which I tried), but of the destination?? Never once framinit thunka
> > that!

> I believe so.

> >       Do I take it aright that you have the same router as I do, or
> > that it doesn't matter, or both? iow, should i edit my file
> > (whatever it is that "netstat -rn" displays), or otherwise change my
> > configuration to make that match? *And* that doing "pico
> > /etc/sysconfig/network" will let me make changes to match, and that
> > I should? that "netstat -rn" displays), or otherwise change my
> > configuration to make that match? *And* that doing "pico
> > /etc/sysconfig/network" will let me make changes to match, and that
> > I should?
 
> I have a non-wireless model (BEFSR11) that I used in conjunction with
> an AirPort Base Station at one time.  None of this setup should
> matter. It's just a matter of which interface is what and making sure
> the default route tells where to send stuff.

	I made the changes above. Then I tried /sbin/modprobe myessid
(though I don't think I understand what modprobe is or does);  it said
it couldn't locate it. Then I did /sbin/iwconfig eth1 essid myessid ; it
put me back to the prompt with no change. I did netstat -rn; no change.
Then /etc/rc.d/init.d/network stop, which shutdown eth0 and eth1; then
/etc/rc.d/init.d/network start.

	That set up network parameters and brought up lo and eth0 -- but 
"Determining IP information for eth1 ... Operation failed." (But ppp1 
succeeded,

	Am I just even more stupefacted than usual today?? One thing I
don't understand is when the actual entries in these files are supposed
to have one or another kind of quotes around them, and when not. Usage
on this list seems to vary -- or there's something else that I alone 
don't know ...
	
-- 
Beartooth the Stubborn <karhunhammas (at) lserv.com>
Double Retiree, Neo-Redneck, Linuxer's Apprentice
Alive & Well & Escaped to Appalachia At Last!