Setting up a VLAN part 2
-
You can add static dhcp IPs with an option on that same page. Or if you have statically assigned the IP on the client itself you can add it manually in the host overrides table at the bottom.
If I need to have anything static I always use static DHCP rather then IPs coded at the client. It makes this sort of thing far easier. Also if I do have to change the IP ever it's all centrally stored.
Steve
-
You can add static dhcp IPs with an option on that same page. Or if you have statically assigned the IP on the client itself you can add it manually in the host overrides table at the bottom.
If I need to have anything static I always use static DHCP rather then IPs coded at the client. It makes this sort of thing far easier. Also if I do have to change the IP ever it's all centrally stored.
Steve
makes sense and i am going to look into that, thank you.
ok, i did that, i added the entry for the static device.
when i ping it, it resolves to a public internet address not the internal IP…..hmmmm
-
You may have to clear the local dns cache. Make sure your client is using the DNS forwarder.
You can try using the Diagnostics: DNS Lookup: tool to check pfSense can resolve it correctly.Steve
-
You may have to clear the local dns cache. Make sure your client is using the DNS forwarder.
You can try using the Diagnostics: DNS Lookup: tool to check pfSense can resolve it correctly.Steve
DNS lookup in pfsense can see the correct name if i type in the ip and it shows the correct ip if i type in the name.
but it uses 127.0.0.1, then 208.67.222.222, 208.67.220.220, finally 192.168.1.1
i do want my machines to use openDNS server for external lookups, but obviously not for internal lookups, which is what i think it happening, but i could be wrong.
local cache cleared and my ipconfig looks like this
ip- 172.10.10.210
sub- /24
gate- 172.10.10.1dns- 172.10.10.1
-
127.0.0.1 is the local machine, which it is checking first. That seems correct. I don't know why it's looking at 192.168.1.1 though, that sounds wrong.
See my screenshots.Steve
-
i know 127 is localhost, but i removed that from the DNS page.
my DNS forwarders are 208.67.222.222, 208.67.220.220, and 192.168.1.1 (for devices that sometimes grab 3 DNS IPs.
although, 192.168.1.1 might be wrong and i probably shouldn't keep it in there now that i no longer have a flat network.
-
@tomdlgns:
my DNS forwarders are 208.67.222.222, 208.67.220.220, and 192.168.1.1 (for devices that sometimes grab 3 DNS IPs.
You mean in System: General Setup: DNS Servers: ?
That should only list external DNS servers that pfSense uses for DNS resolution.
Steve
-
@tomdlgns:
my DNS forwarders are 208.67.222.222, 208.67.220.220, and 192.168.1.1 (for devices that sometimes grab 3 DNS IPs.
You mean in System: General Setup: DNS Servers: ?
That should only list external DNS servers that pfSense uses for DNS resolution.
Steve
ok, no problem, i will remove the 192 entry, if i do that, then only the openDNS servers remain, but those are in spot 1,2 right now so i dont think it will fix my issue, but i will still remove it.
thanks.
-
Ok. Well yes it has to first use the local DNS table so 127.0.0.1 should show first as in my screenshot.
Where exactly did you remove 127.0.0.1 from?pfSense will always use the local DNS table first unless you have checked 'Do not use the DNS Forwarder as a DNS server for the firewall' in System: General Setup: DNS Servers:
Steve
-
Ok. Well yes it has to first use the local DNS table so 127.0.0.1 should show first as in my screenshot.
Where exactly did you remove 127.0.0.1 from?pfSense will always use the local DNS table first unless you have checked 'Do not use the DNS Forwarder as a DNS server for the firewall' in System: General Setup: DNS Servers:
Steve
i didnt remove it, i thought i saw an option to uncheck the use of it.
-
Hmm, that looks fine. Exactly as I have mine set.
Yet when you use Diagnostics: DNS Lookup: it doesn't use 127.0.0.1?
Steve
-
ok, i just added 127.0.0.1 as the first entry and bumped down the openDNS servers.
-
Hmm, that looks fine. Exactly as I have mine set.
Yet when you use Diagnostics: DNS Lookup: it doesn't use 127.0.0.1?
Steve
yeah, i think i am going to take it out, if yours doesnt have 127.0.0.1 listed as the first one.
-
this is what my settings are as of this post:
C:>ping ds2411
Pinging ds2411.home [192.168.1.254] with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64
Reply from 192.168.1.254: bytes=32 time<1ms TTL=64Ping statistics for 192.168.1.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0msC:>
-
i think it is a mac thing. i was trying to ping from my MBP and it was coming back with ds2411 as a public IP address 67.25.xxx.xxx i only x it out because i am not by my MBP and i dont remember the rest of the address.
good news- the option you told me to check a few posts backs when you brought up DHCP worked for windows computers, i tested two computers that were resolving ds2411 to 67.25…..and they now resolve to the correct internal 192.168.1.254 address.
bad news- not working for my mbp. i tried clearing the cache and releasing/renewing ip...nothing, maybe a reboot? i havent had the mbp for a long time, not an expert with it/settings on it.
-
Hmm, well I have almost no mac experience so I'm probably no help.
I would guess that it's using an external dns server some reason. Seems odd though.What external address is it resolving to? Your WAN address?
Steve
-
Hmm, well I have almost no mac experience so I'm probably no help.
I would guess that it's using an external dns server some reason. Seems odd though.What external address is it resolving to? Your WAN address?
Steve
no, i have no clue, let me see if putting it in google tells me anything.
edit- it looks like that IP address belongs to/is an address that openDNS uses/works with for failed lookups.
it makes sense since i open up a cmd prompt and typed in ping afffaasdf
it came back with the same 67.215 IP address that i get when i type ping ds2411 from the mac.
no worries, this isnt related to pfsense or vlans or DNS since all my other machines are working w/o issues.
-
ok, now lets talk about getting two vlan switches to talk.
right now this is what both switches look like.
8 port-
1- E E E U U U U U
100- T U E E E E E E
200- T E U E E E E E24 port-
1- U U U U U U U U E E E E E E U U U U U U U U U U
100- E E E E E E E E T U U U E E E E E E E E E E E E
200- E E E E E E E E T E E E U U E E E E E E E E E Ei know i have to link the respective vlan ports to each vlan switch, but do the packets stay labeled as i have them above? or do i need to switch a few things around when linking from switch to switch?
-
When you link from switch to switch you can send all the VLANs along a trunk connection, the same as you do to pfSense.
So you have one cable connected between the switches. The port that that cable is connected to is set as 'tagged' in each VLAN you want to send along it at both ends.I'm not sure how you have your 24-port switch connected so I can't give you an exact switch config.
Steve
-
When you link from switch to switch you can send all the VLANs along a trunk connection, the same as you do to pfSense.
So you have one cable connected between the switches. The port that that cable is connected to is set as 'tagged' in each VLAN you want to send along it at both ends.I'm not sure how you have your 24-port switch connected so I can't give you an exact switch config.
Steve
the 24 port switch is connected to the 8 port switch as follows:
port 4 on HP-switch8 goes to port 8 on HP-switch24.
however, i dont think the proper tags are in place.
EDIT-
both tags are marked as U and it looks like they both need to be changed to T, correct?
