given above is my network structurei want to enable routing in my machine(192.168.1.5,192.168.2.1)i have already configured /etc/sysctl.confand disabled firewall in my machine i can ping 192.168.2.3,192.168.2.4and in return these two machines can ping 192.168.2.1 but they could not ping 192.168.1.6 and 192.168.1.7
View 1 RepliesI have a problem with the activation of routing under fedora. The problem lies exactly in the file ip_forward who I didn't not change the value to 1. When I use the command echo 1> / proc/sys/net/ipv4/ip_forward. They appears not granted permission. Knowing that I use the root account.
View 1 Replies View RelatedI have a Fedora Linux machine and a Windows XP machine and I want to enable TCP/IP connection between them using a cross-over cable. I have a type of middleware server running on the linux machine and I want to be able to run the client for the application on the windows machine and work that way. I have heard Samba as a solution but my understanding is SAMBA is mainly for file sharing.. and is not necessary for establishing TCP/IP connectivity. Is this a correct statement? How can I go about setting up TCP/IP connectivity between the two machines?
View 2 Replies View RelatedI have a firewall, this consists of three NIC's:
Code: eth0[192.168.0.2] eth1[192.168.1.2] and eth2[10.10.165.2]
I am trying to ping eth0 from eth2, but I am not able to succesfully get a response from pinging the device, I am using:
Code: ping 192.168.0.2 -I eth2
I have tried to insert routing data into the routing table, but it still doesn't work
How do I find out or know whether or not an FTP client is enabled or disabled on my Linux machine? If it is disabled, how do I enable it?I have a Linux 2.6.9-67.ELsmp
View 2 Replies View RelatedHow Do I enable a port 843 in a Linux machine . I have written a server program that listens to port 843 and responds when requested . But Client socket request is not able to reach that port . socket.connect functions returns -1 with timeout. I have edited /etc/services to add that port . But this is not working .
View 6 Replies View RelatedI have been searching for the past hour trying to figure out how I can enable telnet on my Ubuntu 10.10 Virtual Machine.I am using VirtualBox to run my VM. I am trying to access that VM using PuTTy but most everything I have seen says I have to enable telnet first.The directions that I have found say to go to System > Administration > Services and enable telnet.I have nothing called Services under Administration.
View 9 Replies View RelatedI have tried many ways to enable vdpau support in my machine but for no avail. A member here helped me very much but I couldn't manage to succeed. My system has Ubuntu 9.10 64-bit, Nvidia 8500GT 512mb, Intel Core 2 duo. I have installed Nvidia driver version 195 currently available from their site. I tried compiling mplayer with vdpau support from various tutorials thread here around in Ubuntu forums.
Is there anyone in this forum with Ubuntu 9.10 64 bit with the same other system requirements as mine who have successfully managed to make the VDPAU work?
After reading about Linux I decided to try it on an old HP Pavilion model 6617 desktop running Win 98 - so far with limited success!
View 10 Replies View RelatedHow to recompile squid under fedora 13 to insert this arguments ---> --enable-storeio=diskd,coss
View 2 Replies View RelatedI have a fedora 13 with two Internet links, but I'm having problems in configuring them. In the past 11 fedora works fine, on Redhat, Centos, only fedora 13 and 12 is not working the same configuration posted below:
# File rc.local
ip route add 200.20.150.192 dev eth0 src 200.20.150.194 table 1
ip route add default via 200.20.150.193 table 1
ip route add 192.168.2.0 dev eth3 src 192.168.2.2 table 2
ip route add default via 192.168.2.254 table 2
ip route add 200.20.150.192 dev eth0 src 200.20.150.194
ip route add 192.168.2.0 dev eth3 src 192.168.2.2
ip rule add from 200.20.150.194 table 1
ip rule add from 192.168.2.2 table 2
ip rule add fwmark 1 lookup 1
ip rule add fwmark 2 lookup 2
ip route flush cached
# The route default is to link 1 ( 200.20.150.193 )
# Some configuration basic tested and not work with iptables
iptables -t mangle -A PREROUTING -i eth3 -s 192.168.0.0/24 -j MARK --set-mark 2
iptables -t nat -A POSTROUTING -o eth0
iptables -t nat -A POSTROUTING -o eth1
My iptables do the identification mark of the packets, but some things happen that it could not do the routing of packages in Fedora 13 and 12, I don't really know what can be, I tried everything I knew.
I recently installed Deluge 1.2.0 from the following PPA:[URL]I using this on two different Linux computers. One is running Linux Mint 8 and the other is running Ubuntu Netbook Remix 9.10. The first time on either computer when I enable WebUI in the Deluge GUI it works fine. However if I ever disable it in plugins section I am subsequently unable to re-enable it (doesn't appear in the side panel again). Rebooting or reinstalling Deluge seems to have no effect.Is this a bug or am I doing something wrong?
View 3 Replies View RelatedI want to use tab networking in my kvm with routing.Can any one guide me how i can do it. i have been reading different guides over the net but not understand any one clearly.I have read this[URL].. One problem is this all my server are remote and no gui is running.I am able to install kvm with ssh console with -nographic and -x "console=ttyS0" option now i want to change from bridging to tap networking with routing.And i have live ip on kvm guest/Virtual machine.
View 1 Replies View RelatedIN LAN default GW box I have a routing rule of 172.17.1.0 192.168.180.100 255.255.255.0 UG 0 0 0 eth3 that sends packets matching 172.17.1.0/24 to eth3 etc. When I ping 172.17.1.50 - it goes correctly when ping is issued in the same box (LAN GW) - falls through to default rule when the ping is done in LAN's boxes i.e. it goes to the LAN GW box and then to Internet incorrectly instead of going to eth3 and 192.168.180.100.
Is there any way of seeing why the packet matches or not the routing rules?
I just started my Linux class the other day. We are having to use Fedora 12 it came with our book. For homework we were told to join a forum and ask 3 questions. I myself really didn't like this Idea because I would rather do some digging to find the answer but I do need the grade for the homework haha. My First question is, How do you set up routing from wireless to wired?
View 4 Replies View RelatedI have a Pc that has 2 Ethernet and I have also 2 switch. I want the PC to become the router and be connected to 2 switch.How can I setup this one on FEDORA and I want to assigned for eth0 192.168.26.51 and eth1 192.168.22.51 for the IP.
View 1 Replies View RelatedSo my server running FC4 died last night and I decided to go ahead with the long-awaited upgrade to FC10 while I was rebuilding my server. I use my server for a number of things including, but not limited to: router, firewall, web server, mail server... I have a typical configuration process that I have followed since before fedora, and it has worked well for me up through FC4, but my usual config process doesn't work on FC10.
First of all, I don't want SELinux running, I didn't see an option to not install it during the FC10 setup, so how to I properly disable or uninstall it afterwards? Second, I was unable to even configure the server to route traffic from my internal network to the web, here's the process I usually go through for this:
[Code]...
I don't have a static IP from my ISP, so I'm not quite sure how to add the default route. I think I need to do something like "route add default gw xxx.xxx.xxx.xxx eth1" where eth1 is my external NIC, correct?
What else do I need to do to route traffic? I noticed that I wasn't even able to ping my server from the internal network even though they are on the same subnet, my server's internal NIC has an address of 192.168.7.1 and my computer on the network has an address of 192.168.7.2. If I can get this going to I have internet access again at the very least, I can move forward with the web server, email, etc.
I have just installed Fedora 10 on an old laptop and was quite impressed with how smoothly it all went ... until it came to setting up networking!
I have battled for three days now and I'm almost there;
- installed updated firmware to the built in Broadcom 4306 wireless network adapter
- got NetworkManager to work with a static ip address by manually editing the ifcfg-wlan0 file
- managed to get the WPA security to work
The only problem I am left with is that there is no default route; if I set one up using: ip r a default via 10.1.1.1 dev wlan0
Then everything starts working.
If I try to add routes using the NetworkManager gui interface they dont get saved (no suprises there then! ).
I have tried creating a route-wlan0 file in /etc/sysconfig/network-scripts/ but this seems to be ignored by NetworkManager.
Since the NetworkManager GUI is almost useless, does anyone know if there are any other configuration files I can manually modify to get a default route set?
On a Fedora 11 machine, I configured ppp0 on eth0 and ppp1 on eth1, each one is connected to a modem, I also defined ppp0 as the default gateway.. Should I do anything else to load balance the 2 connections or will ppp1 take some of the load by default? Should I add any other routing rules? If yes then please tell me what should I add, keeping in mind that for each pppoe connection both the pppoe address and the remote address are not static so I actually needed some scripting to change the default gateway each time the remote pppoe address changes.
View 4 Replies View RelatedBackground: Took a while to get this working correctly, so figured I'd save you all some time... I (finally) received the beta invite from iPredator. I wasn't happy with the NetworkManager-pptp implementation, I'm running the stock kernel, I stopped the NetworkManager service at this point.
Goals:
1. To be able to control the PPTP tunnel from a remote location over ssh
2. To have services I run from my box accessible via my public IP on the internet (sshd, httpd etc) whilst the tunnel is up
3. To route all Torrent traffic from Vuze out of the encrypted PPTP tunnel, and have it return over that interface
4. To route all other traffic, by default, to my ISP unencrypted
5. To block all Vuze traffic if the tunnel is down
Method:1. PPP config
First, I entered my login details (altered in the below output, of course!!) into chap-secrets and then used "chmod 600 chap-secrets" to make it read/write for root only:
Next, I created a peer file (644 permissions) for the VPN connection, the file name has to match the "iPred" I used above:
I stuck with the defaults in /etc/ppp/options.pptp
To initiate the tunnel, I use: pppd call iPred mtu 1435 mru 1435 persist nolog
Regarding the options used... I'll get onto the MTU/MRU later, persist has the tunnel attempt to reconnect 10 times if it drops, nolog reduces the high volume of syslog messages. The logs for the connection process are written to /var/log/messages, interface ppp0 was created and routing entries were set up (internal network stuff has been cut out below; we'll call 192.168.100.104 my WAN IP, though I've got a static internet-routable IP and wanted to mask it here). The (dynamic) endpoint of the tunnel is 93.182.164.2: you need two routes to this, one via eth0 (my WAN interface) for internet routing of the encrypted packets, and one through the tunnel itself to tunnel and encrypt the traffic:
References:[url] [url]
2. Firewall Setup
I'm a "belt-and-braces" kinda guy ("belt-and-suspenders" if you're from the US), and I've got a custom firewall setup. As I've brought a new interface into the equation, I needed to add some rules.
In order, the rules:
A. NAT the outgoing packets to the ppp0 interface IP
B. Allow established sessions back in
C. Allow the default ports for Vuze through, even if unsolicited, on port 63255 (TCP and UDP)
D. Drop traffic that originates from Vuze (identified by the IP of interface lo:0, which we'll see later) if it tries to exit via eth0 (useful if the tunnel drops or hasn't yet been started)
You can view the rules in place by issuing: iptables -nL
References:man iptables [url]
3. Routing Setup
Obviously, I didn't know who the Vuze peers are going to be and setting a default route via ppp0 means that all traffic would be encrypted. Instead, I created a new, distinct, routing table called IPRED in iproute.
Then I added a default route, via ppp0, into the IPRED routing table and checked that it was there:
The main (default) routing table is still there and has it's routes:
4. Traffic Identification
I tried setting the DSCP (ToS) in Vuze, but that didn't make it into the packets (checking the output packets with Wireshark). So, I created a new Loopback interface lo:0 on my box (later I entered this line into /etc/rc.local so it'll survive a reboot):
I then added a rule to pass traffic from this new lo:0 IP to the IPRED table:
There are a number of other ways to pick out traffic with "ip rule", but this seemed the most elegant solution in this situation.
5. Vuze Config
I looked down the list for the local IP addresses, then bound Vuze to the lo:0 interface which, in Vuze, is lo[1]
Whilst in here, I also dropped the Line MTU to 1435. You'll notice that this matches the MTU and MRU set when using pppd to establish the tunnel... I'm on DSL and have the MTU set to 1478 for the DSL link, the difference between the 1478 and 1435 is the overhead of the additional headers used with PPTP tunnelling (both PPP and GRE headers encapsulate the packets). With the MTUs set up in this way, I shouldn't get any fragmentation of packets on the link, packets with the DontFragment bit set shouldn't get dropped. I gave Vuze a restart.
6. Verifying Operation
I closed any apps that were using the internet, fired up Vuze, loaded a torrent, then opened two Wireshark windows.... Started Wireshark#1 on the eth0 WAN interface and Wireshark#2 on the ppp0 tunnel interface. I saw a long list of PPP and GRE packets (in white) scrolling on the eth0 window, showing that Vuze is going through the tunnel. Checking the ppp0 Wireshark window, I saw the actual Vuze traffic on the ppp0, with SYN's, ACK's, http packets etc as it's being sent down/back through the tunnel.
Starting firefox and visiting www.whatismyip.com, the IP reported was my eth0 address, I saw the http traffic on Wireshark on eth0. Starting e-mail, I saw the packets on eth0.
Dropping the tunnel, I checked Vuze, saw that torrents had stopped and confirmed that I couldn't connect to the net with it.
7. DNATing
Reconnecting everything, I sat and watched the Wireshark outputs on ppp0 and eth0 for a while to make sure everything was working. I noticed that the ppp0 interface was creating a lot of ARP requests for external IP's and sending them out, unencrypted, through eth0 - BAD news!! I'd forgotten that I would need to Destination NAT the unsolicited inbound connections... D'Oh!
As the unsolicited inbound connections are directed at the internet-routable tunnel IP of ppp0, we need to point these to the lo:0 interface that Vuze is listening on. Replies to these will be NAT'd back to the ppp0 address by the MASQUERADE rule we've already entered in iptables and, since the source IP will 172.27.72.64, the packets will match the ip rule pointing them to the IPRED routing table, thus they won't generate ARP requests.
Retrying everything with the firewall updated, everything is working 100% :-D
8. Misc
As the iptables rules have been saved, and lo:0 will survive a reboot in /etc/rc.local, the only commands that need to be run each time you want to bring up the tunnel are (easily scripted with a sleep statement of about 10 seconds after pppd call...):
And, if you wanted to just send all traffic over ppp0, this would be:
Conclusion: I love Linux, an intellectual challenge, having complete control over my PC; iPredator rocks and I hope this howto is of use to anyone running Fedora and iPredator :-D
I want to implement routing using fedora 14. The following is how I arrange my computers -
[PC1]<=======>[ROUTER]<=======>[PC2]
And the following are the configuration -
PC1 : (Tiny Core Linux)
eth0 192.168.2.2/24 (netmask 255.255.255.0)
ROUTER (FC14)
eth0 192.168.2.1/24 (netmask 255.255.255.0)
eth1 192.168.4.1/24 (netmask 255.255.255.0)
PC2 (Tiny Core Linux)
eth0 192.168.4.2/24 (netmask 255.255.255.0)
On the ROUTER I have set the ip_forward=1 and eth0.proxy_arp=1 and eth1.proxy_arp=1
then I run the following command :
route add -net 192.168.2.0/24 gw 192.168.2.1 dev eth0
route add -net 192.168.4.0/24 gw 192.168.4.1 dev eth1
On PC1 I executed the following :
route add -net 192.168.4.0/24 gw 192.168.2.1 dev eth0
and for PC2 I run the following
route add -net 192.168.2.0/24 gw 192.168.4.1 dev eth0
After doing those things, I can't ping between PC1 and PC2... but both can ping the router...
In Ubuntu I can easily transfer packages from offline machine into online machine using APTonCD feature. In fedora ,Is there anything similar by which I can transfer my packages of online machine into the offline machine
View 2 Replies View RelatedI'm currently reading through the Linux Advanced Routing and Traffic Control HOWTO from lartc.org, and I'm wondering whether anyone knows of a file where I could keep qos rules persistent across a reboot, similar to /etc/sysconfig/iptables for netfilter. Should I just write my own script, or does something already exist?
By the way, iproute-2.6.29-4.fc12.i686.
I'm having problems with my route rule in Firewall, I have two links that are working, and set the firewall to use multiple links at once. What has happened is that when i look the IPs of the clients, (its have for default the route to Link 2), they are changing or losing the rule route for link 2 and have in Explorer the Link 1 in any site for show me ip address, then after some seconds back to normal. And the firewall is not configured to do routing load balancing. What can be? Exist some configuration of kernel to accept this configuration ? Like ip route source or anything ?
View 1 Replies View Relatedi have a Server, which has 2 nics installed. Each of those is connected to a router, which is connected to internet. On the server, i have apache, maillserver and im-server running. On the other hand, also squid, dansguardian and clam are running. so now: via eth0 i would like to have just the traffic, which is requested from outside (the big bad internet..) to my server (apache, mail, etc). via eth1 i would like to have all OUTGOING (also to the big bad internet) from the server, which is requested by a internal client. And of course all requests to my own server
both nics shall route their traffic to their own router. For better comprehension please consult the enclosed graph. Until now, i did not find a good solution, the default route is set to the traffic from eth0, if not, no external request will find back to a client do you have a idea how to handle this the easiest way?
I have an issue with the manner in which Network Manager is configuring the network and short of ditching Network Manager I can see no solution.The issue : Getting a machine to update its machine name in the DNS serverSounds simple doesn't it I operate a FreeBSD based firewall / DHCP / DNS server, using a default Network Manager DHCP configuration the Fedora clients do not register their names with the DNS server when they obtain an address.
I have traced the communications with Wireshark and the Fedora clients are NOT supplying the PC's hostname as part of the exchange so this is NOT a DNS server configuration issue. If I uncheck the option 'Automatically obtain DNS information from provider' under the DHCP settings the Fedora clients DO register the hostname that is put into the Hostname (optional) databox. They do NOT however store the DNS server IP address or any other records defined by the DNS server.
Is there some hidden settings or is this a bug because it isn't acceptable 'DHCP' behaviour if it isn't possible to automatically set DNS server IP addresses and at the same time register the hostname during the DHCP negotiation. Before it is said I know I can use a fixed DNS IP address but am not prepared to long term, I am also not prepared to define the Fedora clients with a 'static' IP. I am similarly not interested in playing around with scripts or any other such 'frigs' to achieve what should be a standard activity - registering a host with DNS during the DHCP negotiation.
I have been trying to SCP a couple files from my Ubuntu 10.10 machine to a Fedora 12 machine. Before today, did it with out any problems, always worked. Today however; after the SCP is complete from my machine, the file on the other machine is zero bytes, an empty file. The only thing I can remember getting changed was the new kernel that was in the update I did today. But I don't think that would have changed the SCP works.
View 5 Replies View RelatedI want to make my machine to PXE boot windows from another machine having RHEL5.2. I know the procedure to PXE boot linux, but I want to know is it possible to PXE boot your client machine with windows XP.
View 1 Replies View RelatedI don't know what I'm trying to achieve falls into 'routing' or 'Bridging'???I have two network ports (with static IP ) and I would like to forward RX packets of one to the other.
I have done this in Windows by enabling a service called 'routing'.Is there something similar in Fedora 11? I am pretty sure there are a few thread explaining these but I am just not educated enough to find one that makes sense to me, so Please excuse me for starting a redundant thread and point me to it?
I am having trouble for routing port 80 from a Billion adsl modem to a guest server in VirtualBox. There are quite few different changes from my last setup so I kind of confuse which one is wrong.
I used to use have the setup belowusing modem Linksys WAG354G use static ip 192.168.1.100 for my machine use static ip 192.168.1.102 for my guest VirtualBox server guest OS is serving http listening on port 80 i use bridge from my host OS for VirtualBox set my modem to direct all traffic on port 80 to 192.168.1.102 host OS was Fedora 11
now I useusing modem Billion 7404VNPX use same static address and configuration host OS is Fedora 13
main issue is I cannot reach the guest OS if I navigate to my modem ip address. (e.g. http://192.168.1.1) if I change the modem to direct all traffic to my host OS ip address (192.168.1.100) it works nicely.
I have tried to disable and enable the firewall without any luck.