network issue

Hi,

Please help if you understand networking.
I believe something is misconfigured in my system when I
use /usr/bin/sytem-config-network.

The network is fine using DHCP and "automatically obtain DNS info from
provider" However, it stops when I set it statically.

This is what it shows under /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=no
NETMASK=*************
IPADDR=*************
GATEWAY=*************

Using /sbin/ifconfig I get my inet addr, bcast and mask.

Now, if I enter "statically set ip addresses" (in the system-config-
network gui) and enter the inet addr, bcast and mask; and stop/restart
the network via gui /usr/sbin/system-config-services

then /etc/sysconfig/network-scripts/ifcfg-eth0 is changed to

DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=no
NETMASK=*************
IPADDR=*************
GATEWAY=**********

Note: another difference is that:


Note work set statically
[me@home network-scripts]# /sbin/ip route
aa.aaa.aaa.0/24 dev vnic0 proto kernel scope link src aa.aaa.aaa.2
bbb.b.ccc.0/2 dev eth0 proto kernel scope link src bbb.b.eee.29

working under dhcp
[me@home network-scripts]# /sbin/ip route
aa.aaa.aaa.0/24 dev vnic0 proto kernel scope link src aa.aaa.aaa.2
bbb.b.ccc.0/21 dev eth0 proto kernel scope link src bbb.b.eee.29
ddd.ddd.d.d.d dev eth0 scope link
default via bbb.b.ccc.1 dev eth0

Help!

Oh last info is that I am using
210.230.70.2
210.230.70.2
rosenet.ne.jp when I set dns statically
I think that is right
$ nslookup rosenet.ne.jp
Server: 210.230.70.2

Shawn

P.S. this is in an attempt to resolve past threads on realtek drivers
(not the issue) or lan cards (not the issue)


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: network issue
    ... The network is fine using DHCP and "automatically obtain DNS info from ... aa.aaa.aaa.0/24 dev vnic0 proto kernel scope link src aa.aaa.aaa.2 ... bbb.b.ccc.0/21 dev eth0 proto kernel scope link src bbb.b.eee.29 ...
    (Fedora)
  • Re: network issue
    ... The network is fine using DHCP and "automatically obtain DNS info from ... aa.aaa.aaa.0/24 dev vnic0 proto kernel scope link src aa.aaa.aaa.2 ... bbb.b.ccc.0/21 dev eth0 proto kernel scope link src bbb.b.eee.29 ...
    (Fedora)
  • Re: Traffic NOT moving through the correct network interface?
    ... 10.0.11.0/24 dev eth0 proto kernel scope link src 10.0.11.16 ... 68.145.52.0/22 dev eth1 proto kernel scope link src 68.145.54.200 ...
    (alt.os.linux)
  • Re: mysterious suse 9.2 and web access
    ... > I meant the network definitions of your machine. ... > but something with your local machine is wrong. ... a.b.66.0/24 dev eth0 proto kernel scope link src a.b.66.2 ... target prot opt source destination ...
    (alt.os.linux)
  • Re: networking a Pogolinux system
    ... I didn't install any firewall (this was within a safe network). ... xxx.xx.36.0/22 dev eth0 scope link ... > If there is no rule, then you should check route table. ...
    (comp.os.linux.networking)