[VLAN] linux box as vlan router

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

 



And make sure you the end nodes (client a and c) have the gateway set to the appropriate VLAN interface of the router, box b.

>-----Original Message-----
>From: vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx] On
>Behalf Of Justin Cormack
>Sent: Monday, April 11, 2005 7:56 AM
>To: Linux 802.1Q VLAN
>Subject: RE: [VLAN] linux box as vlan router
>
>Make sure you do
>echo 1 > /proc/sys/net/ipv4/ip_forward
>on the router so it actually routes - it is off by default.
>
>On Mon, 2005-04-11 at 19:01 +0530, Sunil Parolia wrote:
>> Hi all,
>>
>> I try to emulate vlan setup with this setup
>>
>>
>> PC-A -? on vlan2 eth0-0.0.0.0 & eth0.2-192.168.127.141
>> PC-C -? on vlan3 eth0-0.0.0.0 & eth0.3-192.168.128.141
>>
>> PC C acting as vlan router
>> 	eth1-0.0.0.0  eth1.2-192.168.127.142
>> 	eth2 -0.0.0.0 eth2.3-192.168.128.142
>>
>> VLAN2				eth2	VLAN3 eth3
>> PC A  ---------------------->  PC B ----------------------> PC C
>>
>> I was able to ping from a to b and from c to b  but not a->c & c->a. also
>when I analyzed pkt in ethereal I found no vlan tag att to pkt.
>>
>> I?m dumping the output of route and ifconfig.
>>
>> The routing info  & ifconfig at B is
>>
>> Kernel IP routing table
>> Destination     Gateway       Genmask         Flags Metric Ref    Use
>Iface
>> 192.168.128.0   *             255.255.255.0   U     0      0        0
>eth2.3
>> 192.168.127.0   *             255.255.255.0   U     0      0        0
>eth1.2
>> 192.168.144.0   *             255.255.254.0   U     0      0        0
>eth0
>> default       192.168.144.5   0.0.0.0         UG    0      0        0
>eth0
>>
>>
>> ifconfig-
>>
>>
>>
>> eth0      Link encap:Ethernet  HWaddr 00:07:E9:09:D7:79
>>           inet addr:192.168.144.142  Bcast:192.168.145.255
>Mask:255.255.254.0
>>           inet6 addr: fe80::207:e9ff:fe09:d779/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:68255 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1599 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:6391334 (6.0 MiB)  TX bytes:198958 (194.2 KiB)
>>           Base address:0xdec0 Memory:fe960000-fe980000
>>
>> eth1      Link encap:Ethernet  HWaddr 00:07:E9:09:D5:63
>>           inet6 addr: fe80::207:e9ff:fe09:d563/64 Scope:Link
>>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>           RX packets:35 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:3584 (3.5 KiB)  TX bytes:6034 (5.8 KiB)
>>           Base address:0xdf00 Memory:fe9a0000-fe9c0000
>>
>> eth1.2    Link encap:Ethernet  HWaddr 00:07:E9:09:D5:63
>>           inet addr:192.168.127.142  Bcast:192.168.127.255
>Mask:255.255.255.0
>>           inet6 addr: fe80::207:e9ff:fe09:d563/64 Scope:Link
>>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>           RX packets:35 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:45 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:2814 (2.7 KiB)  TX bytes:3862 (3.7 KiB)
>>
>> eth2      Link encap:Ethernet  HWaddr 00:0D:56:D9:22:24
>>           inet6 addr: fe80::20d:56ff:fed9:2224/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:54 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:1000
>>           RX bytes:4016 (3.9 KiB)  TX bytes:4754 (4.6 KiB)
>>           Base address:0xdf40 Memory:fe9e0000-fea00000
>>
>> eth2.3    Link encap:Ethernet  HWaddr 00:0D:56:D9:22:24
>>           inet addr:192.168.128.142  Bcast:192.168.128.255
>Mask:255.255.255.0
>>           inet6 addr: fe80::20d:56ff:fed9:2224/64 Scope:Link
>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>           RX packets:28 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:1680 (1.6 KiB)  TX bytes:1776 (1.7 KiB)
>>
>> lo        Link encap:Local Loopback
>>           inet addr:127.0.0.1  Mask:255.0.0.0
>>           inet6 addr: ::1/128 Scope:Host
>>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>           RX packets:1932 errors:0 dropped:0 overruns:0 frame:0
>>           TX packets:1932 errors:0 dropped:0 overruns:0 carrier:0
>>           collisions:0 txqueuelen:0
>>           RX bytes:2546953 (2.4 MiB)  TX bytes:2546953 (2.4 MiB)
>>
>>
>> And at a is
>> Kernel IP routing table
>> Destination     Gateway     Genmask         Flags Metric Ref    Use Iface
>> 192.168.128.0   *           255.255.255.0   U     0      0        0
>eth0.2
>>
>> And at b is
>> Kernel IP routing table
>> Destination     Gateway      Genmask         Flags Metric Ref    Use
>Iface
>> 192.168.127.0   *            255.255.255.0   U     0      0        0
>eth0.3
>>
>>
>> I have devoted 2 days but I'm not able to figure out the problem. What is
>going wrong?? Please direct me where I?m doing mistake.
>>
>> Thanks ?
>> Sunil Parolia
>>
>>
>>
>> ________________________________________
>> From: vlan-bounces@xxxxxxxxxxxxxxx [mailto:vlan-bounces@xxxxxxxxxxxxxxx]
>On Behalf Of hareram
>> Sent: Monday, April 11, 2005 5:20 PM
>> To: vlan@xxxxxxxxxxxxxxx
>> Subject: Re: [VLAN] linux box as vlan router
>>
>> Hi
>>
>> yes you can do that with out any effort
>> if you are newly installing, install selecing all packages
>> so its installs automatically.
>>
>> vconfig package for adding vlans
>>
>> this link may help you
>>
>> http://www.planetconnect.com/vlan/
>>
>> hare
>> ----- Original Message -----
>> From: Sunil Parolia
>> To: vlan@xxxxxxxxxxxxxxx
>> Sent: Monday, April 11, 2005 11:08 AM
>> Subject: [VLAN] linux box as vlan router
>>
>> Hi I'm new to vlan. This q may sound absurd, but just wanted to know can
>we configure standard linux box as vlan router? If yes can anybody direct
>to relevant site for configuration? I'm using fedora-3 with kernel version
>of 2.6.9-1.667
>>
>> Thanks & regards,
>> Sunil Parolia
>>
>> ________________________________________
>> _______________________________________________
>> Vlan mailing list
>> Vlan@xxxxxxxxxxxxxxx
>> http://www.lanforge.com/mailman/listinfo/vlan
>>
>> _______________________________________________
>> Vlan mailing list
>> Vlan@xxxxxxxxxxxxxxx
>> http://www.lanforge.com/mailman/listinfo/vlan
>
>_______________________________________________
>Vlan mailing list
>Vlan@xxxxxxxxxxxxxxx
>http://www.lanforge.com/mailman/listinfo/vlan

Required statement:
My thoughts and ideas are mine and do not necessarily reflect those of my employer's.


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]     [Video 4 Linux]

  Powered by Linux