| 02:17.21 | *** join/#gllug Pcsett (~don@host86-135-102-188.range86-135.btcentralplus.com) |
| 02:42.51 | Pcsett | Leeds: Evening (for me!) and I'm awake at 2.45 a.m so will probably get scolded again. I've now got the fedora channel connected - doing well, eh? |
| 02:44.35 | Pcsett | Leeds: Can't stay long - MUST try to kip again. Talk again soon - byeeee |
| 02:46.42 | Leeds | night |
| 09:19.11 | *** join/#gllug gmarkall (~graham@84.45.235.192) |
| 11:10.47 | *** join/#gllug morsing (morsing@emil.morsing.cc) |
| 11:18.52 | *** join/#gllug cityLights (~cityLight@98.158.117.241) |
| 11:18.54 | cityLights | hi |
| 11:19.03 | cityLights | I need help with source level routing |
| 11:20.02 | cityLights | assuming I got eth0 from which I establish l2tp and get ppp0 , which supplies the dafult gateway, how can I answer traffic coming in to eth0 from eth0? |
| 11:31.58 | *** join/#gllug an0key (~an0key@2001:470:1f09:1367::4) |
| 12:10.52 | *** join/#gllug gmarkall (~graham@84.45.235.192) |
| 12:31.07 | *** join/#gllug cityLights (~cityLight@bzq-84-109-112-194.red.bezeqint.net) |
| 12:46.04 | antiphase | Routing is all about destinations unfortunately |
| 12:47.15 | morsing | Unless you do source routing... |
| 13:01.55 | hali | l2tp? arp should take care of that |
| 13:02.54 | hali | layer2 vpn's are always a bit of a hassle, dmvpn or something with dynamic routing is always easier |
| 13:09.10 | antiphase | ISTR that there was a reason for all the rigmarole, involving the need for bridging to carry broadcast traffic etc. |
| 13:16.21 | hali | i always find it interesting that people think layer 2 networking is easier than layer 3 and routing stuff properly |
| 13:16.48 | hali | when layer 2 is always prone to fuckups when doing complex stuff, with stuff like spanning-tree breaking etc |
| 13:33.04 | cityLights | does source based routing mean: if you get traffic from a certian IP address answer using this device? |
| 13:41.02 | antiphase | No. It's a deprecated method of routing where the sender of a packet may specify the route to the destination |
| 13:41.42 | antiphase | It's a huge security risk and you're unlikely ever to see it enabled except by accident |
| 13:42.33 | antiphase | If you want to originate packets from specific interfaces, then you need to have a route to the destination which specifies that interface |
| 13:43.26 | antiphase | Otherwise, your traffic will leave by the most specific route to that destination according to the routes you do have available, or the default route if there isn't one |
| 18:47.43 | *** join/#gllug boudiccas (~boudiccas@unaffiliated/boudiccas) |
| 20:12.37 | *** join/#gllug gmarkall (~graham@84.45.235.192) |
| 20:58.21 | cityLights | can I say "any communication coming in via port 1234 will be answered via eth0? |