Re: Switch from Cable Modem to FIOS

Stan Koper adjusted his/her tinfoil beanie to post:

> I've had a home network for a number of years, a PII 450 mhz with
SuSE
> (now 9.3) connected to a cable modem, and connnecting five or six
> Windows computers (2000 and XP) to the internet.
>
> I'm switching over to Verizon fiber optic, which uses PPPoE instead
of
> DHCP. I followed some instructions elsewhere to set up PPPoE, and I

> can
> get onto the internet from the SuSE box. ifconfig shows me the
> following:
>
> dsl0 IP # from Verizon
> eth0 No IP # at the moment, had been running dhcpcd for cable modem> eth1 Class C IP #192.168.xxx.1, running dhcp
> lo 127.0.0.1
>
> eth0 had been set to run dhcpcd automatically. I set it to a fixed> number, then wiped the fixed number and set it back to dhcp, per
some
> instructions I've seen on the net.
>
> dsl0 is set to use the card that is at eth0. But none of the
> computers on my lan are able to get out to the internet.
>
> My question is, if dsl0 is using the card at eth0, should I even be> seeing an eth0 entry from ifconfig?
>
> Thanks
>
> Stan Koper

Hi Stan,

Is dsl0 in the firewall as an external interface?

Also have you got masq and nat enabled on it?

HTH
--
Mark
Novell Support Forums SysOp
Twixt hill and high water
N. Wales, UK.
Skype <my nick> text only please

baskitcaise wrote:
> Stan Koper adjusted his/her tinfoil beanie to post:
>
>
>>I've had a home network for a number of years, a PII 450 mhz with
SuSE
>>(now 9.3) connected to a cable modem, and connnecting five or six
>>Windows computers (2000 and XP) to the internet.
>>
>>I'm switching over to Verizon fiber optic, which uses PPPoE instead
of
>>DHCP. I followed some instructions elsewhere to set up PPPoE, and I

>>can
>>get onto the internet from the SuSE box. ifconfig shows me the
>>following:
>>
>>dsl0 IP # from Verizon
>>eth0 No IP # at the moment, had been running dhcpcd for cable modem>>eth1 Class C IP #192.168.xxx.1, running dhcp
>>lo 127.0.0.1
>>
>>eth0 had been set to run dhcpcd automatically. I set it to a fixed>>number, then wiped the fixed number and set it back to dhcp, per
some
>>instructions I've seen on the net.
>>
>>dsl0 is set to use the card that is at eth0. But none of the
>>computers on my lan are able to get out to the internet.
>>
>>My question is, if dsl0 is using the card at eth0, should I even be>>seeing an eth0 entry from ifconfig?
>>
>>Thanks
>>
>>Stan Koper
>
>
> Hi Stan,
>
> Is dsl0 in the firewall as an external interface?
>
> Also have you got masq and nat enabled on it?
>
> HTH
Yes, dsl0 is on the firewall as an external interface. And ip
masquerade and nat are enabled.

I think if I just had a dsl modem and one other nic card, for the LAN,

this would all be simple. But since I have two ethernet nics, and I'm

using one to do pppoe, I'm just not sure what I should be looking at
here.

Thanks,

Stan

Stan Koper adjusted his/her tinfoil beanie to post:


> Yes, dsl0 is on the firewall as an external interface. And ip
> masquerade and nat are enabled.
>
> I think if I just had a dsl modem and one other nic card, for the
LAN,
> this would all be simple. But since I have two ethernet nics, and
I'm
> using one to do pppoe, I'm just not sure what I should be looking at

> here.
>
> Thanks,
>
> Stan

Must admit I am working blind on this here as I have never configuredeither cable or fibre but what is the output of the route command on
the box?


--
Mark
Novell Support Forums SysOp
Twixt hill and high water
N. Wales, UK.
Skype <my nick> text only please

baskitcaise wrote:
> Stan Koper adjusted his/her tinfoil beanie to post:
>
>
>
>>Yes, dsl0 is on the firewall as an external interface. And ip
>>masquerade and nat are enabled.
>>
>>I think if I just had a dsl modem and one other nic card, for the
LAN,
>>this would all be simple. But since I have two ethernet nics, and
I'm
>>using one to do pppoe, I'm just not sure what I should be looking at

>>here.
>>
>>Thanks,
>>
>>Stan
>
>
> Must admit I am working blind on this here as I have never
configured
> either cable or fibre but what is the output of the route command on

> the box?
>
Route looks like this:

Destination Gateway Genmask Flag IFac
10.9.221.1 0.0.0.0 255.255.255.255 UH dsl0
192.168.10.0 0.0.0.0 255.255.255.0 U eth1
169.254.0.0 0.0.0.0 255.255.0.0 U eth1
127.0.0.0 0.0.0.0 255.0.0.0 U lo
0.0.0.0 10.9.221.1 0.0.0.0 UG dsl0

The first destination listed appears to be a "modem" at Verizon's end.

I'm not sure about the 169#, it appears that eth0 tries to get it when
I
first boot up. If I don't use route-n, it's described as
"link-local".

So although ifconfig will show dsl0 (with an IP), eth0 (no IP), eth1 (with the fixed IP (192.168.10.1), and lo with 127.0.0.1, route does
not
show eth0 at all.

But I have good news. In the limited time available to me this
morning,
before the house stirs and people turn on their computers and want to

know "why can't I get on the internet" (because I'm testing), I was
able
to both attach to the internet via the SuSE box, and get on from the
LAN
through it. I also have my directories back, which is the best news (where I store all my junk).

However, unlike when the D-Link router is in operation, in order for
the
computers on the LAN to get on the internet, I have to hard-code the

DNS numbers from Verizon (in the TCP/IP setup, these are all windows
XP
computers). With the D-Link, I can just check get DNS automatically
(or
whatever it says).

So I am on the internet, with my LAN behind SuSEfirewall2.

I do have some unanswered questions, such as (1) how to set up SuSE so

that it will pass Verizon's DNS numbers on to the computers on the LAN

automatically, and (2) how the heck do you do an FTP install of SuSE with a PPPoE connection to the internet?

Thanks for your interest.

Stan
>