Re: Revisted Eth1 problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ed Greshko wrote:
david walcroft wrote:
Ed Greshko wrote:
david walcroft wrote:
Mikkel L. Ellertson wrote:
Tim wrote:
On Tue, 2007-09-18 at 19:16 -0500, Mikkel L. Ellertson wrote:
As far as changes, I suspect that the Windows machine was providing
the DHCP server, and an update turned it off. (Internet connection
sharing, I think.)
I would expect the opposite, turning on internet connection sharing
tends to also turn the box into a DHCP server.  At least that was my
experience in the past.

It does, but an update can turn off Internet connection sharing. (I
was not sure of the name.) You never know what a Windows update will
do. I have even seen machines running 2 firewall programs because an
update urned on the Windows firewall, even though they already had
one running. It messed up printing to a network printer. I have even
seen DHCP blocked by installing a new firewall.

Mikkel
I now have the problem in which using "service network restart"
disconnects me from the net.

my /var/log/messages after a reboot

Sep 17 11:52:40 reddwarf NET[1838]: /sbin/dhclient-script : updated
/etc/resolv.conf
Sep 17 11:52:40 reddwarf dhclient: bound to 121.208.35.242 -- renewal in
1551 seconds.
Sep 17 11:52:40 reddwarf kernel: eth1: link up, 100Mbps, full-duplex,
lpa 0x41E1
Sep 17 11:52:40 reddwarf dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 7
Sep 17 11:52:47 reddwarf dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 16
Sep 17 11:53:03 reddwarf dhclient: DHCPDISCOVER on eth1 to
255.255.255.255 port 67 interval 14
/var/log/messages Thanks david
Do you still have eth1 set to get its IP address via DHCP?
No I set it up as a static IP
Really?

It hard to believe since you are seeing the message

DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14

Also, the netstat you posted....
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
121.208.32.0    0.0.0.0         255.255.248.0   U         0 0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0        0 eth1
0.0.0.0         121.208.32.1    0.0.0.0         UG        0 0        0 eth0

Would show the static address if it is indeed set.

Can you post the contents of /etc/sysconfig/network-scripts/ifcfg-eth1?


What is wrong with this ping.
Well, if the interface doesn't exist then potentially this would be the
error you'd get.

[[email protected] ~]$ sudo ping -c 5 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted

--- 192.168.0.1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4002ms

Thanks  david


Thanks Ed

My /etc/sysconfig/network-scripts/ifcfg-eth1

# Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=none
HWADDR=00:14:78:04:C4:91
TYPE=Ethernet
NETMASK=255.255.255.0
IPADDR=192.168.0.1
USERCTL=yes
IPV6INIT=no
PEERDNS=yes

Thanks  david


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux