On Thursday 29 January 2004 07:59 pm, Christopher Blough wrote:
> Here is an updated capture of route -n
> --
> Kernel IP routing table
> DestinationGateway Genmask Flags Metric Ref
> Use Iface
> 209.112.193.120 *255.255.255.248 U 0 0
Here is an updated capture of route -n
--
Kernel IP routing table
DestinationGateway Genmask Flags Metric Ref Use
Iface
209.112.193.120 *255.255.255.248 U 0 00
eth0
netstat -nr results
Kernel IP routing table
D
I will get a copy of route -n information when my machine is at hand. At the
moment, I'm at work, and it isn't available. IIRC, the only entry was
something like this:
AddressGateway
209.112.xxx.120*
There was only that one entry.
The IP address listed in my route add example
Quoting Christopher Blough <[EMAIL PROTECTED]>:
[snip]
> route add -net default gw 209.xxx.xxx.xxx also returned a 'network is unreachable'
> error. Essentially, I am seeing my LAN boxes fine, but am completely unable to go
> past my firewall. Before anyone asks, yes, it's properly punched. All e
On Thursday 29 January 2004 01:47 pm, Christopher Blough wrote:
> I have recently made my first foray into Debian.
Welcome.
> I am able to ping the other three Windows-based boxes on my LAN (same
> subnet as this box). However, any attempt to resolve an internet
> address or to go outside of
Greetings,
I have recently made my first
foray into Debian. Being a linux newbie, the entire experience has been filled
with a great deal of learning. That said, I've run into an odd issue that I
haven't been able to resolve via HOWTO or through older mailing list
posts.
I am usin
6 matches
Mail list logo
