NW Gurus Help Pl: Bridging Problem Query

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

 



Hello all

My system has two network cards. Ifconfig & route output below:

[root@swyam network-scripts]# ifconfig
eth0      Link encap:Ethernet  HWaddr E0:69:95:77:A7:F3
          inet addr:172.16.1.1  Bcast:172.16.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Memory:fe600000-fe620000

eth1      Link encap:Ethernet  HWaddr 00:60:52:0C:0B:DE
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2760421 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1810288 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3815395265 (3.5 GiB)  TX bytes:137041755 (130.6 MiB)
          Interrupt:16 Base address:0xc000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:11964 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11964 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5035051 (4.8 MiB)  TX bytes:5035051 (4.8 MiB)

[root@swyam network-scripts]# ip route show
192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.3  metric 1
172.16.1.0/24 dev eth0  proto kernel  scope link  src 172.16.1.1
169.254.0.0/16 dev eth0  scope link  metric 1002
default via 192.168.1.1 dev eth1  proto static


172.16.1.0/24 is the ltsp network. 192.168.1.0/24 is the home LAN with
192.168.1.1 as ADSL router with dynamic IP providing natted Internet
access. 192.168.1.3 is my server machine.

I wish to setup a kvm based virtual network with say 172.31.1.0/24 or
192.168.2.0/24 addressing (separate network), with various virtual
machines coming up as required on the virtual network.

Question is how to setup the bridging, so that 1) the ltsp network
machines have access to each other (for any locally run software, if
required), the virtual machines, lan machines & the Internet 2)
Similar access for all virtual machines (ltsp network, lan pcs &
internet).

Hope to get an answer here....have been stuck at this for a month now.

With best regards.
Sanjay.
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org


[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux