=== Napsterbater is now known as Guest66672 === Napsterbater_ is now known as Napsterbater [16:51] morning guys [16:51] anyone here savvy with vlans? [16:51] for osme reason cant get one to fire up [16:52] https://pastebin.com/M1qkZWbq [16:52] thats my /etc/network/interfaces [16:52] followed this guide https://wiki.ubuntu.com/vlan [16:52] eno1.13 starts fine [16:57] fretegi: whihc ubuntu release is this? do you know about netplan, systemd-networkd? [16:58] I don't think you need to specify netmask when you put the /24 in the address [16:58] netplan + systemd-networkd: https://netplan.io/examples/#attaching-vlans-to-network-interfaces [16:59] and the interfaces(5) man page doesn't mention vlan-raw-device, I think it should be able to figure that out from the name [16:59] fretegi: typo in your file: you named it eth1.8 instead of eno1.8 [16:59] took me a while to notice! [17:00] hey since when do wiki.ubuntu.com pages no longer show the last modified date? [17:07] mgedmin, jesus.... [17:07] mgedmin, lol great eye thanks! [17:08] mgedmin: wiki.ubuntu.com still shows last modification time + editor for me on the bottom [17:08] tomreyn: what does it say about https://wiki.ubuntu.com/vlan ? [17:09] nothing :( [17:09] mgedmin, yea i was wondering about those details myself.. i just put em in there as the guide calls for it. in fact.... my pihole is on a vlan and the config follows your line of thinking, this device is just more mission critical so figured id follow the guide better [17:09] mgedmin: that's until you click on "info" on the top [17:09] ah, I can see it in https://wiki.ubuntu.com/vlan?action=info [17:10] last updated in 2012, no wonder it doesn't say anything about netplan or systemd-networkd [17:10] "use iproute2" also seems old ;) [17:13] at least iproute2 is still the current tool at that abstraction level [17:14] mgedmin, otherwise config looks fine? [17:15] mgedmin, made those changes and not doesnt seem to want to connect to anything... dang it lol [17:18] oh right, iproute2 is fine. i keep mixing those packages up with the commands. [17:20] mgedmin: vlan-raw-device is part of the vlan-interfaces extension to interfaces: http://manpages.ubuntu.com/manpages/bionic/man5/vlan-interfaces.5.html [17:21] but "This is ignored when the devicename is part of the vlan interface name." [17:21] cool, I thought it might be [17:23] fretegi: do you have the "vlan" package installed (due to deprecation, it moved to universe with 20.04 LTS)? [17:24] you didn't say which Ubuntu release you're using, though [17:24] ah yes good pt [17:24] ubuntu 18 [17:24] there's two of those [17:25] but one is eol, so hopefully not that one [17:25] hopefully! [17:25] 18.04 haha [17:25] yea still using vlan package [17:26] i know i know... this ole dog needs upgrading [17:27] 16.04 lts would, no need to rush it for 18.04, yet [17:28] tomreyn, perhaps im misunderstanding how this works [17:28] adding a managed switch to a network === xtao_ is now known as xtao [17:30] managed switch created 4 vlan networks.. i have a port trunked for vlans 8 & 13. i want this server to connect to both vlans [17:30] so i created the file saw before. confirmed on boot that both vlan interfaces come up on the server. i connect to the switch nothing... [17:30] trying to ping it from a device within the same vlan, so just level 2 routing... nothing.. [17:32] i mean i need the vlan tags on the server do i not? or is it just asking for an IP on the proper subnet of a particular vlan sufficient? [17:35] fretegi: whether oyu need to configure the vlans on the server depends on how you want to set things up architecturally. you can do so, or you can have the vlan end on the managed switch and then just hand out single vlans on the ports that connect to the server(s). [17:36] you mentioned link aggregation / port trunking, but this is really a different / separate concept to vlans. you can combine the two. [17:37] with the current configuration, you're not doing link aggregation, but i assume you're aware of this. [17:39] you're making vlans 8 and 13 available to the server through the single physical ethernet interface eno1 [17:39] tomreyn, right, the goal here was to have the server connect to 2 dif. vland ( 8 & 13 ) for purposes of different services being offered to the respective vlans and keeping traffic seperate [17:40] only 1 nic on server [17:41] then a trunked interface on the switch for both vlans 8 & 13. figured the server would 'tag' the traffic per the respective vlan and the switch would handle accordingly. am i think about this all wrong? [17:41] if you just pass through traffic on the switch without removing the vlan layer, your servers' ip addresses should become available to other resources on these LANs. [17:43] ok going into the switch now, cisco sg350 if that matters [17:46] you're right about the server doing the vlan tagging. with your configuration, if you also added the interface to the vlan using vconfig (and ensured the module is loaded), what is directed towards 192.168.8.* should get vlan tag 8, and what is directed towards 192.168.13.* should get vlan tag 13 [17:46] tomreyn, ok thanks for confirming [17:47] so im in my switch.. the port im connected ive confirmed is set to trunk and tag traffic from those 2 vlans [17:48] this machine im typing on... is on that vlan 8, via an assigned port on same switch, cant ping server... [17:49] now my router is issuing the IP's. so i suppose if server is not getting IP's i cannot route [17:50] i'm not so familiar with cisco stuff, but assume you don't want to set vlan tagging on the port the server connects to, unless you want the vlan to end there. [17:51] (which you probably dont want, a vlan just between the server and the switch probably makes not a lot of sense) [17:53] see i was fuzzy about that... so the port that connects the switch to my router is also trunked and tagging traffic and seems to be working fine [17:54] apparently you want "Interface VLAN Mode" = "Trunk" https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-250-series-smart-switches/smb5306-assign-an-interface-vlan-as-an-access-or-trunk-port-on-a-swi.html [17:56] yea thats what i have, just at the port level not LAG [17:57] im just lost... i dont understand.. [17:58] port is trunked... referencing the correct vlans... vlans setup on server..nothing on same vlan can talk to server.. [17:58] and nothing useful on the logs? [17:58] of what, cant get to server lol [17:59] oh, i assumed you have some means of out of band access [17:59] i do just a total pita to setup [17:59] but if you undo the switch configuration you should be able to access the server and its logs again? [17:59] seems im gonna have to [18:00] this discusses general configuration for vlan tagging https://www.cisco.com/c/en/us/support/docs/smb/switches/cisco-350-series-managed-switches/smb5827-configure-vlan-interface-settings-on-a-sx350-sg350x-or-sx550.html [18:00] sorta, joking that around now actually [18:07] dude [18:07] your a rockstar [18:07] tomreyn, so... check this out [18:08] tomreyn, so the server connected to port 6 on switch, i trunked and set to tag traffic on vlans 8 & 13 [18:09] i flip it to untagged for vlan 8, tagged for 13. now i can ping the vlan 8 tag [18:09] vlan 8* [18:10] so question is i have a tagged trunk port connecting to the router... why is that working? [18:30] fretegi: i think you only apply tags on the outer ends of a vlan, not all devices the traffic passes through. [18:30] so if you do it on the server, and the vland expands beyond your switch, then you don't need to do it on the switch [18:31] that's unless you want to split the traffic there and have it passed through different ports [18:33] there's also ##networking for your general networking architecture questions [18:33] great call [18:33] so.... thinking i may not even need a trunk port? [18:33] i cant have both vlans untagged... [18:34] has anyone noticed that https://ubuntu.com/download/server shows 20.10 as LTS [18:35] lol 5-years of guaranteed support no backsies! [18:36] hehe, on the button, right. it does say "including nine months of security and maintenance updates, until July 2021" above it, though. [18:36] scroll down, file a but [18:36] *bug [18:36] awww [18:37] yeah, read that, but the button headline [18:54] Anyone here running KVM qemu setup with virtmanager? Im struggling to get RDP connection for windows vms [18:55] Using Ubuntu 18.04 server [18:55] WobblyBob: you shoudn't need to configure this on the virtualization, as long as the vm has network connectivity [18:55] I know this is whats confusing me :/ [18:58] how can i check what port each vm is using [18:58] ? [18:59] the ip address should be enough...are you bridging the network interface or nat? [18:59] WobblyBob: what type of network is libvirt using? is it NAT, bridged, routed or something else? [18:59] easyst config on that is to bridge a network interface and then have a dhcp server on the phisical network somewhere... [19:00] or after connecting your guest to the bridged adapter set a static ip on the same subnet as your physical network. [19:01] has anyone had to set up an apache2 proxy to a wordpress server? [19:02] grendal-prime: reverse proxy? [19:03] I have a whole grip of web servers that i can access via virtual hosts...ya referse proxy...anyway they all work fine with like ops.mydomain.com or dev.mydomai.com but for some reason the one site that someone wants a wordpress server on...when i try and connect to it..."dev.mydomain.com" i can see it is usine the ipaddress wich..is internal and of course will not resolve [19:05] eventually times out and in the browser windows shows 192.168.20.31 wich is the ip of the wordpress serer. Now..i have read that i need ProxyPreserveHost on in the config...but that does not seem to do anything. [19:09] really werid part it worked for some time until i tried to log into the admin portion of it...ive tried clearing cache...nothing its really strange [19:11] does wordpress know that it's supposed to live at dev.mydomain.com? [19:11] thats a good question [19:12] * mgedmin has never used or configured wordpress, but usually when you do reverse proxying you have to tell the final web server how to generate correct urls to itself [19:12] i dont know didly dick about word-press to be honest. [19:12] hmf....i have not had to do that with any of my other web application servers... [19:12] good idea though [19:12] there are possible workarounds on the apache side, but they involve running regexp replaces on the html and just no [19:13] also, ProxyPassReverse is a lighter form of that that fixes up things like Location: headers on redirects [19:19] beam me up, scottie [19:23] mgedmin, you mean i need to use one or the other but not both? like ProxyPassReverse or ProxyPass but not both? [19:24] no, that's not what I mean [19:24] you use either ProxyPass alone, or ProxyPass + ProxyPassReverse [19:24] but ideally the backend server knows its public name and you don't need to use ProxyPassReverse [19:24] besides ProxyPassReverse fixes wrong URLs in headers but doesn't fix them in document bodies [19:25] grr...i knew this thing was going to be a pain in the ass [19:29] Sorry if i missed anything my internets being horrible lol [19:30] !irclogs [19:30] Official channel logs can be found at https://irclogs.ubuntu.com/ . LoCo channels are now logged there too. Meetingology logs at https://ubottu.com/meetingology/logs/ [19:33] dude..you were right [19:33] i need to go get my pelet gun and shoot myself in the foot so i never forget this [19:35] wordpress i accessed it on its wp-admin and settings->general change the site urls to whatever you set your domainname (incoluding the subdmain) and whammo IT WORKS! [19:41] congrats!