Routing Debian 5
The Doctor
I chacked the network interface files and yes the gateway
is correct.
I cannot get the Debian Box to passed the Gateway.
What do I need to fix?
--
Member - Liberal International This is doc...@nl2k.ab.ca
Ici doc...@nl2k.ab.ca God, Queen and country! Beware Anti-Christ rising!
Never Satan President Republic!
Point to http://tv.cityonahillproductions.com/
s. keeling
> Step one accomplished Debian on one machine.
>
> I chacked the network interface files and yes the gateway
> is correct.
>
> I cannot get the Debian Box to passed the Gateway.
>
> What do I need to fix?
http://www.catb.org/~esr/faqs/smart-questions.html
What hardware? Is your connection Ethernet or WiFi? Static or
dynamic IP? What's the model name of your interface card? What does
"/sbin/ifconfig" say?
Can you find any mention of software failures in /var/log/messages or
syslog?
Try this in X:
xman -notopbox -bothshown &
Point and click interface to the manpages (documentation).
--
Any technology distinguishable from magic is insufficiently advanced.
(*) http://www.xs4all.nl/~js/gnksa/ Linux Counter #80292
- - http://www.faqs.org/rfcs/rfc1855.html Please, don't Cc: me.
Balwinder S Dheeman
> Step one accomplished Debian on one machine.
>
> I chacked the network interface files and yes the gateway
> is correct.
>
> I cannot get the Debian Box to passed the Gateway.
>
> What do I need to fix?
Please provide more information.
Can you from your debian machine, ping:
1) 127.0.0.1
2) ip.add.re.ss of your debian machine
3) ip.add.re.ss of your gateway?
--
Dr Balwinder S "bsd" Dheeman Registered Linux User: #229709
Anu'z Linux@HOME (Unix Shoppe) Machines: #168573, 170593, 259192
Chandigarh, UT, 160062, India Plan9, T2, Arch/Debian/FreeBSD/XP
Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/
The Doctor
Balwinder S Dheeman <bsd.S...@cto.homelinux.net> wrote:
>On 03/22/2009 02:52 AM, The Doctor wrote:
>> Step one accomplished Debian on one machine.
>>
>> I chacked the network interface files and yes the gateway
>> is correct.
>>
>> I cannot get the Debian Box to passed the Gateway.
>>
>> What do I need to fix?
>
>Please provide more information.
>
>Can you from your debian machine, ping:
>
>1) 127.0.0.1
Yes.
>2) ip.add.re.ss of your debian machine
YEs.
And NS1 and NS2.
>3) ip.add.re.ss of your gateway?
>
No :-~
>--
>Dr Balwinder S "bsd" Dheeman Registered Linux User: #229709
>Anu'z Linux@HOME (Unix Shoppe) Machines: #168573, 170593, 259192
>Chandigarh, UT, 160062, India Plan9, T2, Arch/Debian/FreeBSD/XP
>Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/
Balwinder S Dheeman
> In article <lb6g96x...@news.homelinux.net>,
> Balwinder S Dheeman <bsd.S...@cto.homelinux.net> wrote:
>> On 03/22/2009 02:52 AM, The Doctor wrote:
>>> Step one accomplished Debian on one machine.
>>>
>>> I chacked the network interface files and yes the gateway
>>> is correct.
>>>
>>> I cannot get the Debian Box to passed the Gateway.
>>>
>>> What do I need to fix?
>> Please provide more information.
>>
>> Can you from your debian machine, ping:
>>
>> 1) 127.0.0.1
>
> Yes.
>
>> 2) ip.add.re.ss of your debian machine
>
> YEs.
>
> And NS1 and NS2.
>
>> 3) ip.add.re.ss of your gateway?
>>
>
> No :-~
Can you ping ip.add.re.ss of your gateway from other machines in your
network? If not ...
Is the ip.add.re.ss of your gateway within your network address range?
Hope that http://jodies.de/ipcalc helps. Are your cables, hubs and, or
switches are intact or working?
The Doctor
Balwinder S Dheeman <bsd.S...@cto.homelinux.net> wrote:
>On 03/22/2009 04:30 AM, The Doctor wrote:
>> In article <lb6g96x...@news.homelinux.net>,
>> Balwinder S Dheeman <bsd.S...@cto.homelinux.net> wrote:
>>> On 03/22/2009 02:52 AM, The Doctor wrote:
>>>> Step one accomplished Debian on one machine.
>>>>
>>>> I chacked the network interface files and yes the gateway
>>>> is correct.
>>>>
>>>> I cannot get the Debian Box to passed the Gateway.
>>>>
>>>> What do I need to fix?
>>> Please provide more information.
>>>
>>> Can you from your debian machine, ping:
>>>
>>> 1) 127.0.0.1
>>
>> Yes.
>>
>>> 2) ip.add.re.ss of your debian machine
>>
>> YEs.
>>
>> And NS1 and NS2.
>>
>>> 3) ip.add.re.ss of your gateway?
>>>
>>
>> No :-~
>
>Can you ping ip.add.re.ss of your gateway from other machines in your
>network? If not ...
YEs.
>
>Is the ip.add.re.ss of your gateway within your network address range?
>Hope that http://jodies.de/ipcalc helps. Are your cables, hubs and, or
>switches are intact or working?
>
Irrelevant.
However the gateway router can ping the Debian box.
>--
>Dr Balwinder S "bsd" Dheeman Registered Linux User: #229709
>Anu'z Linux@HOME (Unix Shoppe) Machines: #168573, 170593, 259192
>Chandigarh, UT, 160062, India Plan9, T2, Arch/Debian/FreeBSD/XP
>Home: http://cto.homelinux.net/~bsd/ Visit: http://counter.li.org/
wisdomkiller & pain
....
> Irrelevant.
>
Nothing is irrelevant.
> However the gateway router can ping the Debian box.
>
Damnfsck, what is the output of "route -n" on the debian box?
Where does the default route entry point to, or is it unset?
The Doctor
Oddly enough the gateway is set to 0.0.0.0 . Huh??
BTW /sbin/ifconfig yields the correct IP information.
The Doctor
The Doctor <doc...@doctor.nl2k.ab.ca> wrote:
>In article <1570257.1...@woodpecker.motzarella.org>,
>wisdomkiller & pain <leaf-node.2...@spamgourmet.com> wrote:
>>The Doctor wrote:
>>
>>....
>>> Irrelevant.
>>>
>>Nothing is irrelevant.
>>
>>> However the gateway router can ping the Debian box.
>>>
>>Damnfsck, what is the output of "route -n" on the debian box?
>>Where does the default route entry point to, or is it unset?
>>
>
>Oddly enough the gateway is set to 0.0.0.0 . Huh??
>
>BTW /sbin/ifconfig yields the correct IP information.
>
Further:
route -nv -FC
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
204.209.81.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
Kernel IP routing cache
Source Destination Gateway Flags Metric Ref Use Iface
204.209.81.12 204.209.81.1 204.209.81.1 0 0 0 eth0
204.209.81.12 204.209.81.1 204.209.81.1 0 0 0 eth0
204.209.81.12 204.209.81.11 204.209.81.11 0 1 0 eth0
169.254.183.26 169.254.255.255 169.254.255.255 bl 0 0 1 eth1
204.209.81.2 255.255.255.255 255.255.255.255 bl 0 0 8 lo
204.209.81.11 204.209.81.12 204.209.81.12 l 0 0 1491 lo
204.209.81.12 204.209.81.255 204.209.81.255 bl 0 0 1 eth0
204.209.81.32 204.209.81.255 204.209.81.255 ibl 0 0 0 lo
204.209.81.11 204.209.81.12 204.209.81.12 il 0 0 114 lo
204.209.81.32 204.209.81.255 204.209.81.255 bl 0 0 0 lo
204.209.81.2 255.255.255.255 255.255.255.255 ibl 0 0 8 lo
204.209.81.19 204.209.81.255 204.209.81.255 bl 0 0 1 lo
204.209.81.1 204.209.81.12 204.209.81.12 il 0 0 1 lo
204.209.81.2 is the Ethernet side of a Cisco Router.
The Doctor
Further yet:
ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:48:9d:25:90
inet addr:204.209.81.12 Bcast:204.209.81.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe9d:2590/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:469916 errors:0 dropped:0 overruns:0 frame:0
TX packets:32531 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:44379387 (42.3 MiB) TX bytes:2465236 (2.3 MiB)
Memory:df220000-df240000
less /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 204.209.81.12
netmask 255.255.255.0
network 204.209.81.0
broadcast 204.209.81.255
gateway 204.209.81.2
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 204.209.81.1 204.209.81.3
Magnate
> The Doctor <doc...@doctor.nl2k.ab.ca> wrote:
>>wisdomkiller & pain <leaf-node.2...@spamgourmet.com> wrote:
>>>The Doctor wrote:
>>>
>>>....
>>>> Irrelevant.
>>>>
>>>Nothing is irrelevant.
>>>
>>>> However the gateway router can ping the Debian box.
>>>>
>>>Damnfsck, what is the output of "route -n" on the debian box?
>>>Where does the default route entry point to, or is it unset?
>>>
>>
>>Oddly enough the gateway is set to 0.0.0.0 . Huh??
>>
>>BTW /sbin/ifconfig yields the correct IP information.
>>
>
> Further:
>
> route -nv -FC
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 204.209.81.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0
> eth1
You don't have a default route, so any packets destined for anywhere other
than the two networks specified above have nowhere to go. Try
route add default gw 204.209.81.2
CC
The Doctor
That fixes it. However I thought upon setup
that was implied As I was using a netinst CD.
Magnate
You are correct that this should have been set correctly at installation - I
was merely hoping to establish the nature of the problem.
To fix it permanently, you need to edit /etc/network/interfaces. You need to
find the stanza which defines eth0 and add the line
gateway 204.209.81.2
- this should result in the default route being set up when eth0 is
activated.
If the gateway line is already present in /etc/network/interfaces then the
problem is more serious.
CC