Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Having trouble with my network implementation for my office

Hardware:
n port switch
one server (debian based) (internet Gateway)
x amount of access points
y amount of desktops

I want to segment the desktops and access points away from each other. So Far: I've done:

vconfig add eth0 3
vconfig add eth0 10

MY /etc/network/interfaces file

auto eth0
auto eth0.3
auto eth0.10

iface eth0 inet static
address 192.168.1.101
netmask 255.255.255.0
network 192.168.1.0


iface eth0.3 inet static
address 192.168.3.101
netmask 255.255.255.0
network 192.168.3.0

iface eth0.10 inet static
address 192.168.10.101
netmask 255.255.255.0
network 192.168.10.0

Then my /etc/dhcp/dhcpd.conf file

...
subnet 192.168.1.0 netmask 255.255.255.0 {
    range 192.168.1.1 192.168.1.200;
    option routers 192.168.1.254;
    option domain-name-servers 192.168.1.101;
    }
subnet 192.168.3.0 netmask 255.255.255.0 {
    range 192.168.3.1 192.168.3.200;
    option routers 192.168.1.254;
    option domain-name-servers 192.168.1.101;
    }
subnet 192.168.10.0 netmask 255.255.255.0 {
    range 192.168.1.1 192.168.1.200;
    option routers 192.168.1.254;
    option domain-name-servers 192.168.1.101;
    }
...

On the switch then
Port connected to server is trunked and tagged to vlan 3 and 10
ports x untagged to vlan 3
ports y untagged to vlan 10

ports x or y cant get dhcp response (altho have not tried wireshark)
There isnt a firewall on the server (yet)

Anyone have any ideas?

share|improve this question

migrated from stackoverflow.com Sep 4 '09 at 8:48

This question came from our site for professional and enthusiast programmers.

    
Have you resolved this yet? If not, can you also post the relevant parts of your switch config? –  Jason Antman Oct 21 '09 at 13:18

4 Answers 4

  1. Do you really want machines in VLAN10 to receive IPs from 192.168.1.0/24 range?

  2. It is usually not a good idea to have a static IP address (in your case .101) inside the DHCP range (in your case 1..200)

  3. Assign a static IP from the correct range to a test machine and do a basic network troubleshooting (e.g. can you ping the gateway - ping 192.168.10.101)

  4. Also not sure about the 192.168.1.254. How do you specify a default gateway for machines in VLAN3 and 10?

share|improve this answer
    
1) no i wanted vlan10 to get 192.168.10.0/24 2) I know, bad desicion made by someone else i plan on changing them when i get the vlans working 3)yeah .. even though i assigned a .10.0/24 ip address i could still ping the .3.101 server and im thinking that shouldnt happen? 4)It will be using dhcp i left it out to prevent confusion but obviously added more... I've added interfaces for each vlan in the server. –  Aceth Sep 2 '09 at 18:41
    
1) see - then you have an error - vlan10 has range 192.168.1.1 192.168.1.200. Change it to 192.168.10.1 192.168.10.200 3) It is fine. You reach server via .10.101 and ping the other network interface. 4) default gateway has to be inside your network range. So if you are inside .3.0/24 then you can't have a default gateway 192.168.1.254. It has to be from the 192.168.3.0/24 range! The same applies to .10.0/24 range. –  DmitryK Sep 3 '09 at 6:15
    
btw, have a look here: redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/… Plenty of useful information. –  DmitryK Sep 3 '09 at 6:19

As you mention /etc/network/interfaces that implies a debian derivative.

I suggest you install ifupdown-scripts-zg2 which allows you to create VLAN's from within /etc/network/interfaces so you don't need to mess with vconfig.

Also have you verified basic connectivity on the VLAN's?

share|improve this answer

If you put a computer in each vlan with a static IP, can it ping your DHCP machine ? Your router ? The DHCP server can ping the router on each network ? Have you corrected your DHCP conf ? The router must be in the range of the network to be seen.

share|improve this answer

Have a look at the switches' CAM table and make sure the client's and the server's MACs are learned on the correct VLANs.

One other quick thought: you are using a mixed setup with tagged/untagged port on the server side. Is the switch able to handle this? Maybe it's easier to set up eth0 (192.168.1.101) as a tagged port (eth0.x) aswell to prevent confusion on the switch side. What kind of switch are you using?

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.