[lug] Qwest ADSL
Larry D. Ashton
ldashton at infowest.com
Mon Feb 19 18:49:04 MST 2001
Samartha,
To set the 675, were the commands something like this after starting your
communication program:
enable
password <password>
set nat entry delete all
set nat entry add 10.0.0.2
set mask 255.255.255.0
set interface eth0 address 10.0.0.1
write
reboot
I think the "set nat entry delete all" and the "set nat entry add 10.0.0.2"
will stop the ongoing "who has 10.0.0.2++ tell 10.0.0.1", but I haven't
tried it yet. Just trying to check out a few things with you first. While
I'm writing this, I'm trying a few things, too.
Is this similar to what your 675 shows for "show interface". What about the
vip0,1,2
cbos#show interface
IP Address Mask
eth0 10.0.0.1 255.255.255.0
vip0 0.0.0.0 255.255.255.0
vip1 0.0.0.0 255.255.255.0
vip2 0.0.0.0 255.255.255.0
wan0 Physical Port: Not Trained
Dest IP Address Mask
wan0-0 63.226.100.254 255.255.255.255
No, it is not connected at the moment.
About the ethernet setup on the linux box that connects to the 675 - sounds
like you are using a static IP - is that correct? ie 10.0.0.2.
Are you using two ethernet cards?
If yes, which one is connected to the 675?
Is it brought at boot time or do you manually configure it with "ifconfig"
and "route"?
Assuming you are using static IP:
What netmask are you using 255.255.255.0?
What broadcast 10.0.0.255?
Thanks again,
Larry
----- Original Message -----
From: "Deva Samartha" <blug-receive at mtbwr.net>
To: <lug at lug.boulder.co.us>
Sent: Monday, February 19, 2001 5:29 PM
Subject: Re: [lug] Qwest ADSL
> Larry,
> yes, it works, the IP number change on the 675 eth0 was the fix for me.
> What bothers me a little is the ongoing "who has 10.0.0.2++ tell
10.0.0.1".
> I have not figured yet, how to stop it.
> Also, I am not going to use dhcp, that's unessential - there is only going
> to be the firewall after the router and that can be static IP.
>
> I hope it works for you too.
>
> Samartha
>
> At 05:13 PM 2/19/01 -0700, you wrote:
> >Hi,
> >
> >I had to do the work thing today, so wasn't able to get back to you
> >immediately. I take it from reading your posting, that you have it up
and
> >running, or is that a premature assumption? Which steps made the big
> >difference? I'll be here the rest of the evening fiddling with my set up
> >and trying some of the suggestions you and others have made. Let me know
> >how it is going. If I have any success, I'll post it.
> >thanks,
> >Larry
> >
> >
> >Deva Samartha wrote:
> >
> > > Hi Larry,
> > >
> > >
> > >
> > > > > http://my.qwest.net/nav4/help/faqs/faqs_top10.html#5
> > > > >
> > > >Yes, I looked at this page and also read the Qwest DSL Instalation
> >Reference
> > > >Guide for Windose
> > >
> > > Actually, looking at it, hat page is not great - he is putting MAC
> > > addresses somewhere in /etc files, uses static IP's and dhcp. (maybe
that
> > > is dynamically set)
> > >
> > > My working setup with fixed IP's is definitely different from yours
and my
> > > play setup. With the play setup, I am exactly where you are.
> > >
> > > I think I know where the problem is but don't know a solution at this
> >point
> > > except that this setup (dynamic IP from USwest) worked before only no
> >notes
> > > were made by the person who did it and the stuff is forgotten ( but he
> > > said, he changed the IP number).
> > >
> > > From the router, I can ping the internet (name server IP), so the
router
> > > works fine.
> > >
> > > the show interface however shows me
> > >
> > > eth0 63.227.12.120
> > > wan0-0 63.227.9.254
> > >
> > > and I think the eth0 is the problem.
> > >
> > > It goes
> > >
> > > USwest-GW
> > > (63.227.9.254)<-->[675]-eth0(63.227.12.120)<-@@@->(10.0.0.2)eth0-Linux
> > >
> > > The eth0 on the 675 does not match the eth0 network on the Linux and
this
> > > link needs to be done my NAT. There is a default nat pool 0 which
handles
> > > the 10.0.0.0 area by default, so one does not need to set up a nat
> > > configuration for this case. If you need different IP numbers on your
> > > network, I would think that you can arrange that by adding a NAT pool
> >there.
> > >
> > > Ok, what I did on the router:
> > >
> > > set interface eth0 address 10.0.0.1
> > > write
> > >
> > > the show dhcp server leased
> > > shows me, that indeed, my eth0 on the Linux has signed out the IP
> >10.0.0.2,
> > > I can verify the MAC address.
> > >
> > > and the show nat
> > > shows - oh surprise - there is nat happening,
> > >
> > > so, let's try to ping a name from the Linux - WORKS!!!
> > > Internet broser - WORKS!
> > >
> > > also, make sure you do
> > > set web disable
> > > set telnet disable
> > > write
> > >
> > > to prevent telnet and web access to the router from the internet.
> > >
> > > and set passwords for user and root - assuming, you did this already
> > > anyway, but I found myself having the ports open on the router and
after a
> > > reset, the router does not have any passwords (I think).
> > >
> > > I don't think your /etc/dhcp is an issue at this point. I think this
> > > information is set dynamically by the dhcp server/clients and I would
not
> > > mess with that.
> > >
> > > Hope it helps,
> > >
> > > Samartha
> >
> >
> >_______________________________________________
> >Web Page: http://lug.boulder.co.us
> >Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>
> _______________________________________________
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>
More information about the LUG
mailing list