1 |
I figured out what the problem was. |
2 |
I hadn't changed the interfaces file in shorewall to point to eth1 |
3 |
instead of ppp0 (the old adsl connection). Shorewall was blocking the |
4 |
connection. Once I corrected this, I was up and running :-) |
5 |
|
6 |
Thanks |
7 |
|
8 |
|
9 |
|
10 |
On 2005-10-29 20:26 +0000, jcranmer01@×××××××××.net wrote: |
11 |
> Here's where I get a little stuck. My internet programs are |
12 |
not |
13 |
> recognising this eth1 connection. What step do I need to |
14 |
perform in |
15 |
> order to get the internet connection working? |
16 |
|
17 |
A good starting point may be taking a look at the kernel IP |
18 |
routing |
19 |
table -- that's what "route" is for. You probably want to use |
20 |
its "-n" |
21 |
switch to disable host name lookups. |
22 |
|
23 |
You want a route with destination 0.0.0.0, genmask 0.0.0.0 |
24 |
(means CIDR |
25 |
network 0/0, or "default" upstream) and gateway somewhere in the |
26 |
range |
27 |
24.88.247.x (24.88.247/24), going through (iface) eth1. Without |
28 |
it, |
29 |
your system will not be able to talk to anything outside of your |
30 |
little corner of Road Runner's network. |
31 |
|
32 |
If you have such a route, then running traceroute (also with |
33 |
"-n") |
34 |
towards a known valid IP address should give you some clue as to |
35 |
where |
36 |
the problem is. You may also want to look at any iptables rule |
37 |
sets |
38 |
you may have; that's "iptables -L -n" (list, numerical). |
39 |
|
40 |
If you can connect to an IP address but not using a DNS name, |
41 |
that |
42 |
leaves just name resolution (/etc/resolv.conf |
43 |
and /etc/nsswitch.conf |
44 |
under "hosts:", as I recall). |