Setting up internet

[trixee]

I've just installed Fedora on my computer and am having difficulty connecting to the internet.

As far as I know, I've managed to install the ethernet driver (although it says FAIL during bootup) but it still doesn't connect to any websites.

It gets as far as trying to resolve the web address, but always times out on it. Any ideas would be greatly appreciated.

[kal]

you dont have a working network if it says fail on start up.
Any more info like log messages?

[trixee]

But the network configuration tool shows the ethernet card as configured and active, so I don't get why it shows fail on boot.

The log messages don't really shed any light. Is there anything specific I should look for?

[kal]

ifconfig -a if you havent already tried that.
output may give hints, to start from.

[mbottrell]

If you're using Fedora...

Use the adsl-setup command to get it going...

It can't be simpler. It 'binds' the ppp0 interface to one of your NICs (eg: eth0 or eth1) that is connected to the ADSL modem. This ppp0 interface will pickup your static IP.

Also ensure your ADSL router is in bridge mode....

It should go as such:

Phone <--> ADSL Modem <--> Lin Box

Cheers,

Matt.

[trixee]

Originally posted by mbottrell
If you're using Fedora...

Use the adsl-setup command to get it going...

I saw that when I was looking through the scripts, and it looked good! But I had trouble running it. Could you please tell me exactly what to do? (yeah, I sound stupid, I know *g*)


Also ensure your ADSL router is in bridge mode....

Okay, this may be a little bit tricky, but I'll get out the manual.

Thanks!

[mbottrell]

Originally posted by trixee
I saw that when I was looking through the scripts, and it looked good! But I had trouble running it. Could you please tell me exactly what to do? (yeah, I sound stupid, I know *g*)


Take a read here: https://www.redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-network-config-xdsl.html

That may be the easiest method for you. :)

Cheers,

Matt.

[kal]

Perhaps this is a silly question, but why would you want to run the modem in bridged mode? Why not just use dhcp on the lin box and use the modem in router mode? Seems to me like this would not only be simpler but far more flexible for future additions (another pc access to the net). Just curious

[MrShadow]

Main reason (for me) to run modem in bridge (or half-bridge) is so I can run my own web server. My modem wasn't forwarding ports in router mode, so it has to be in hlaf-bridge. But you're right, if you're not going to be running your own servers, leave it as-is.

[psykles]

Linux problems are pretty much useless without posting any logs/error msg's.

If you aren't using your modem's dhcp, the 2 following commands should get you connected, provided you have your ethernet card correctly set up:

# ifconfig eth0 192.168.x.x up netmask 255.255.255.0
Add whatever IP you assigned to your computer in the modem config.


# route add default gw 192.168.xx
This will be your router's IP.
Default for a billion 743GE should be 192.168.1.254
For a netcomm, I can't remember !

As for trying to access webpages, after you have the connection set up, you need to edit /etc/resolv.conf and add:

nameserver 202.154.83.53
nameserver 202.154.92.35

Save and try some sites.

Update: sorry, for the nameserver(s) use whtever the DNS servers are for your state or however this stuff goes :)

[mbottrell]

Originally posted by kal
Perhaps this is a silly question, but why would you want to run the modem in bridged mode? Why not just use dhcp on the lin box and use the modem in router mode? Seems to me like this would not only be simpler but far more flexible for future additions (another pc access to the net). Just curious

You run the modem in bridge mode for a few reasons:
[list=1]
It becomes a dumb router.
Avoids 'holes' in the security of the router... as no IP address is assigned to it. :) Though non-IP based attacks are still possible... but it does greatly reduce it.
Bridge modem does turn it into a 'router' mode... it just passes packets.
Yes, you do setup DHCP, SQUID, Apache and DNS on the Linux box... also more flexability for firewalling.
I run two public Internet ranges.... using a Lin firewall allows me to do this with a 4-port NIC card. :) (1 to ADSL, 1 each for the two DMZ's, 1 for my LAN. :) )
Cause you can. :p
[/list=1]

Hope that sheds a little light onto it.

Cheers,

Matt.

[kal]

I guess I come from a different angle on that then. More net admin than sys admin :)
Just a clarification though, unless you have a far different modem than what I'm used to using, bridged mode is not router mode, it isnt a router in any sense at all. It acts like the name suggests as a bridge between PC(FW in this case) and the DSL link(connecting dissimilar physical networks). The Virtual circuit is between the PC's ip stack and the remote end.
Actually my point was in reference to ease of setup rather than technical.
You cant beat the simplicity of not setting any software up on a pc and just hooking up straight to a router. Having worked at several ISP's, I speak from painful experience. KISS works!! :D

