tag:blogger.com,1999:blog-1914137086502555859.post1379220070697869555..comments2019-02-18T15:33:07.664+05:30Comments on Your Own Linux..!: How to : Configure Ubuntu as a RouterMandar Shindenoreply@blogger.comBlogger23125tag:blogger.com,1999:blog-1914137086502555859.post-27100013374112194642017-08-23T12:29:55.639+05:302017-08-23T12:29:55.639+05:30heyy can you create a script that the linux server...heyy can you create a script that the linux server turns into router? thanks<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-23655094612451182162017-06-04T03:50:39.764+05:302017-06-04T03:50:39.764+05:30All due respect to the webmaster, I see several p...All due respect to the webmaster, I see several problems with this configuration. Routers are used to break up broadcast domains, so instead of having two interfaces in 10.10.6.0/24, one host should be in something like 10.10.6.0/23 and the other should be in something like 10.10.7.0/23 to make two different subnets communicate. Also, since eth0 has a default gateway of 10.10.6.203 which is localhost, the command in IPtables should read &quot;sudo iptables -A POSTROUTING -t nat -o eth0 -j MASQUERADE&quot;, eth0 should be set (with forward) rules to the NAT interface, and eth1 should use 10.10.6.203/23 as its default gateway to reach the outside. That scenario would be a better fit sir. Kind regards and thank you for your post. Admin LinAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-76629297619270129472017-04-16T21:15:49.695+05:302017-04-16T21:15:49.695+05:30Can this tutorial be followed for wlan interface?Can this tutorial be followed for wlan interface?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-13311272979620947992017-02-22T22:23:51.461+05:302017-02-22T22:23:51.461+05:30If 10.10.6.2 is between the switch and host A (192...If 10.10.6.2 is between the switch and host A (192.168.1.0 network) then the routing aspect of the article happened on the 10.10.6.2 gateway and not the Ubuntu &quot;router&quot;...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-61933271940523911982017-02-20T07:29:32.822+05:302017-02-20T07:29:32.822+05:30Not abke to ping 192.168.50.4 from my router ether...Not abke to ping 192.168.50.4 from my router ethernet 192.168.50.1 and vice versa.<br /><br />Pls. suggestrajat kotharihttps://www.blogger.com/profile/06758270854297787787noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-91619434579438385842016-11-05T01:06:51.617+05:302016-11-05T01:06:51.617+05:30Have been trying for 2 days to get ubuntu to route...Have been trying for 2 days to get ubuntu to route IP traffic from my raspberrypi zero connected via USB. The 3 commands:sudo iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE<br /><br />sudo iptables -A FORWARD -i eth1 -o eth0 -m state -–state RELATED,ESTABLISHED -j ACCEPT<br /><br />sudo iptables -A FORWARD -i eth0 -o eth1 -j ACCEPT<br /><br />work great!scotto2000https://www.blogger.com/profile/01607202874355915538noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-19125464459370925972016-06-07T20:38:12.027+05:302016-06-07T20:38:12.027+05:30NooooooNooooooLuc Goossenshttps://www.blogger.com/profile/13549420752151439399noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-91567385603658653762015-06-24T17:45:14.903+05:302015-06-24T17:45:14.903+05:30DNS not resolving in the client machine, but it is...DNS not resolving in the client machine, but it is resolving in the server. please help.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-11215434903852677862015-01-27T08:58:49.794+05:302015-01-27T08:58:49.794+05:30If both of your cards are in the same [sub]network...If both of your cards are in the same [sub]network the PC is not routing is switching.<br />In the configuration described the Switch must be rounting or Host A will never see your PC NIC.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-14226840470438114112014-02-16T16:35:00.043+05:302014-02-16T16:35:00.043+05:30Here eth1 should be in 192.168.1.x network. then o...Here eth1 should be in 192.168.1.x network. then only Host A can reach eth1 as a Gateway. It should not be in 10.0.6.x Anbarasanhttps://www.blogger.com/profile/12464851582688351976noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-59181061094020937952014-02-13T17:58:42.116+05:302014-02-13T17:58:42.116+05:30If Host A and Host B are in the same network, ther...If Host A and Host B are in the same network, there is no need of a router!<br />I tryied with host A and host B in differents networks but it doesn&#39;t work :(<br />Any tips??? <br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-12059453382837668472014-01-15T07:16:47.423+05:302014-01-15T07:16:47.423+05:30I read your post. Thanks so much!
I have problems ...I read your post. Thanks so much!<br />I have problems for my network: Host A, RedHat Linux (2 Lan Cards), Host B.<br />_ Host A: 192.168.1.2 netmask 255.255.255.0 gw 192.168.1.1 (connect to eth0 - RedHat).<br />_ RedHat Linux: eth0 192.168.1.1 netmask 255.255.255.0<br /> eth1 192.168.2.1 netmask 255.255.255.0<br />_ Host B: 192.168.2.2 netmask 255.255.255.0 gw 192.168.2.1 (connect to eth1 RedHat).<br />From Host A, I can ping to eth0, eth1 but I can&#39;t ping to Host B<br />And From Host B, I can ping to eth0, eth1 but I can&#39;t ping to Host A<br />Can you help me?Phat Hohttps://www.blogger.com/profile/16138064199109331126noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-62431457393187427762013-11-10T20:53:47.855+05:302013-11-10T20:53:47.855+05:30Lots of crap may happen while using abovemention c...Lots of crap may happen while using abovemention configuration.<br /><br />First of all, it may be OK to enable Path MTU Discovery with MSS Clamping (http://lartc.org/howto/lartc.cookbook.mtu-mss.html). Otherwise half of sites won&#39;t work.<br /><br />Secondly, sometimes it&#39;s necessary to disable TCP timestamps (http://www.tmltechnologies.com/html-2012/index.php/linux-rescue-kits/82-secret/91-disable-tcp-timestamps-on-linux). Otherwise you may face specific TCP ports unreachability.<br /><br />Other tricks may involve MTU lowering.<br /><br />Consider that.post-factumhttps://www.blogger.com/profile/12098091624630953604noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-58677891352963742522013-11-04T23:37:00.692+05:302013-11-04T23:37:00.692+05:30Try updating your kernel version and reboot your s...Try updating your kernel version and reboot your system.Mandarhttp://www.yourownlinux.comnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-46223988339124011692013-11-04T23:05:21.563+05:302013-11-04T23:05:21.563+05:30when i enter the command: sudo iptables -t nat -A ...when i enter the command: sudo iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE<br />i get this message: iptable: no chain\target\match by that name<br />what should i do?Ahmed Alaahttps://www.blogger.com/profile/10931121625813550371noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-37219706049708248212013-10-29T17:58:39.948+05:302013-10-29T17:58:39.948+05:30Hi. Theres a mistype with your tuto, it should be:...Hi. Theres a mistype with your tuto, it should be: sudo iptables -A FORWARD -i eth1 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT<br /><br />Thanks for the tuto, saved my day!poisonhttps://www.blogger.com/profile/01523732192428686186noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-39761222962634585732013-10-29T00:47:55.993+05:302013-10-29T00:47:55.993+05:30Getting an error:
firewall:~$ sudo iptables -A FOR...Getting an error:<br />firewall:~$ sudo iptables -A FORWARD -i eth1 -o eth0 -m state -state RELATED,ESTABLISHED -j ACCEPT<br />Bad argument `RELATED,ESTABLISHED&#39;<br />Try `iptables -h&#39; or &#39;iptables --help&#39; for more information.<br /><br />Any ideas?poisonhttps://www.blogger.com/profile/01523732192428686186noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-72983605288508996502013-10-26T23:06:18.236+05:302013-10-26T23:06:18.236+05:30It worked fine for me.It worked fine for me.Mandarhttp://www.yourownlinux.comnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-80961550482815318692013-10-26T19:28:19.736+05:302013-10-26T19:28:19.736+05:30shoudn&#39;t the eth0 gateway be (10.10.6.204) ? o...shoudn&#39;t the eth0 gateway be (10.10.6.204) ? or it is right as you did it ?Ahmed Alaahttps://www.blogger.com/profile/08863785695920563733noreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-1260395859437306962013-09-28T14:10:15.261+05:302013-09-28T14:10:15.261+05:30This experiment was performed in the college campu...This experiment was performed in the college campus and the gateway 10.10.6.2 was located between the Switch and Host A.Mandarhttp://www.yourownlinux.comnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-87385196181550029772013-09-27T08:27:43.144+05:302013-09-27T08:27:43.144+05:30I cannot find the gateway 10.10.6.2 from your conn...I cannot find the gateway 10.10.6.2 from your connection diagram or summary. Can you show me where it is.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-42778111558371506272013-09-25T11:58:12.995+05:302013-09-25T11:58:12.995+05:30Well, in above experimentation, eth0 (the router i...Well, in above experimentation, eth0 (the router in fact) and the client were in the same network. And IP address of eth0 was the default gateway for the client.<br />Plus 1 for you. :)Mandarhttp://www.yourownlinux.comnoreply@blogger.comtag:blogger.com,1999:blog-1914137086502555859.post-51211888444992005542013-09-25T03:08:08.188+05:302013-09-25T03:08:08.188+05:30shouldn&#39;t eth0 be in the same network as the c...shouldn&#39;t eth0 be in the same network as the client? Is presume the client would use eth0 as its def gw?Anonymousnoreply@blogger.com