Alvin Oga wrote:
yup ... your mask 255.255.255.0 says use only the last octet ..
10.0.0.x is NOT in the same network as 10.1.1.x
it's doing what you told it ... maybe not what you want
if you want to use 10.0.0.2 ... don't... "0" is best used for network name
use 10.1.1.2 and your trouble
Matt Perry wrote:
On Mon, 2 Aug 2004, Jonathan Barnes wrote:
eth1 Link encap:Ethernet HWaddr 00:05:1C:13:5C:8D
inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
That's odd. The line above should contain "RUNNI
Matt Perry wrote:
On Sun, 1 Aug 2004, Jonathan Barnes wrote:
Destination Gateway Genmask Flags Metric RefUse Iface
10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0
10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth1
Matt Perry wrote:
On Sun, 1 Aug 2004, Jonathan Barnes wrote:
I cant see anything wrong with my routing table either:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
10.0.0.00.0.0.0 255.255.255.0 U 0 00 eth0
John Summerfield wrote:
I _thought_ you might be Australian.
Yes I am :)
I don't know just that your tools are on Windows: boot Linux (Knoppix
is fine) if you can. From there,
traceroute x.com
ping -R -c4 x.org
and see where routing breaks.
Also, on Debbie (the Debian box)
sysctl -a | grep ip_
H
Matt Perry wrote:
On Sun, 1 Aug 2004, Jonathan Barnes wrote:
my Debian Box. eg: The Firewall can ping my Debian Box, but my Debian
Box can't ping the firewall.
It's sounds like IP forwarding isn't working. Take down the interface
that uses 10.1.1.1 and then try to ping the
Hi, I'm having a very strange networking problem that has my linux
buddies and I stumped.
I'll draw a basic mud map because it makes it ALOT easier to understand
my situation as I have two gateways due to shared housing.
[Bridged ADSL Modem]
|
[Firewall]
(220.244.217.*, 10.0.1.1, 10.0.0.
7 matches
Mail list logo
