[lug] Qwest ADSL
blug-receive at mtbwr.net
Mon Feb 19 10:41:22 MST 2001
> > 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
the show interface however shows me
and I think the eth0 is the problem.
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
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
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,
> > I don't know, if that helps much. I went through a printed (by USWEST)
> > brochure (8 1/2 x 11") but this contained partial information and I had to
> > figure out some stuff myself.
> > But I have static IP's set up later on, so my current setup may not match
> > yours.
> > I think dhcp may mess it up. I have it in bridging mode.
> > I have a second DSL line with 675 which I can use for playing.
> > How are you accessing the 675? Over serial cable, I assume/hope?
>I have gone though the set up of the 675. I have interfaced with minicom on
>the linux box and hyperterminal on a windose box - both work good. Just to
>make sure that the equipment was working, I hooked it up to a Windose box
>and it worked great. Sometimes it is not worth fighting the establishment.
> > It defaults to 10.0.0.1 but this is not what you want and if your network
> > card is not set up to 10.0.0.?, then you can't talk to the router over the
> > network, you'll need to use the serial cable to set it up.
> > Mine wants to know: who-has 10.0.0.153 tell 10.0.0.1.
> > So, if you firewall interface to the router is 10.0.0.1 then you have a
> > conflict with the routers default setting right there.
> > Can you talk to the router at all, like the show command?
>Yes, though minicom or hyperterminal on the serial cable, but not through
>the lan cable. I have tried using a static IP address on eth1, which is the
>NIC connecting to the 675, of 10.0.0.2 and a netmask of 255.255.255.0 and
>network of 10.0.0.0 but the routing table was screwed up. I could ping
>10.0.0.2 but pings were denied to 10.0.0.1. I then tried DHCP on eth1 which
>did give a "connect on 10.0.0.2". I could ping 10.0.0.2 but pings still
>denied on 10.0.0.1 - the 675. That is when I did a tcpdump and found all of
>the "who-has 10.0.0.x,s tell 10.0.0.1. Seems that the 675 is not setup
>correctly on the lan side or I am missing something in the dhcpcd-eth1.info
>file? On my machine this file is located in the /etc/dhcpc/ directory and
>contains the following info:
>Something in my memory seems to tell me that your reference document above
>has something about domain is Qwest.net - One of the blank spaces in my
>file. I'll try inserting qwest.net in the "domain=" and give it a try.
>If anyone is using DHCP to connect to DSL on the 675, would you check your
>dhcpcd-ethX.info file and compare it to mine - especially the blank spots
>above - and let me know the file content?
>thanks for the thought provoking info,
>Web Page: http://lug.boulder.co.us
>Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
More information about the LUG