no errors (RX, TX) seems allright. Is126.96.36.199 your router or server you connect to WAN ? I assume you use network manager try to look if dhcp is running if you can for example ping this forum or download
updates (maybe some DNS issue )
> # netstat -rn
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt Iface
> 0.0.0.0 188.8.131.52 0.0.0.0 UG 0 0 0 em1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 184.108.40.206 0.0.0.0 255.255.255.0 U 0 0 0 em1
> I do not quite understand why I see two em1 interfaces and why
> information about ip s is different from ifconfig
Those are two different rules, not two interfaces. The second one tells the
em1 route to addresses 143.239.109.*. With that rule in hand, you can get to
220.127.116.11. The first of the rules shows that to get to all other IP
addresses, one needs to use 18.104.22.168.
I am a little confused about your IP number. Please tell us more about the
On 02/08/2014 03:36 PM, Massimo33 wrote:
> lwfinger;2623248 Wrote:
>> On 02/08/2014 08:26 AM, Massimo33 wrote:
>>> # netstat -rn
>>> Kernel IP routing table
>>> Destination Gateway Genmask Flags MSS Window
>> irtt Iface
>>> 0.0.0.0 22.214.171.124 0.0.0.0 UG 0 0
>> 0 em1
>>> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0
>> 0 lo
>>> 126.96.36.199 0.0.0.0 255.255.255.0 U 0 0
>> 0 em1
>>> I do not quite understand why I see two em1 interfaces and why
>>> information about ip s is different from ifconfig
>> Those are two different rules, not two interfaces. The second one
>> tells the
>> em1 route to addresses 143.239.109.*. With that rule in hand, you can
>> get to
>> 188.8.131.52. The first of the rules shows that to get to all other
>> addresses, one needs to use 184.108.40.206.
>> I am a little confused about your IP number. Please tell us more about
> ok, what information exactly would be useful?
Why do you have a class C address on your box? Are you connected directly to the
modem without a home router? Most of us have an access point/router in the
middle and are given a non-routing 192.168.X.Y address.
this a campus network, so I am not sure of its configuration, but everything works well for nearby computers. The question is are there any means in linux to diagnose the problem?
and what these means are? from the information I provided looks like ok, but I am far from being expert.
and maybe try to set statci route via yast->network devices-> set some DNS servers here are some [CODE[i]Google Public DNS: 220.127.116.11, 18.104.22.168, 2001:4860:4860::8888, 2001:4860:4860::8844 info] OpenDNS: 22.214.171.124, 126.96.36.199 info] Norton DNS: 188.8.131.52, 184.108.40.206 info] DNS Advantage: 220.127.116.11, 18.104.22.168 ]
try different gateway maybe 109.1, 109.0 or 109.255 and set IP forwarding
> campus IT support only windows.
> I can ping my ip, I can ping the gateway, but not other ip’s
It seems you have a connection to the college network, but routing is not
working correctly. That is strange, as the routing table looked correct. Please
show the output of ‘ping -c5 22.214.171.124’. Perhaps that will provide a clue.
Did you obtain your IP using DHCP, or is that a static IP assigned by the college?
On 2014-02-09 21:26, Massimo33 wrote:
> deano_ferrari;2623436 Wrote:
>> Many campus networks will present an authentication page before allowing
>> you to browse non-campus web sites, or connect to external services.
>> Perhaps that is the issue.
> does that mean that without authentification page ( if any ) I can not
> ping ip addresses?
Your network is correctly set, as you can ping the gateway. Your campus
IT people is intentionally blocking you from accessing outside, so it is
they who have to support you. Request they be fired.
Some sites only allow internet browsing via proxy, meaning no any other
type of access outside except hhtp, and via their proxy and filters.
Perhaps looking at another computer running Windows and looking how the
proxy is setup, you can replicate the same thing.