| 02:00.19 | *** join/#utah tiwula (~lane@134-54-190-199.cust.rcwmoab.com) |
| 14:37.29 | *** join/#utah emcnabb (~emcnabb@hs-nc-1fff767f54-29977-1.tingfiber.com) |
| 16:07.23 | *** join/#utah josephscott (~josephsco@c-174-52-11-31.hsd1.ut.comcast.net) |
| 19:08.57 | *** join/#utah RyanE (rberick@shell.xmission.com) |
| 19:16.18 | Migs | http://pittsburgh.cbslocal.com/2018/04/05/millennials-flat-earth-survey/ |
| 20:27.20 | *** join/#utah josephscott (~josephsco@c-174-52-11-31.hsd1.ut.comcast.net) |
| 22:03.00 | jfindlay | is there a way to add an IP address to an interface such that the new address does not result in an "alias"? |
| 22:40.41 | klys | jfindlay, why would you want to do that? how do you want it to behave? |
| 22:41.00 | jfindlay | klys: I'm only trying to figure out what an alias is |
| 22:41.56 | klys | jfindlay, it's an interface which refers to the same hardware, and uses the same arp, just that it attaches to a different ip network. |
| 22:43.42 | *** join/#utah tristanbob_home (~Tristan@2602:41:82b1:f800:a19b:70fd:32e3:8262) |
| 22:44.05 | jfindlay | klys: According to my understanding `ip address add 10.10.0.1/24 dev eth0 label eth0:MyInterface` creates an aliased address whereas `ip address add 10.10.0.1/24 dev eth0` does not |
| 22:44.31 | jfindlay | I'm still not sure what that means |
| 22:45.38 | klys | it would be like saying ifconfig eth0:1 10.10.0.1 netmask 255.255.255.0 |
| 22:47.56 | jfindlay | the deprecated ifconfig framework cannot handle multiple addresses on the same device without aliasing from what I've learned |
| 22:48.56 | klys | erm, multiple addresses on the same device without aliasing? |
| 22:49.03 | jfindlay | since iproute2 has been around for like two decades, why is ifconfig still around? |
| 22:49.20 | klys | how do you propose to do that? |
| 22:50.07 | jfindlay | klys: `ip address add 10.10.0.1/24 dev eth0` |
| 22:50.44 | klys | and why? |
| 22:51.02 | jfindlay | I'm not sure, this is all new territory for me |
| 22:51.33 | klys | well, aliasing is traditionally the only way to get more than one ip on the same device (not interface). |
| 22:52.19 | jfindlay | #strongswan recommended me to not use the alias format |
| 22:52.33 | jfindlay | what's the difference between a device and an interface? |
| 22:52.42 | klys | and if it isn't an alias, does it bridge them? |
| 22:53.11 | klys | well, an interface is a logical representation of your device. |
| 22:53.32 | jfindlay | my guess is that you're responsible for setting up routes and other filtering |
| 22:54.07 | klys | if the routes go over the same device that makes less sense to me. |
| 22:55.28 | klys | I mean |
| 22:55.51 | klys | if the routes go over the same /interface/ that makes less sense to me. |
| 22:57.11 | klys | device should refer to the medium, interface should refer to media access control (medium plus address). |
| 22:58.07 | klys | well, my guess is you'll get the hang of it pretty quick. good luck with that. |
| 22:59.25 | klys | bbl suppertime. |
| 23:13.35 | klys | ~slashdot |