[mbottrell]

Kal,

Yes, in that aspect it is a bridge rather than a router. :)

hehehe... agree KISS for the majority works best....

Personally I've got two /28 ranges hanging off as well as our /32 and a private /24 hanging off the firewall. :)

Yeah, I personally like the idea of a locked down box in my control ratehr than a vendors implementation I don't have much control of. :)

I have also found that the PPPoE client running under Linux seems a lot more resiliant than that of the ADSL router I own.

I guess... whatever works. :D

Cheers,

Matt.

[trixee]

I got it working guys, thanks for all your help! I implemented most of the recommendations, but I think the clincher was here:

Originally posted by psykles
# route add default gw 192.168.xx

I did this and nothing much happened, but then I tried it again with the -net switch and it worked!

Thanks again, everyone!

And please, continue with the discussion on bridging, it's very interesting :)

[kal]

Good to hear you're up and going.
I think as a beginner networking concepts can be a bit arcane.
A good site for future reference: http://www.linuxhomenetworking.com/index.htm#Linux
has basic and advanced topics.
may come in handy.
I should really explain that bridge in this sense is used rather loosely. Technically a bridge will filter traffic between ports depending on the destination hardware address (think switch). In *bridged* mode a dsl modem is in truth nothing more than an adapter for the local pc's ip stack. The older definition of a bridge excludes its presence in a point to point network like home dsl connections.
However the term bridge is now used loosely not only by forum posters :) but also by many of the home network device vendors. I personally feel this is detrimental to consumer choice as using the term interchangably disguises the products true capabilities. _takes deep breath_
Now that my rant is over, enjoy your home network :D

[Ashtrax]

Would it help if i wrote a HOWTO document? I have got it working and customized very well on RedHat distros. I'll cover everything from setting up the modem to establishing a link, to getting over the timeout issue, and then onto setting up a firewall.

If anyone is interested in this drop me an email at josh@thechatplace.net

If anyone has already written one, forgive me for posting this.

Josh.

[mbottrell]

Yup... go for it. :)

Cheers,

Matt.

PS: I would if I ever had the time.... I'm still doing the Samba PDC and Exchange Server HOWTO! :(

[trixee]

Originally posted by Ashtrax
Would it help if i wrote a HOWTO document?
Josh.

That would be fantastic!

I'm still having problems, I have to admit, but I can manage to do a hacked up fix. I log in as root and add my default gateway via route add etc, and then I log out and log back in with my regular login. It works, but it's annoying having to do it all the time. I just don't have the time or patience to fix it properly at the moment. Maybe in July.

[kal]

to add the default route every time you boot, you can either add an RC script. Or more conveniently add the follwing in /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=MYHOSTNAME
GATEWAY=192.168.1.1

I use very few GUI apps on *nix but I recall there being an app called netcfg on some linux distributions, that will provide a nice interface to alter this file and those under /etc/sysconfig/network-scripts/ . That is NIC specific files.

[trixee]

Originally posted by kal
Or more conveniently add the follwing in /etc/sysconfig/network

NETWORKING=yes
HOSTNAME=MYHOSTNAME
GATEWAY=192.168.1.1


Hey, thanks for this, I honestly can't remember what I've tried and what I haven't. Hopefully it will work! However, the default gateway is 192.168.1.254 - or that's what I use to make mine work, anyway. Is there any reason for the 192.168.1.1 you have there? I thought that was for the loopback device?

[kal]

nope no reason. it was just an example.
if your default gateway is 192.168.1.254 use that address.
Hostname was also an example :)
loopback is normally 127.0.0.1 . Can be other ip addresses, but I wont get into that.