to /etc/sysconfig/network/network-scripts/route-eth0 after doing 'service network restart' I'm do see the new route as described by directive above. However, I still do not see the default gateway that's supposed to be on my box. Where/how do I define the default gateway using the route-ethX method above?
I have the following network/server configuration:
[Code]....
How do I prevent eth1 from being able to overwrite the default gateway that eth0 has already set?!? I read that one can create route-* files in the /etc/sysconfig/network-scripts/ directory to setup static default routes.But those seems to require one to know the IP address of the gateway, but in my case the ISP's gateway is served via DHCP and so it could vary from day to day. Here are the contents of some of the relevant files:
When ever I restart the machine, both interfaces pull a IP, but the it randomly chooses eth0 or eth1 to have the gateway. I want the gateway to be eth0 always.
[Code]...
Is there some file or setting I can modify in Fedora10 that will always choose 192.168.1.1 on eth0 as the default gateway?
I've been seeing a bunch of issues with the /etc/resolv.conf not picking up the nameservers for 3g connections, and managed to fix that issue using tips found here.. the one thing I m having a problwm with is my 3G USB modem not picking up a default route/gateway. I can connect using KNetworkManager, get an IP and nameservers, but.
[Code]..
And to top it all off, I cannot figure out what the default gateway should be from verizon to just write a script out myself that'll do it automatically.
I would like, from a C program, find the hardware MAC address of the default route path. With BASH I can do a 'route' find 'default and then an ifconfig and grep for 'HWaddr'. Are there C calls to do the same??
I have a static ip on my wired (eth0) connection. I thought I had it well set up in yast. In the routing section I do have my default gw coming up there, with the the right nw i/f (eth0) associate with it. However, when I boot up, y config seems to ignore that fact, and I have to keep goign to root and typing "route add default gw <mygwip>" each time, which is something I want to avoid. Isn't it odd that the route settings created by yast have no effect? If they did, the route would be set up on bootup and I would haven't to do that typing.
I'm currently struggling with the following problem: Connecting to a wired network with NetworkManager (0.7.1) is no problem at all: Everything is set up automatically, including the default route:
[Code]....
When I now add the route manually it works. But as soon as the cable is plugged in, the NetworkManager overwrites the routing table entry again (which makes it quite annoying). Does anyone know a way to avoid this behaviour?
I'm currently working with Ubuntu 10.10.I wanted to add a default route to a gateway named ppp0.I did it with the command> route add default ppp0It works ok. But then from time to time it suddenly stops and I have to go back again to the server and retype the command. I'm clueless as to why is it happening. I can assure no one is working at the server or doing anything over there.Does anyone know causes that might be triggering route default to stop working?Btw where is the best place to add this command so it will be executed automatically on start-up and without needing to login to the server?
I am attempting to run apache on my linux router while connected to a VPN. My default route is set to the VPN endpoint and I cannot control port forwarding at that end. I cannot seem to connect to any service that i bind to the eth0 interface. I believe that my iptables rules and OpenVPN are the source of the problem.
/sbin/iptables -t nat -A POSTROUTING -o tun1 -j MASQUERADE /sbin/iptables -A FORWARD -i tun1 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT /sbin/iptables -A FORWARD -i eth1 -o tun1 -j ACCEPT
eth0 is the default route, and eth3 is being used for something else. So what I want to do is load balance browsing between eth1 and eth2. I've added all of the routes in the LARTC guide, but the command to enable the load balancing:
Quote:
ip route add default scope global nexthop via $P1 dev $IF1 weight 1 nexthop via $P2 dev $IF2 weight 1 obviously involves creating a new default route. Since I'll be using Squid to push the traffic through the relevant line, how can I set up a load-balanced link for eth1 and eth2 without changing the existing default route on the server?
In an attempt to get something that, well, you know, just works... I migrated a laptop to Karmic server today. Which works fine, except for one thing: when I use wvdial and a Huawei E160g USB modem to connect to the Internet (which is the only option out here in the sticks where I live) no default gateway is set. When I add one manually everything is fine, except that the default gateway keeps disappearing after a while (at irregular intervals, as far as I can see). Nothing appears in any logfile that even mentions the default route, let alone a reason for its magical vanishing trick. My wvdial.conf is fairly pedestrian:
[Code]...
What's going on here? I'm stumped. And the mighty Googlebrain doesn't seem to know, either. How do I get wvdial & friends to set the correct default route upon connecting? Given the fact that without a default route a PPP connection to a remote network is little use, I would expect this to be a standard feature and not something that I'd have to script a work-around for myself. But then, I have been wrong before. Secondly, and more importantly, why does my default route keep disappearing without a trace?
I have a home server running Lucid which basically runs our home lan, but I also wanted to be able to run transmission-daemon over an ipredator VPN connection completely independently of the ethernet port (as far as the application layer is concerned anyway). Most of the howtos for setting up VPN use the VPN as the default route, however I still wanted to run a webserver, dnsmasq etc, not to mention free bandwidth access to my ISP etc.
Thus, this howto. The ppp connection still tunnels through eth0, but as far everthing else is concerned my server has two independent network ports eth0 and ppp0 and applications use the default route via eth0 to our router unless explicitely directed down pppX. I assume that you already have transmission-daemon installed.
I ask your help to diagnose a problem. For business reasons I use a broadband internet connection via a mobile phone's connected via bluetooth [rfcomm]. Speed is not the maximum but it is more than sufficient for my work. For configuration of ppp I followed this guide Pon pulls up dialup, but I can't navigate also if resolv.conf and default route are correct. In addition I would like to use the NetworkManager that by default, does not see the device. I worked around the problem this way:
I modified the / etc / rc.local so that launch at boot time: # Rfcomm bind yes
After starting Lucid Lynx, bluetooth connects to the phone but NetworkManager does not see the modem. When I run the connection manually, by: # Pon BluetoothDialup
NetworkManager sees the device, but can not use it because obviously it is locked by the ppp daemon. So I close the connection with: # poff
Now NetworkManager sees the broadband modem via / dev/rfcomm0, dialup is performed properly. I can finally surf and just enable vpn with NetworkManager. all start automatically at boot, without the need to manually connect and disconnects the dialup to use, finally, the NetworkManager.
i have setup an open vpn server and when i connect to it the client pulls an IP and but not default gateway. My goal is to route all web traffic through the VPN... My config file looks like this...
Code:
dev tun proto tcp port 1194 ca /etc/openvpn/easy-rsa/keys/ca.crt
In 11.3, if in "/etc/sysconfig/network/ifcfg-eth0" i set DHCLIENT_SET_DEFAULT_ROUTE="no" this seems to have no effect. If i start my box, the routing table has the "default route"-entry offered by a remote DHCP-Server. More Info: My Susebox has eth0 and eth1 and both network devices should use DHCP4. But from DHCP-offer on eth0 i want to use
yesterday I installed openSUSE 11.2 on my laptop. But I'm having problem getting the wifi configured properly. During the installation I got the message "No network running" (which I also saw after the installation when using the network configuration module of YaST after switching from ifup to NetworkManager). After installation NetworkManager seemed to work fine, it detected my wifi card, found the network, and I could even connect to it. Then the problems began, no Internet connection. The first thing I tried was pinging Google which yielded an "unknown host" message. So I checked /etc/resolv.conf, to look for the DNS servers, which where missing.
I added them manually and tried again. Still no luck, so I started pinging my router, which worked, tried again pinging Google using one of there IP addresses, which failed. So I ran route to find out which routes where being used, this one gave an unexpected result, because it only showed the route to the local network (I'm not sure about the loopback one, because this was also a lot of times missing when testing):
I have been encountering this problem, not only on 10.4, but on older versions too: I use a wifi router to connect my laptop to the Internet, but sometimes I need to connect directly to another computer to move some files over GLAN. But Ubuntu's Network manager doesn't allow me to configure the eth0 interface without specifying a gateway (no gateway = grey submit button), but when a gateway is specified, it always rewrites the default gw specified already by the active wifi connection and returns back after unplugging the eth cable.
Of course this can be solved by a few route commands, but this is unacceptable since it is needed to establish the cable connection without any further assistance from within and as well without replacing the default gw and thus breaking the Internet connection. Is there, please, any possibility how to prevent Network Manager from replacing these routes?
br0 - 192.168.0.1 - Internet eth2 - 192.168.1.1 - LAN tun0 - 10.0.0.2 - VPN (via br0)
What I'd like to do is to route all TCP packets coming from eth2 to tun0 where a VPN client is running on 10.0.0.2. If I delete all default routes and if I add a new route to tun0 like :
Code:
route del default route add default gw 10.0.0.2
Everything is fine, and everyone on eth2 can reach the Internet using the VPN access. Now the problem is that my VPN client does not allow any other protocols other than TCP. And I also want to allow VPN access only to eth2, no other LAN nor the router itself. use iptables to filter any TCP packets and mark them, so they can be sent to tun0, while any other packets can reach the Internet via br0 (192.168.0.1). I found on the Internet that we can mark packets before they get routed. Using the following commands :
Code:
iptables -t mangle -A PREROUTING -j MARK --set-mark 85 -i eth2 -p tcp --dport 80 ip route add table 300 default via 10.0.0.2 dev tun0 ip rule add fwmark 0x55 table 300
First of all, --dport 80 never work... :/ I wanted to filter TCP 80 packets coming from eth2, but none of them seems to be HTTP packets... oO (very strange...). Nevermind, I decided to forget about the --dport option. I use the "iptables -L -v -t mangle" command to see how many packets are marked, and it is working fine, all TCP packets coming from eth2 are marked. Now the problem is that none of them are routed to tun0 they are all respecting the "route -n" rules... and not the "table 300" rule I have created.
I have OpenVPN working well, but I can't figure out how to change the default route. By default, a "route" shows me: 192.168.0.100 * 255.255.255.255 UH 0 0 0 tun0 But I want it to read: 192.168.0.0 192.168.0.100 255.255.255.0 UG 0 0 0 tun0 ... so I can access other computers on the network. I can accomplish this manually by running: ip route add 192.168.0.0/24 via 192.168.0.100 dev tun0 proto static How can I get this to be the default route? I've tried adding push "route 192.168.0.0 255.255.255.0" to my /etc/openvpn/openvpn.conf on the VPN server but that has not helped.
I got this definition:"a process that replaces a series of related, specific routes in a route table with a more generic route." honestly I found it not so clear.. I want to know if this definition is correct and also more details about this subject..
Having trouble getting my Netgear WNA1000 working thru wireless router. Have tried lots of suggestions from other threads to no avail. Someone suggested that th routing table isn't set correctly, so have been trying to use the follwing to make the proper entry in the routing table: sudo route add -net 192.168.0.1 netmask 255.255.255.0 dev wlan0
Result: error message stating with: "route: netmask does not match route address"
followed by "Usage" instructions which tell me to do what I just did. Any ideas on how I can populate my routing table with correct entry for my wireless card? Not to complicate matters, but I temporarily turned off encryption on my router to eliminate that as a possibility until I get connected. So maybe it'still trying to connect via encrypted mode - do I need to turn off encryption on my (client) end?
basically what i'm trying to do is get sound from flash videos on videos. my plan is to use gnash to play flash files within firefox. since gnash uses gstreamer to output audio and since i'm using jack for playback, i need to somehow route gstreamer to jack. does anyone know how to do that? here is an ubuntu thread that may help, but i'm not sure how to translate that to fedora. i'm already able to hear the sine tone from running:
code: gst-launch audiotestsrc ! audioconvert ! audioresample ! jackaudiosink in the console. i just don't know what to do next.
I have two system, an Intel Core2 Duo system running the 32-bit version of Fedora 12, and a MacBook Pro running the 64-bit version of Fedora 12. I'm using the Gnome desktop on each system. I have enabled all the services I believe are necessary to support NFS including nfs, rpcbind, rpcgssd, rpcidmapd, and rpcsvcgssd on each system. I have added an entry to my /etc/exports file to export my home on each system, and if I type this command:
$ showmount -e localhost
I get a result like this:
Export list for localhost:
/home/tron 192.168.200.101,192.168.200.100
However when I issue this type of command:
$ showmount -e <remote host name>
I get this kind of result: rpc mount export: RPC: Unable to receive; errno = No route to host Research on the Internet indicates this is usually due to a firewall problem. However, I use the Firewall Configuration application to the disable the firewall on both systems, and I continue to get the same result. What is needed so I can get this two machines to display their exported file shares remotely? It turns out I did not disable the firewall when I thought I had. Now that I'm certain the firewall is disabled on both systems, I'm able to get the showmount command to succeed.
I setup my old laptop for my mom with F13 and have sshd running. My dad set up their DD-WRT router so that it's forwarding port 22 to the laptop's ip address. Yet, I get "No route to host" when I try and ssh in from my house. Is there anything that would be preventing F13 from accepting the SSH connection?
I am using RHEL4 server in my network. I have configured VLAN in my network. i am using two gatways to access my Network. I also add two gateways to both the network. but only one gateways will work. Then I added a route for the other netowrk. but when i restart my computer my route is deleted. i used this command to add the route
I used ssh to log into my sever that I had and I from there I ran the command dhclient eth by mistake on the server but the serve had an static IP address. Unfortunately I can't ssh back into the server anymore! It replies back with No route not host. Now my questions are. First of all how do I change it back into the previous setting? Secondly, can I do this remotely since the server is in another place and I don't have access to it right now or do I have to go there and sit behind it and play around with it there?
I have two system, an Intel Core2 Duo system running the 32-bit version of Fedora 12, and a MacBook Pro running the 64-bit version of Fedora 12.
I'm using the Gnome desktop on each system. I have enabled all the services I believe are necessary to support NFS including nfs, rpcbind, rpcgssd, rpcidmapd, and rpcsvcgssd on each system.
I have added an entry to my /etc/exports file to export my home on each system, and if I type this command: $ showmount -e localhost
I get a result like this: Export list for localhost: /home/tron 192.168.200.101,192.168.200.100
However when I issue this type of command: $ showmount -e <remote host name>
I get this kind of result: rpc mount export: RPC: Unable to receive; errno = No route to host
Research on the Internet indicates this is usually due to a firewall problem. However, I use the Firewall Configuration application to the disable the firewall on both systems, and I continue to get the same result.
What is needed so I can get this two machines to display their exported file shares remotely?
I am trying to share directories between two F12 machines on a local network with a router box doing DHCP because not all machines on all the time. Web access is fine and local ping and ssh works but telnet doesn't. I have never succeeded doing mounts. So I have been searching for things to fix the above and have just tried rpcinfo. If I do this :
rpcinfo -p 192.168.2.2 it gives rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host. Does that suggest that actually there is an installation problem? So I tried "yum provides portmapper" and that gives "No Matches found".
