running fc10 in a vmware setup Added /etc/sysconfig/network-scripts/ifcfg-eth0:0 to create another interface and all works fine (IPADDR=10.99.56.98). Would you expect this to be available after a reboot, last reboot I had to run ifup eth0:0
View 7 RepliesI am applying a virtual interface (eth0:0) which is failing after the system reboots. It actually cause the default interface (eth0) to fail as well, I must manually go in and remove the configuration for the eth:0:0 and restart the network to get it running again. How do I successfully add a Virtual interface to Fedora 11 that will stick when rebooted.
eth0: 192.168.0.200, 255.255.255.0, 192.168.0.1, BROADCAST: 192.168.99.255
eth0:0 192.168.0.98, 255.255.255.0, 192.168.0.1, BROADCAST: 192.168.99.255
I have installed Fedora 14 about 4 days ago. I have set all the networking parameters like dns path, hostname etc. I have also ensured that I select the check-box for "Enable automatically when system starts" for eth0 interface. But weirdly, whenever I boot my system(or restart), I see that the interface eth0 is disabled. I have to manually enter as root and enable it, each time I boot/reboot my system. Why is this happening? Could you please suggest a way so that I have eth0 interface enabled always when I boot up?Also, my domainname also is not boot-persistent. What steps should I take to ensure that the domainname set once persists across reboots?
View 12 Replies View RelatedI'm configuring an HP Mini 110 (wireless BCM4313) to use it as a small Access Point (ad-hoc mode).
I want to make my configuration reboot friendly. With what I have right now, as soon as I reboot the laptop, the wireless interface configuration isn't correctly setup. I have to do "ifdown eth1; ifup eth1" manually.
Here is what I have in /etc/network/interfaces for the wireless interface code...
So the question is how can I avoid having to bring down and up the interface?
My centos host (running under VMware) is called localhost.localdomain I've tried to rename this is a myriad of ways:
* I've altered HOSTNAME variable in /etc/sysconfig/network
* I've created a file called /etc/hostname with the new name
* I've modified /etc/hosts
* I've written the new name to /proc/sys/kernel/hostname
* I've used sysctl -w kernel.hostname=NEWNAME
* I've run hostname NEWNAME
and yet after reboot the name remains localhost.localdomain
I heard from my friend that i could launch programs and make them use different network interface instead of default (USB0 [3g connection] instead of ETH0 [normal ADSL connection..])I tried to google for a while and ask around in IRC, no luck so far.
View 1 Replies View RelatedI've a headless custom device that boots from USB using live image. Since I cannot access the device through the network, I need a way to persist boot related log files (dmesg, boot.log, messages) to view them on another computer. I also need to know how can I run custom commands on startup of live image.
View 3 Replies View RelatedI've a headless custom device that boots from USB using live image. Since I cannot access the device through the network, I need a way to persist boot related log files (dmesg, boot.log, messages) to view them on another computer. I also need to know how can I run custom commands on startup of live image.
View 3 Replies View RelatedSo I found many methods on google, but no one works. It seems that this one is THE Debian way.
Code:
### BEGIN INIT INFO
# Provides: mystartupscript
#[code]...
Is there any web interface that I can install to remotely reboot ubuntu? It would only be accessible via a VPN or on the LAN so not too much worry over security.
View 3 Replies View RelatedMy bluetooth chip is no longer seen by bcm203x. Only thing I did before last rebooting was upgrade udev.
Edit: I built in all bluetooth protocols and drivers, still no interface shown in hciconfig.
I've installed transmission-daemon on my headless Ubuntu 11.04 server and use the web interface to manage it. This is all working fine. However, after a reboot it seems that transmission daemon starts but the webinterface is unavailable. I get this in the syslog after a reboot:
Code:
Jun 22 10:54:27 localhost transmission-daemon[703]: Transmission 2.31 (12441) started (session.c:706)
Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Adding address to whitelist: 192.168.*.* (rpc-server.c:805)
Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (rpc-server.c:982)
Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Whitelist enabled (rpc-server.c:986)
Jun 22 10:54:27 localhost transmission-daemon[703]: RPC Server Password required (rpc-server.c:989)
Jun 22 10:54:27 localhost transmission-daemon[703]: Port Forwarding Stopped (port-forwarding.c:181)
Jun 22 10:54:27 localhost transmission-daemon[703]: UDP Failed to set receive buffer: requested 4194304, got 262142 (tr-udp.c:75) .....
I just had an ATT Uverse RG installed. However my Smoothwall router that previously worked fine with the ADSL SpeedStream is no longer accepting an address assignment DHCP ip address from this new gateway. (3800HGV-B)Any thoughts ideas or experience working with this hardware? ATT only supports Windows and Mac
View 2 Replies View RelatedI have a ppp0 entry with post-up options like this
mapping ppp0
map none photon-plus motorola
map timeout: 12
[code]...
some of you might have experienced the network speed problem that occurs when ipv6 is enabled. So have I. I know about the common workaround of disabling ipv6, but recently I tested the new ubuntu live system, and the problem was gone with ipv6 being enabled.
Now my question is: Do you know what ubuntu is making different? I haven't found an explanation. Is there a better workaround than blacklisting ipv6?
As root, I can mount the /home directory from my desktop to my laptop which uses wireless. However, when I logout the mount disappears. That is, I mount the directory, check it is mounted, then I logout, log back in as root, the mount is now not there. How do I make the mount persistent, always there?
I want the mount to persist so that the two ordinary users on my small household network can access the same files whichever computer they use.
It appears that this may be because the wireless link disappears when I log out. Both machines are using Fedora 10. A persistent mount used to work using Febora 8, but maybe some settings I am not aware of have changed.
I'm running CentOS 5.4 and have problems with a USB-Ethernet network interface. It works in another, very similar environment but now I added Virtualization when installing the system. The interfaces comes up as usb0 - as usual, and I'm sending and receiving packets (PPPoE) but there seems to be a link missing so that the ppp session can be build. I wondered if this has to do with the Xen virtual environment running which installed a lot of virtual interfaces and bridges, but not for the USB interface.
The problem is that for PPPoE server, the interface must not have an IP address assigned - not an option when creating a new host interface. But even when I do so, the interface seems unlinked somehow. Funny thing, I can monitor the incoming and outgoing packets using Wireshark. I have not (yet) set up a virtual machine/guest system but the default machine is running.
We are making an embedded product based on Fedora 10 (this could change, but right now we stick to 10 because it works ok). We have an intel PC board with a build a normal ethernet adapter. Then we have a home build PCI-express card with 4 ethernet adapter build into a Xilinx FPGA (Xilinx Temac) (we got the driver from git.xilinx.com and modified it enough to make it work).
Now, by problem is: How do we control the device names of these ethernet adapters? It would be really nice to have them called eth0, eth1-eth4 in the order mentioned above, such our software always knows which to use for what.
Also: What to we do when the our adapter card is replaced because it is broken? A new card will have new MAC addresses and therefore the adapters will get new names destroying our IP configurations.
I have web application running on my server and can access this over the GUI.
This morning I can no longer access the gui interface. The activity LED flickers non stop on my nic card. I cannot ping or ssh into the server. However can access it directly from console and system is responsive when doing that. So i think this is a n/w issue... Any thoughts? How can I troubleshoot this?
I'm just installed Fedora 14 64-bits into a server which come with Multiple network interfaces, I'm found that the naming of each network interface is not in sequences in what I'm thought (e.g: the on board network interfaces name as Eth5 and Eth6, the additional card ethernet port name from Eth0 - Eth1 and etc). How to name the interfaces as what I wish to? What should I install to allow me to rename the interfaces.
View 2 Replies View RelatedI'm a newbie on Linux and trying to find my feet so please be kind.I have installed vmware on my XP laptop and have installed fedora core 9. Network setting on the VMware is set to bridged. My interface eth0 which is using the wireless does not start on boot. I have to run ifup ifcfg-eth0.The file ifcfg-eth0 had onboot=yes and NM=no, so i changed it so that the NM=yes.However this does not resolve the problem at all. I have put the file back to its original configuration and I have disabled network manager and have had no luck
View 2 Replies View RelatedI have two network interfaces on my computer but only one of them is connected to an Ethernet cable. Until now on every Fedora release, the activated primary interface has been named as eth0 and everything has always worked well without any problem. Recently I switched to Fedora Core 12 and surprisingly I observed that for the first time, my primary interface has been considered by the system to be eth1 instead of eth0. I tried to replace the content of ifcfg-eth0 by ifcfg-eth1, yet system gave me an error that there was MAC address mismatching. I conserved their MAC addresses in their files and just replaced other connection parameters ( such as IP ADDR, NETWORK, NETMASK, etc.) but it did't work. When I do "server network restart", the command blocks.
As I try to install oracle on this system, regarding the fact that oracle requires static network configuration on the primary network interface, I don't know how to proceed in order to set eth0 as my primary interface (or rather set the current eth1 to eth0 because it is actually eth1 that refers to my activated primary network card).Just one more time, I would like to remark, that with previous versions of the Fedora Core, on the same computer (with the very same two network cards) I never had problem and I had installed oracle on the system with success, having the statically configured eth0 correctly detected by the system.
I have a set up with a computer that has two network cards and is connected to two networks. Both networks connect to the internet via separate routers that have DHCP enabled. I can set one of the routers up to do port forwarding to the computer without any complications but if I want to do the same on the other router the port forwarding from it doesn't work and I can't reach the system.
I know for a fact that the services are accessible from both networks and both routers can forward ports to other computers in their network. The networks are 10.10.0.1/24 and 172.22.0.1/24. I've tried turning off iptables but that didn't change anything.
Is there any kind of setting that could prevent the interface on the computer to reject traffic using NAT or something?
If I disable the interface on the working network (ifdown eth1) then suddenly eth0 on the other networks starts accepting requests sent to it via the router that does the port forwarding. I do however want to emphasize that services work just fine as long as the requests originate from either of the networks they are on.
I upgraded from kernel-2.6.38.6-27.fc15.x86_64 to kernel-2.6.38.7-30.fc15.x86_64. After the upgrade I no longer have a wireless interface in Network Management. I have a broadcom BCM4312, booting the previous kernel solves this problem.
View 9 Replies View RelatedI have entered my primary and secondary DNS addresses through Network Configuration tool (system-config-network). But whenever I reboot the system it loses the DNS addresses. Following another thread, I tried changing the PEERDNS=no in ifcfg-wlan0; but it didn't work. I also put both DNS addresses in the ifcfg file, but that didn't work either.Does anyone know a solution to this?$ uname -aLinux fedoralinux 2.6.27.15-170.2.24.fc10.i686 #1 SMP Wed Feb 11 23:58:12 EST 2009 i686 i686 i386 GNU/Linux
View 11 Replies View RelatedI have installed fedora core 9 and configures the ifcfg-eth0 script as below. my problem is the network is not coming up after reboot. after the reboot if i restart the network service(service network restart) network is coming up.
View 12 Replies View RelatedSomeone just erased my HWADDR line from /etc/sysconfig/network-scripts/ifcfg-eth0. How can I obtain my original MAC address?
Code:
ifconfig eth0 does not work (it shows the wrong MAC address) since the HWADDR line from the file I mentioned above was erased. Also there is no ifcfg-eth0.bak backup configuration file.
is it possible to setup a DHCP server using the loopback or a virtual interface? I installed Sun VirtualBox on my fedora system and want to try and kickstart them from within the same box on a virtual network. Is this possible and has anyone done it? I only have a single NIC in the box and it is on my public network.
View 1 Replies View RelatedIve been struggling to configure a wireless interface on Fedora 9I need to configure wlan0 command line only with NO display managerIve tried setting up /etc/sysconfig/network-scripts/ifcfg-wlan0 with the right information, doing dhcpbut no ip is retrieved. Checking the dhcp server logs on the DHCP server - no request is received.The link light on the wireless nic is not on either. iwconfig shows it has an Access point associated and an ESSID but im not getting back any IP.There seems to be very little documenta on how to set up wireless nics command line only on Fedora
View 1 Replies View RelatedOn FC10, when system boots up, it would auto detect (from DHCP) and configure eth0.
This does not happen on FC11, but I can manually configure the interface. The entries in /etc/sysconfig/network-scripts/ifcfg-eth0 are identical on both OS releases.
Don't know if this is related, but when I run System->Administration->Bootloader, it fails system-config-boot - missing module kudzu.