Hi Everybody,

I need some light here with my network configs. I am running FC12 86_64x version with home adsl broadband.

The rp-pppoe was already installed. DSL config with my login and password has the setup done in GUI mode.
http://hubpages.com/hub/Configure-DSL-in-Fedora-Linux

If I go on GUI --> system --> network, it shows:

inactive ppp0 AOL xDSL
active eth0 eth0 Ethernet

I have done everything possible so far and spent 2 days on it, but still couldn't browser on internet.

Here are some details about my ethernet card and some other trials running as root

# ifconfig -a
eth0 Link encap:Ethernet Endereço de HW 00:19:66:8C:8E:8A
inet end.: 192.168.1.2 Bcast:192.168.1.255 Masc:255.255.255.0
endereço inet6: fe80::219:66ff:fe8c:8e8a/64 Escopo:Link
UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
RX packets:126 errors:0 dropped:0 overruns:0 frame:0
TX packets:190 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:1000
RX bytes:10353 (10.1 KiB) TX bytes:17987 (17.5 KiB)
IRQ:27 Endereço de E/S:0xe000

lo Link encap:Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
endereço inet6: ::1/128 Escopo:Máquina
UP LOOPBACKRUNNING MTU:16436 Métrica:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:0
RX bytes:480 (480.0 b) TX bytes:480 (480.0 b)

# lspci -vvnn > output.file
...
00:07.0 Bridge [0680]: nVidia Corporation MCP61 Ethernet [10de:03ef] (rev a2)
Subsystem: ASRock Incorporation 939NF6G-VSTA Board [1849:03ef]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 27
Region 0: Memory at df7fd000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at d480 [size=8]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable+ DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit+
Address: 00000000fee0100c Data: 4181
Masking: 000000fe Pending: 00000000
Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: forcedeth
Kernel modules: forcedeth

# /sbin/ifup eth0

Determining IP information for eth0...dhclient(1004) is already running - exiting.

This version of ISC DHCP is based on the release available
on ftp.isc.org. Features have been added and other changes
have been made to the base software release in order to make
it work better with this distribution.

Please report for this software via the Red Hat Bugzilla site:
http://bugzilla.redhat.com

exiting.
failed.

# dhcpcd -n eth0
bash: dhcpcd: command not found

# modprobe forcedeth
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.

# dmesg | grep eth0
forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:66:8c:8e:8a
eth0: no IPv6 routers present

All comments and suggestions are highly appreciated.

It would help to know what hardware you are using for your DSL modem and maybe which ISP you are using.

1 members found this post helpful.

Thanks for the feedback...

I have a DSL modem Thomson ST510v6
http://www.thomsonbroadbandpartner.c...ail.php?id=102

ISP name: GLOBO.COM

Thanks for the extra information

Looking at the User Guide it seems the ST510v6 can make its own internet connection and act as a NATing router with firewall etc. That would be a much more secure way to use it that to have it in bridged mode in which case it is transparent in network terms and your computer is exposed on the Internet. Unless you have any special reasons for wanting that I strongly recommend configuring the ST510v6 as a router.

How do you feel about that?

1 members found this post helpful.

It sounds great and really nice.

So, could you please point how to get it acting as a NATing router?

I did the FC12 installation, and it didn't detected the modem automatically. Maybe I should reinstall the system again, or missed something!?

Thanks again!

Well ... it's not the most comprehensible User Guide (linked from the page you linked) but it's all in there somewhere.

There aren't many ADSL modem/router chipsets around so the functional differences between such devices are in the firmware -- and this one seems less dumbed down than most allowing most of the functionality to be accessed. Nice.

Is the ST510 your only way of connecting to the Internet? We have to proceed with caution if it is.

In essence the procedure is

1. Wire your ethernet port to the router.
2. Configure your ethernet port to be in the same address range as the router. "1.2.1 Access via the Web Interface" shows the ST510v6 defaults to LAN address 192.168.1.254 so configure your computer to, say, 192.168.1.200 with a netmask of 255.255.255.0 and default gateway of 192.168.1.254.
3. Use a web browser to open http://192.168.1.254. If this doesn't work try a "hardware reset" as described in "5.3 Reset to Factory Defaults".
4. Open SpeedTouch->Configuration, configure and WIN!

Unfortunately the devil is in the details of the last step. Even knowing the essentials of what has to be configured I can't follow the User Guide here! Maybe you just go through with the wizard.

You will need information from GLOBO.COM to configure the broadband connection from the ST510 to GLOBO.COM. Searching for "adsl "GLOBO.COM" ST510" found nothing useful so I guess either GLOBO.COM are a very small ISP or they did not supply the ST510. Searching for "adsl "GLOBO.COM" australia" didn't help either. Which country are you in?

Do you have any setup instructions from GLOBO.COM? Should be something like PPPoE or PPPoA, PVC (VPI/VCI), username and password.

Great!!! I got it working - the solution was simply to run on console the command pppoe-setup and it worked. Before I was trying pppoe and pppoeconf, adsl-setup, but for fedora the right choice is the pppoe-setup. Quite funny that the other versions of pppoe didn't work for FC12.

Great!!! I got it working - the solution was simply to run on console the command pppoe-setup and it worked. Before I was trying pppoe and pppoeconf, adsl-setup, but for fedora the right choice is the pppoe-setup. Quite funny that the other versions of pppoe didn't work for FC12.

Glad you found a solution

Threads can be marked SOLVED using the Thread Tools menu.